My Oracle Support Banner

OID 11g - Fails To Start With Error "Bind Failed" "OS Error=(125)" on Solaris Platform (Doc ID 2345527.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Internet Directory - Version 11.1.1.9.0 to 11.1.1.9.0 [Release 11g]
Oracle Solaris on SPARC (64-bit)

Symptoms

Oracle Internet Directory (OID) 11g 11.1.1.9.0 fails to start with error "Bind failed" "OS error=(125)".

The error is reported in the oidmon log as follows:

[2017-05-18T11:22:19.882289-04:00] [OID] [TRACE:16] [] [OIDMON] [host: oidhost] [pid: 15317] [tid: 0] Guardian: sgslupsCheckProcess: is not oiddispd process
[2017-05-18T11:22:19.882631-04:00] [OID] [TRACE:16] [] [OIDMON] [host: oidhost] [pid: 15317] [tid: 0] Guardian: sgslupsCheckProcess: is not oiddispd process
[2017-05-18T11:22:19.882953-04:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: oidhost] [pid: 15317] [tid: 0] Guardian: Killed process pid = 18365

The error in file oiddispd01.log is reported as follows:

[2017-05-18T11:22:20.530366-04:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 18643] [tid: 0] Main:: sgslun6lBind: IPV6 Bind failed (port=3136), OS error=(125)
[2017-05-18T11:22:20.530528-04:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 18643] [tid: 0] Main:: sgslunlListen: IPV4 Bind failed (port=3136), OS error=(125)
[2017-05-18T11:22:20.530634-04:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 18643] [tid: 0] Main:: gslmBind2Port: INFO * Bind Failed
[2017-05-18T11:22:20.530799-04:00] [OID] [ERROR:8] [23001] [OIDLDAPD] [host: oidhost] [pid: 18643] [tid: 0] Main:: OID is unable to come up using the configured port.
[2017-05-18T11:22:20.856547-04:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host: oidhost] [pid: 18361] [tid: 1] ProcessDispatcher: sgsluscSendPort: sendmsg failed, OS ERROR = 32
[2017-05-18T11:22:20.856843-04:00] [OID] [ERROR:8] [23124] [OIDLDAPD] [host: oidhost] [pid: 18361] [tid: 1] ProcessDispatcher: The server with Process ID = 18365 is not running.

Issue is not reproduced in earlier versions such as 11.1.1.6 or 11.1.1.7.0, and it is specific to OID 11.1.1.9.0 and Solaris platform.

OID fails when attempting to bind its LDAP and LDAPS ports; returning error: 125, EADDRINUSE.

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


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