[SERVER-20751] Cannot start mongod after unclean shutdown Created: 02/Oct/15  Updated: 05/Oct/15  Resolved: 05/Oct/15

Status: Closed
Project: Core Server
Component/s: Admin, WiredTiger
Affects Version/s: 3.0.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Hugo Augusto Freitas do Carmo Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File new_files.tgz     Text File stacktrace.txt    
Operating System: ALL
Participants:

 Description   

We were using MongoDB v3.0.3 when the problem appeared.

We installed WiredTiger from source and tried to run `wt salvage` with no solution.

I'll update the ticket with the commands i've used so far.

My database have 310GB, with zlib compression.

Similar tickets:
https://jira.mongodb.org/browse/SERVER-18850
https://jira.mongodb.org/browse/SERVER-18448

Thank you for your time and consideration.



 Comments   
Comment by Ramon Fernandez Marina [ 05/Oct/15 ]

Thanks for the update spelcaster, and glad to hear the repair attempt worked. I'd strongly encourage you to upgrade to MongoDB 3.0.6 right away, as it fixes a number of known bugs related to unclean shutdowns.

Regards,
Ramón.

Comment by Hugo Augusto Freitas do Carmo [ 05/Oct/15 ]

The commands i've tried before the fix submitted by ramon.fernandez:

mongod --dbpath /data/db --repair --repairpath /data/db1 --directoryperdb \
--storageEngine wiredTiger;
 
sudo -u mongodb -H LD_LIBRARY_PATH=/usr/local/wiredtiger/lib/ \
/usr/local/wiredtiger/bin/wt \
-C "extensions=[/usr/local/wiredtiger/lib/libwiredtiger_zlib.so],log=(path=journal)" \
-h /data/db salvage;

P.S.: This is just FYI, since the problem was already solved.

Comment by Hugo Augusto Freitas do Carmo [ 05/Oct/15 ]

ramon.fernandez, with those files i could start my database.

Thanks,
Hugo do Carmo.

P.S.: By the way thanks for the quick reply.

Comment by Ramon Fernandez Marina [ 02/Oct/15 ]

spelcaster, there are known bugs around this scenario as you've already found. I've attempted a repair and uploaded the result to the new_files.tgz archive. Can you please extract these files on your dbpath, try to start the database again and let us know how it goes?

Thanks,
Ramón.

PS: The known bugs are addressed in the latest stable release (3.0.6 at the time of this writing), so I'd strongly recommend you to upgrade right away.

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