My Oracle Support Banner

OPMN Fails to Start OID 10.1.4.x on RHEL / OEL 5 - oidldapd crashes with SIGFPE (Floating point exception) (Doc ID 1142566.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jan-2013***


Oracle Internet Directory (OID) was installed successfully on a Linux Redhat 5 or OEL 5 server and was running without issues. 

Now OID fails to start using using OPMN. 

There are no errors in the oidmon.log.

opmnctl output:

$ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OID
opmnctl: starting opmn managed processes...
opmn id=oraaps-pun03:6201
0 of 1 processes started.


--> Process (pid=24595)
failed to start a managed process after the maximum retry limit
The $ORACLE_HOME/ldap/log/oidldapd01.log file shows repeated errors as follows:
2010/06/29:10:48:37 * ProcessDispatcher:1 * sgslupsCheckProcess: sigsend to pid 10623 failed, os error = 3
2010/06/29:10:48:37 * ProcessDispatcher:1 * Server with PID = 10623 is not running
2010/06/29:10:48:38 * ProcessDispatcher:1 * Starting OIDLDAP Server,PID=10625
2010/06/29:10:48:38 * ProcessDispatcher:1 * sgslupsCheckProcess: sigsend to pid 10625 failed, os error = 3
2010/06/29:10:48:38 * ProcessDispatcher:1 * Server with PID = 10625 is not running
The oidmon and oidldapd processes appear to be running on the server.
Example 'ps -ef | grep oid' output:

oracle 17953 1 1 13:16 ? 00:00:00 /u01/oracle/oid//bin/oidmon connect=orcl opmnuid=1 start
oracle 17957 1 3 13:16 ? 00:00:00 /u01/oracle/oid//bin/oidldapd connect=orcl -p 389 -i 1 -conf 0 -sport 636 -sslenable 2 key=1176615607

$ORACLE_HOME/ script has been run to set the permissions of the oidldapd executable correctly and $ORACLE_HOME/bin/oidldapd is owned by root with sticky bit set.

Steps to reproduce

1. Stop all processes running from the OID ORACLE_HOME.
2. Run: $ORACLE_HOME/opmn/bin/opmnctl start: completes successfully.
3. Run: $ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OID: fails with error 'failed to start a managed process after the maximum retry limit'.


New software has been installed on the server.


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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.