-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.6.4
-
Component/s: None
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Hi,
We have a three node mongodb cluster (with one arbiter) where every couple of days, mongod service on the primary restarts itself without any apparent reason. I have the following entry in the logs:
2016-04-04T03:34:50.130-0500 [signalProcessingThread] now exiting 2016-04-04T03:34:50.130-0500 [signalProcessingThread] dbexit: 2016-04-04T03:34:50.130-0500 [signalProcessingThread] shutdown: going to close listening sockets... 2016-04-04T03:34:50.130-0500 [signalProcessingThread] closing listening socket: 10 2016-04-04T03:34:50.130-0500 [signalProcessingThread] closing listening socket: 11 2016-04-04T03:34:50.130-0500 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock 2016-04-04T03:34:50.137-0500 [signalProcessingThread] shutdown: going to flush diaglog... 2016-04-04T03:34:50.137-0500 [signalProcessingThread] shutdown: going to close sockets... 2016-04-04T03:34:50.137-0500 [signalProcessingThread] shutdown: waiting for fs preallocator... 2016-04-04T03:34:50.137-0500 [signalProcessingThread] shutdown: lock for final commit... 2016-04-04T03:34:50.137-0500 [signalProcessingThread] shutdown: final commit...
There is nothing before the shutdown signal in the logs (just normal operation). Nothing weird in SAR logs (processor, memory, disk usage normal), no log messages in /var/log/messages. It just looks like as if somebody restarted it manually but in fact nobody did, there is no indication of that in command history.
Mongodb version: 2.6.4-1
OS: RHEL 6.5
Any idea why this is happening?