-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.5.5
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
I'm running 2.5.5 as a hidden replica in a replSet that is composed of 2.4.6 instances. About once a day the server segfaults. I've included the backtrace and some of the log prior to the segfault. Let me know if I there is any additional information I can provide that would be useful.
Invalid access at address: 0 from thread: rsSyncNotifier Got signal: 11 (Segmentation fault). Backtrace: 0x114d711 0x751cba 0x757402 0x7f090424dcb0 0x1100c2d 0x1102086 0x1102671 0x7b20a5 0x7dc027 0x7dc /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x114d711] /usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x3ba) [0x751cba] /usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x282) [0x757402] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f090424dcb0] /usr/bin/mongod(_ZN5mongo13MessagingPort4recvERNS_7MessageE+0x87d) [0x1100c2d] /usr/bin/mongod(_ZN5mongo13MessagingPort4recvERKNS_7MessageERS1_+0x36) [0x1102086] /usr/bin/mongod(_ZN5mongo13MessagingPort4callERNS_7MessageES2_+0x31) [0x1102671] /usr/bin/mongod(_ZN5mongo18DBClientConnection4callERNS_7MessageES2_bPSs+0x55) [0x7b20a5] /usr/bin/mongod(_ZN5mongo14DBClientCursor11requestMoreEv+0x397) [0x7dc027] /usr/bin/mongod(_ZN5mongo14DBClientCursor4moreEv+0x4d) [0x7dc4ed] /usr/bin/mongod(_ZN5mongo7replset14BackgroundSync9markOplogEv+0xb3e) [0xd8d00e] /usr/bin/mongod(_ZN5mongo7replset14BackgroundSync14notifierThreadEv+0x15e) [0xd8f8ce] /usr/bin/mongod() [0x1192459] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f0904245e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f09035583fd]
There were also some interesting logs prior to the segfault:
2014-02-06T13:34:45.883-0500 [rsBackgroundSync] Socket recv() timeout 10.145.170.96:27017 2014-02-06T13:34:45.883-0500 [rsBackgroundSync] SocketException: remote: 10.145.170.96:27017 error: 9001 socket exception [RECV_TIMEOUT] server [10.145.170.96:27017] 2014-02-06T13:34:45.883-0500 [rsBackgroundSync] DBClientCursor::init call() failed 2014-02-06T13:35:08.642-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:08.911-0500 [rsSyncNotifier] replset setting oplog notifier to [server]:27017 2014-02-06T13:35:08.914-0500 [rsSyncNotifier] upstream updater is unsupported on this version 2014-02-06T13:35:08.922-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:08.995-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.174-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.219-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.240-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.250-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.259-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.269-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.294-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.307-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.322-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.334-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.344-0500 [rsBackgroundSync] upstream updater is unsupported on this version 2014-02-06T13:35:09.391-0500 [rsBackgroundSync] upstream updater is unsupported on this version