OUD11g - Server Instance Consumes 100% CPU, Becomes Unresponsive and Does Not Accept Connections

(Doc ID 2312410.1)

Last updated on OCTOBER 03, 2017

Applies to:

Oracle Unified Directory - Version 11.1.2.2.0 and later
Information in this document applies to any platform.

Symptoms

OUD Server is consuming 100% CPU, is unresponsive and not accepting connections. 

OUD Server ran for an hour exceeding 100% of CPU usage, then dropped down to approximately 2% CPU usage but still would not accept connections.

The following type of messages can be seen in the logs:

 [14/Sep/2017:11:02:16 -0600] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.replication.server.ReplicationServer (alert type org.opends.server.replication.ServerMissingTrimmedChanges, alert ID 14942419): Alert in replication server app_1:8989 with server id 22578: in domain dc=example,dc=com, the remote server app_2:8989 with server id 6205 is missing some changes from directory server id 399 that have been purged from the changes database because they were too old. This may happen if the remote server has been stopped for too much time or if it is very late replaying the changes. If the remote server is a directory server, its backend should be re-initialized. If the remote server is another replication server, potentially many directory servers may lack some changes and their backend should be re-initialized
[14/Sep/2017:11:02:16 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942389 msg=Replication Server 6205 app_2:8989 o=internaluser,dc=example,dc=com has badly disconnected from this replication server 22578
[14/Sep/2017:11:02:16 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942389 msg=Replication Server 6205 app_2:8989 cn=schema has badly disconnected from this replication server 22578
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942388 msg=The connection to replication server app_2/<IP>:8989 6205 has been unexpectedly dropped by the replication server for dc=example,dc=com in local server id 12188
[14/Sep/2017:11:02:16 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942388 msg=The connection to replication server app_2/<IP>:8989 6205 has been unexpectedly dropped by the replication server for o=internaluser,dc=example,dc=com in local server id 6610
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942388 msg=The connection to replication server app_2/<IP>:8989 6205 has been unexpectedly dropped by the replication server for cn=schema in local server id 21316
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=NOTICE msgID=15138878 msg=Replication is up and running for domain cn=admin data with replication server id 6205 app_2/<IP>:8989 - local server id is 8559 - data generation is 95401
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942386 msg=Directory server 8559 was attempting to connect to replication server 22578 but has disconnected in handshake phase
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942386 msg=Directory server 8559 was attempting to connect to replication server 22578 but has disconnected in handshake phase
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=NOTICE msgID=15138921 msg=SSL connection attempt from <host_name> (<IP>) failed: Remote host closed connection during handshake
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=NOTICE msgID=15138921 msg=SSL connection attempt from <host_name> (<IP>) failed: Remote host closed connection during handshake
[14/Sep/2017:11:02:51 -0600] category=SYNC severity=NOTICE msgID=15138921 msg=SSL connection attempt from <host_name> (<IP>) failed: Remote host closed connection during handshake
[14/Sep/2017:11:02:52 -0600] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.replication.server.ReplicationServer (alert type org.opends.server.replication.ServerMissingTrimmedChanges, alert ID 14942419): Alert in replication server app_1:8989 with server id 22578: in domain dc=example,dc=com, the remote server app_2:8989 with server id 6205 is missing some changes from directory server id 399 that have been purged from the changes database because they were too old. This may happen if the remote server has been stopped for too much time or if it is very late replaying the changes. If the remote server is a directory server, its backend should be re-initialized. If the remote server is another replication server, potentially many directory servers may lack some changes and their backend should be re-initialized
[14/Sep/2017:11:02:52 -0600] category=SYNC severity=NOTICE msgID=15138913 msg=Replication Heartbeat Monitor for RS <IP>:8989 cn=schema in RS 6205 is closing the session because it could not detect a heartbeat
[14/Sep/2017:11:02:52 -0600] category=SYNC severity=NOTICE msgID=15138913 msg=Replication Heartbeat Monitor for RS <IP>:8989 o=internaluser,dc=example,dc=com in RS 6205 is closing the session because it could not detect a heartbeat
[14/Sep/2017:11:02:52 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942388 msg=The connection to replication server app_2/<IP>:8989 6205 has been unexpectedly dropped by the replication server for cn=admin data in local server id 8559
[14/Sep/2017:11:02:52 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942389 msg=Replication Server 6205 app_2:8989 dc=example,dc=com has badly disconnected from this replication server 22578
[14/Sep/2017:11:03:26 -0600] category=SYNC severity=SEVERE_ERROR msgID=14942389 msg=Replication Server 6205 app_2:8989 cn=admin data has badly disconnected from this replication server 22578

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms