OID 11g Errors on Solaris / Sun Clustered Hosts: gsluslldConnect: Failed to connect oid1-z2:3060 / Replication Configuration Hangs (Doc ID 1600332.1)

Last updated on JUNE 30, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Oracle 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., oid1-z1 and oid1-z2), and oid1vip is the VIP of the cluster.
OID is running on oid1-z1 (while oid1-z2 is the inactive node).

OID is installed and running on oid1-z1.  Nothing is installed or running on oid1-z2.

Installed OID on oid1-z1 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:

gslusrnChkConn2RemNode:Connect to OID on host:oid1-z2 failed
gsluslldConnect: Failed to connect oid1-z2:3060
gsluslldConnect: Failed to connect oid1-z2:3060

And oidmon log reports:

[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oid1-z1] [pid: 11604] [tid: 0] Guardian: gslsgldConnect: Failed to connect oid1-z2:3060
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oid1-z1] [pid: 11604] [tid: 0] Guardian: gslsgrnPing: Failed to connect to OID host:oid1-z2 port:3060 ssl:0
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oid1-z1] [pid: 11604] [tid: 0] Guardian: gslsgldConnect: Failed to connect oid1-z2:3060
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oid1-z1] [pid: 11604] [tid: 0] Guardian: gslsgrnPing: Failed to connect to OID host:oid1-z2 port:3060 ssl:0
[2013-11-01T11:36:57-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oid1-z1] [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

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