GPNPD Crashed Because it Could Not Establish a TCP Connection to Remote Servers (Doc ID 1249614.1)

Last updated on DECEMBER 29, 2010

Applies to:

Oracle Server - Enterprise Edition - Version: and later   [Release: 11.2 and later ]
Information in this document applies to any platform.


CRS does not come up because ocssd.bin fails to come up.  The ocssd.log shows that it can not talk to gpnp daemon.

The following is a sample excerpt from the end of the ocssd.log (located in $GRID_HOME/log/<hostname>/cssd/):

2010-10-07 20:42:22.264: [ GPnP][2924105472]clsgpnp_profileCallUrlInt: [at clsgpnp.c:2195] Result: (13) CLSGPNP_NO_DAEMON. Error get-profile CALL to remote "ipc://GPNPD_nydcjsadsa01" disco ""
2010-10-07 20:42:22.264: [ GPnP][2924105472]clsgpnp_getProfileEx: [at clsgpnp.c:540] Result: (13) CLSGPNP_NO_DAEMON. got profile (nil)
2010-10-07 20:42:22.264: [ GPnP][2924105472]clsgpnp_getProfileEx: [at clsgpnp.c:546] Result: (13) CLSGPNP_NO_DAEMON. Can't get GPnP service profile from local GPnP daemon
2010-10-07 20:42:22.264: [ default][2924105472]Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).
2010-10-07 20:42:22.264: [ CSSD][2924105472]clsgpnp_getProfile failed, rc(13)

The gpnpd.log (located in: $GI_HOME/log/<hostname>/gpnp/) shows that gpnpd comes up successfully on the local node but crashes a few seconds later after trying to establish a TCP connection to the remote server.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms