OID Fails to Start with Error sgslunlListen: Bind failed on communication endpoint (98) / (226) or (67) or (125)
(Doc ID 564600.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Internet Directory - Version 10.1.2.0.2 to 10.1.4 [Release 10gR2 to 10gR3]Information in this document applies to any platform.
Symptoms
Unable to start OID services after the machine has been shutdown
"opmnctl status" shows OID as up and running but ldapbind gives "cannot contact the LDAP server" error
"netstat" output doesn't list the OID port, here 3
Errors in oidldapd01.log
98 is for Linux.
226 is for HP.
125 is for Solaris.
Changes
Machine was brought down for maintenance
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 |