[SERVER-17824] Mongo server seagfault Created: 31/Mar/15  Updated: 31/Mar/15  Resolved: 31/Mar/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.0.0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Umputun Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File qfshc-20150331-134840-cdz5c.png    
Issue Links:
Duplicate
duplicates SERVER-17613 Unable to start mongod after unclean ... Closed
Operating System: ALL
Steps To Reproduce:

I have stopped mongo secondary member (in container) and can not start it anymore.

Participants:

 Description   

Attempt to restart mongo replica member (secondary) leads to segfault



 Comments   
Comment by Ramon Fernandez Marina [ 31/Mar/15 ]

umputun, looks like you've run into SERVER-17613, which may happen after an unclean shutdown.

SERVER-17613 is fixed in the upcoming 3.0.2 release, but since we haven't published it yet here's a workaround to allow you to get past this problem:

  • Download a recent nightly build on the v3.0 branch
  • Temporarily replace your 3.0.0 binary with the one from the nightly build
  • Start your MongoDB instance with this new binary, and then do a clean shutdown by running db.shutdownServer() in the shell
  • Revert back to the 3.0.0 binary

The alternative, which may take longer but is much simpler, is to wipe out the data in this secondary and resync the data from the primary.

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