10g OID / SSO / OC4J_SECURITY Fail to Start. Error in OID Log File: "sgslunlListen: Bind failed on communication endpoint (125)"
(Doc ID 825550.1)
Last updated on AUGUST 27, 2019
Applies to:
Oracle Internet Directory - Version 10.1.2 to 10.1.4 [Release 10gR2 to 10gR3]Oracle Application Server Single Sign-On - Version 10.1.2 to 10.1.4 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
Symptoms
Error received in OID oidldapd01.log file:
2009/05/14:05:12:01 * Main:0 * sgslunlListen: Bind failed on communication endpoint (125)
2009/05/14:05:12:01 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port
2009/05/14:05:12:21 * Main:0 * sgslunlListen: Bind failed on communication endpoint (125)
2009/05/14:05:12:21 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port
2009/05/14:05:12:01 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port
2009/05/14:05:12:21 * Main:0 * sgslunlListen: Bind failed on communication endpoint (125)
2009/05/14:05:12:21 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port
OID is shown as ALIVE in the opmnctl status command output table, but ldapbind fails with "Cannot connect to the LDAP server" error.
Unable to start the OID and OC4J_SCURITY services.
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 |