[SERVER-12004] Mongodb process crash during reelection Created: 08/Dec/13  Updated: 10/Dec/14  Resolved: 17/Jun/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.1
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Dharshan Rangegowda Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AWS


Operating System: ALL
Participants:

 Description   

There were some temporary network issues which caused a leader election. MongoDB crashed during the election

Fri Dec 6 16:23:15.666 [rsMgr] replSet warning caught unexpected exception in electSelf()
Fri Dec 6 16:23:15.691 Invalid access at address: 0 from thread:

Fri Dec 6 16:23:15.691 Got signal: 11 (Segmentation fault).

Fri Dec 6 16:23:15.695 Backtrace:
0xdc7f71 0x6ce459 0x6ce9e2 0x7fc10f8d1500 0xd8c217 0xd8cce4 0xe10879 0x7fc10f8c9851 0x7fc10ec6c11d
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xdc7f71]
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x6ce459]
/usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x262) [0x6ce9e2]
/lib64/libpthread.so.0(+0xf500) [0x7fc10f8d1500]
/usr/bin/mongod(_ZN5mongo13BackgroundJob7jobBodyEN5boost10shared_ptrINS0_9JobStatusEEE+0xa7) [0xd8c217]
/usr/bin/mongod(_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi3mf1IvN5mongo13BackgroundJobENS_10shared_ptrINS7_9JobStatusEEEEENS2_5list2INS2_5valueIPS7_EENSD_ISA_EEEEEEE3runEv+0x74) [0xd8cce4]
/usr/bin/mongod() [0xe10879]
/lib64/libpthread.so.0(+0x7851) [0x7fc10f8c9851]
/lib64/libc.so.6(clone+0x6d) [0x7fc10ec6c11d]



 Comments   
Comment by Ramon Fernandez Marina [ 17/Jun/14 ]

dharshanr@scalegrid.net, we haven't heard back from you for a while so we're going to mark this ticket as resolved. If this is still an issue for you feel free to re-open the ticket.

Comment by Ramon Fernandez Marina [ 30/May/14 ]

Is this still an issue for you? Have you tried upgrading to a newer release? There have been many improvements in this area since 2.4.1, so I'd recommend you upgrade to a newer production release. The latest release in the 2.4 branch is 2.4.10. Can you try the upgrade and let us know if the problem still persists?

Generated at Thu Feb 08 03:27:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.