OID 11g Errors on Solaris / Sun Clustered Hosts: gsluslldConnect: Failed to connect <OIDHOST1_ZONE2>:<PORT> / Replication Configuration Hangs
(Doc ID 1600332.1)
Last updated on MARCH 24, 2021
Applies to:
Oracle Internet Directory - Version 11.1.1 and laterOracle Solaris on SPARC (64-bit)
Sun SPARC Sun OS
Symptoms
Oracle Internet Directory (OID) 11g, i.e., 11.1.1.7.0.
OID has been installed in only one of the nodes of a two node Sun clustering software (e.g., Sun cluster 3.3).
Each node has a zone (e.g., <OID_HOST1_ZONE1> and <OIDHOST1_ZONE2>), and <OID_VIRTUAL_HOSTNAME> is the VIP of the cluster.
OID is running on <OIDHOST1_ZONE1> (while <OIDHOST1_ZONE2> is the inactive node).
OID is installed and running on <OIDHOST1_ZONE1>. Nothing is installed or running on <OIDHOST1_ZONE2>.
Installed OID on <OIDHOST1_ZONE1> as if standalone, following the documentation. (Also installed Weblogic using Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1 (10.3.6).)
OID errors on clustered hosts.
Repeated connection failures reported in OID logs.
The size and number of OID logs keep growing very large.
The OID ldap server log is filled with the following error:
gsluslldConnect: Failed to connect <OIDHOST1_ZONE2>:<PORT>
gsluslldConnect: Failed to connect <OIDHOST1_ZONE2>:<PORT>
And oidmon log reports:
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: <OIDHOST1_ZONE1>] [pid: 11604] [tid: 0] Guardian: gslsgrnPing: Failed to connect to OID host:<OIDHOST1_ZONE2> port:<PORT> ssl:0
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: <OIDHOST1_ZONE1>] [pid: 11604] [tid: 0] Guardian: gslsgldConnect: Failed to connect <OIDHOST1_ZONE2>:<PORT>
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: <OIDHOST1_ZONE1>] [pid: 11604] [tid: 0] Guardian: gslsgrnPing: Failed to connect to OID host:<OIDHOST1_ZONE2> port:<PORT> ssl:0
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: <OIDHOST1_ZONE1>] [pid: 11604] [tid: 0] Guardian: Shutting down
However, OID should not be trying to connect to the inactive node in the first place, as there is nothing running on this second node.
In addition, setting up replication using the Replication Wizard in Enterprise Manager (EM) Fusion Middleware (FMW) Control with another cluster (e.g., oid2) just hangs.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |