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

Mongos crashed because of mongod cannot reach.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.2.0-rc0
    • Component/s: Stability
    • Environment:
      Ubuntu 12.04 LTS
      Linux yz-uc-core-a08 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
    • ALL

      Mongos crashed! Because of 192.168.130.12:15002 connot reached.
      192.168.130.12:15002 mongod crashed because of "SERVER-6538"

      Fri Jul 20 17:32:47 [ReplicaSetMonitorWatcher] reconnect 192.168.130.18:15002 failed couldn't connect to server 192.168.130.18:15002
      Fri Jul 20 17:32:47 [WriteBackListener-192.168.130.12:15002] DBClientCursor::init call() failed
      Fri Jul 20 17:32:47 [WriteBackListener-192.168.130.12:15002] WriteBackListener exception : DBClientBase::findN: transport error: 192.168.130.12:15002 ns: admin.$cmd query: { writebacklisten: ObjectId('5008fe6b0e2a603cc3f9b46d'), $auth: { local:

      { __system: 2 }

      } }
      Fri Jul 20 17:32:48 [conn28] got not master for: 192.168.130.12:15002
      Received signal 11
      Backtrace: 0x69f2a5 0x7f5ef462f4c0 0x7f5ed005d928
      /home/mongo/.bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x69f2a5]
      /lib/x86_64-linux-gnu/libc.so.6(+0x364c0)[0x7f5ef462f4c0]
      [0x7f5ed005d928]
      ===

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            xjtyfq NOVALUE yangfenqiang
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: