OUD Process Fails to Start and Error Includes Incorrect LDAP Port Number: "LDAP Connection Handler" ... "was unable to bind to 0.0.0.0:389: IOException(Address already in use)"
(Doc ID 2930790.1)
Last updated on FEBRUARY 24, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Unified Directory (OUD) Server or Proxy fails to start with error:
Where the OUD LDAP port number configured is Not 389 as shown in the error above. The port number in the error is a typical/default port number from the "LDAP Connection Handler" configuration section of the $ORACLE_HOME/oud/config/config.ldif template file.
Both, the configured LDAP port number and the LDAP port number shown in the error, have been verified to be clear/free with "netstat -an | grep <port number>" command prior to starting OUD.
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 |