[SERVER-7038] Mongo 2.2.0 Replica Set Primary Node Crashes Created: 13/Sep/12  Updated: 08/Mar/13  Resolved: 05/Nov/12

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

Type: Bug Priority: Major - P3
Reporter: Vinayak Javaly Assignee: Kristina Chodorow (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

EC2


Operating System: Linux
Participants:

 Description   

We recently upgraded from 2.0 to 2.2, and several of our replica sets have had 1 or more nodes crash. An example is, in a 6-node replica set, the primary has crashed twice today. Bottom of mongod.log output below:
**********
:
:
Thu Sep 13 16:38:58 [rsHealthPoll] replSet member EC2_PUBLIC_DNS_HOSTNAME:27017 is up
Thu Sep 13 16:38:58 [rsHealthPoll] replSet member EC2_PUBLIC_DNS_HOSTNAME:27017 is now in state SECONDARY
Thu Sep 13 16:38:58 [rsMgr] replSet warning caught unexpected exception in electSelf()
Thu Sep 13 16:38:58 Invalid access at address: 0x7fc305dde6f0 from thread:

Thu Sep 13 16:38:58 Invalid access at address: 0x7fc305dde720 from thread:

Thu Sep 13 16:38:58 Got signal: 11 (Segmentation fault).

Thu Sep 13 16:38:58 Got signal: 11 (Segmentation fault).

Thu Sep 13 16:38:58 Backtrace:
0xade6e1 0x5582d9 0x558862 0x7fc98faff500 0x7fc305dde6f0
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xade6e1]
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x5582d9]
/usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x262) [0x558862]
/lib64/libpthread.so.0(+0xf500) [0x7fc98faff500]
[0x7fc305dde6f0]
**********



 Comments   
Comment by Kristina Chodorow (Inactive) [ 14/Sep/12 ]

Can you attach a larger chunk of the log? (The last couple hundred lines would be helpful.) Can you also attach the log from another time it crashed?

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