Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23528

Primary restarts itself unexpectedly

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • 2.6.4
    • None
    • None
    • ALL

    Description

      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?

      Attachments

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey Schubert
            koitautomation@altegrity.com Kroll Ontrack
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: