OID Shuts Down With oidmon.log Error "Time Difference of atleast 250 sec found"
(Doc ID 568027.1)
Last updated on SEPTEMBER 13, 2019
Applies to:
Oracle Internet Directory - Version 10.1.2 and laterInformation in this document applies to any platform.
Symptoms
- Multiple OID instances, located on separate machines, share the same Metadata Repository.
- A single OID instance starts successfully
- When starting a second instance, the first instance shuts down automatically. On the affected server, oidmon.log reports:
date * Time Difference of at least 250 sec found between <OID_HOSTNAME1> and <OID_HOSTNAME2>.
date * Please sync the time between <OID_HOSTNAME1> and <OID_HOSTNAME2>
date * Please adjust the time and restart OID - Comparison of the clocks of the two servers shows that they are significantly out of sync.
When this occurs, messages similar to the following may appear in oidldapd.log:
2011/05/03:11:13:48 * Main:0 * Oid Server Connected to DB store via connect string.
2011/05/03:11:13:48 * Main:0 * OiD LDAP server started.
2011/05/03:11:13:48 * MainController:0 * Creating shared memory segment size 89788
2011/05/03:11:13:48 * DispatcherController:0 * Thread Started
2011/05/03:11:13:49 * DispatcherController:0 * Starting OIDLDAP Server,PID=<PID>
2011/05/03:11:13:49 * DispatcherListener:2 * Thread Started
2011/05/03:11:13:49 * ProcessDispatcher:1 * Thread Started
2011/05/03:11:13:50 * ProcessDispatcher:1 * sgsluscpPollPort: Recvd connect from server process <PID>
2011/05/03:11:13:50 * ProcessDispatcher:1 * sgsluscHsHandShake : Sending Conn ACK to server process <PID>
2011/05/03:11:13:51 * DispatcherListener:2 * Listening on Non SSL port = <OID_PORT> and SSL port = <OID_SSL_PORT>
2011/05/03:11:19:49 * DispatcherListener:2 * WARNING : DispatcherListener : Shutting down
2011/05/03:11:19:49 * ProcessDispatcher:1 * sgsluscSendPort: sendmsg failed, OS ERROR = 32
2011/05/03:11:19:49 * ProcessDispatcher:1 * send port for server PID : <PID> failed
2011/05/03:11:19:49 * ProcessDispatcher:1 * WARNING : Shutting down
2011/05/03:11:19:49 * DispatcherController:0 * Sent SIGTERM to process id = <PID>
2011/05/03:11:19:54 * DispatcherController:0 * sgslupsCheckProcess: sigsend to pid <PID> failed, os error = 3
2011/05/03:11:19:54 * DispatcherController:0 * WARNING : DispatcherController : OiD LDAP server exiting with status -1
2011/05/03:11:20:49 * Main:0 * gslduudSetDBparams * DB parameter _hash_join_enabled is set to false
2011/05/03:11:20:49 * Main:0 *
2011/05/03:11:13:48 * Main:0 * OiD LDAP server started.
2011/05/03:11:13:48 * MainController:0 * Creating shared memory segment size 89788
2011/05/03:11:13:48 * DispatcherController:0 * Thread Started
2011/05/03:11:13:49 * DispatcherController:0 * Starting OIDLDAP Server,PID=<PID>
2011/05/03:11:13:49 * DispatcherListener:2 * Thread Started
2011/05/03:11:13:49 * ProcessDispatcher:1 * Thread Started
2011/05/03:11:13:50 * ProcessDispatcher:1 * sgsluscpPollPort: Recvd connect from server process <PID>
2011/05/03:11:13:50 * ProcessDispatcher:1 * sgsluscHsHandShake : Sending Conn ACK to server process <PID>
2011/05/03:11:13:51 * DispatcherListener:2 * Listening on Non SSL port = <OID_PORT> and SSL port = <OID_SSL_PORT>
2011/05/03:11:19:49 * DispatcherListener:2 * WARNING : DispatcherListener : Shutting down
2011/05/03:11:19:49 * ProcessDispatcher:1 * sgsluscSendPort: sendmsg failed, OS ERROR = 32
2011/05/03:11:19:49 * ProcessDispatcher:1 * send port for server PID : <PID> failed
2011/05/03:11:19:49 * ProcessDispatcher:1 * WARNING : Shutting down
2011/05/03:11:19:49 * DispatcherController:0 * Sent SIGTERM to process id = <PID>
2011/05/03:11:19:54 * DispatcherController:0 * sgslupsCheckProcess: sigsend to pid <PID> failed, os error = 3
2011/05/03:11:19:54 * DispatcherController:0 * WARNING : DispatcherController : OiD LDAP server exiting with status -1
2011/05/03:11:20:49 * Main:0 * gslduudSetDBparams * DB parameter _hash_join_enabled is set to false
2011/05/03:11:20:49 * Main:0 *
If messages similar to the above are seen in oidldapd.log, check oidmon.log to see if this issue is occurring.
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 |