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:
} }
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]
===
- duplicates
-
SERVER-7061 mongos can use invalid ptr to master conn when setShardVersion fails
-
- Closed
-
- is related to
-
-
- Closed
-