My Oracle Support Banner

OID Ldap Command Line Tools Work Against the OID Physical Hostname, But Hang or Fail Against a Front-End Load Balancer (LBR) With sgslufread: Hard error on read, OS error = 104 / ldap_bind: Can't contact LDAP server (Doc ID 1495900.1)

Last updated on JULY 06, 2021

Applies to:

Oracle Internet Directory - Version 9.0.4 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) command line ldap tools work fine using the OIDs physical hostnames or IP addresses, e.g.:

ldapbind -h <OID_HOSTNAME> -p <OID_PORT> -D cn=orcladmin -w <PASSWORD>
bind successful


After adding a load balancer (LBR) in front of the OIDs, the same ldap commands now either hang or fail against the LBR hostname:

ldapbind -h <LBR_HOSTNAME> -p <LBR_PORT> -D cn=orcladmin -w <PASSWORD>
<Hangs>

Or:

ldapbind -h <LBR_HOSTNAME> -p <LBR_PORT> -D cn=orcladmin -w <PASSWORD>
sgslufread: Hard error on read, OS error = 104
ldap_bind: Can't contact LDAP server

ldapcompare -h <LBR_HOSTNAME> -p <LBR_PORT> -D cn=orcladmin -w <PASSWORD> -b "cn=<USERNAME>,cn=users,dc=<COMPANY>,dc=com" -a userpassword -v <user password>
sgslufread: Hard error on read, OS error = 104
ldap_simple_bind_s: Can't contact LDAP server

 

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.