[SERVER-28168] Cannot start or repair mongodb after unexpected shutdown. Created: 02/Mar/17 Updated: 15/Aug/17 Resolved: 24/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.13, 3.4.4, 3.5.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | kurevo18 | Assignee: | Keith Bostic (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage 2017-04-17, Storage 2017-05-08 | ||||||||
| Participants: | |||||||||
| Description |
|
Hello, i'm running mongodb on VPS, here is the version: MongoDB shell version v3.4.1 I had an unexpected shutdown, i looked up the log and i can see following:
I get exactly same message when i try to do mongod --repair --dbpath /var/lib/mongodb Someone please help!!! I will be thrown out from work... |
| Comments |
| Comment by Githook User [ 13/Apr/17 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Import wiredtiger: f5c08e2b5f02805b062888d45c9eca19af175f7e from branch mongodb-3.2 ref: d48181f6f4..f5c08e2b5f
|
| Comment by Githook User [ 13/Apr/17 ] |
|
Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith.bostic@mongodb.com'}Message: Panic if there's an error in reading/writing from/to the turtle file, |
| Comment by Githook User [ 12/Apr/17 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Import wiredtiger: cb16839cfbdf338af95bed43ca40979ae6e32f54 from branch mongodb-3.4 ref: cc2f15f595..cb16839cfb
|
| Comment by Githook User [ 12/Apr/17 ] |
|
Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith.bostic@mongodb.com'}Message: Panic if there's an error in reading/writing from/to the turtle file, |
| Comment by Githook User [ 31/Mar/17 ] |
|
Author: {u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}Message: Import wiredtiger: af735d14a603a6ef6256a6685f09ec13755a5024 from branch mongodb-3.6 ref: cc2f15f595..af735d14a6
|
| Comment by Githook User [ 27/Mar/17 ] |
|
Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith.bostic@mongodb.com'}Message: Panic if there's an error in reading/writing from/to the turtle file, |
| Comment by Keith Bostic (Inactive) [ 07/Mar/17 ] |
|
kurevo18, we've managed to reproduce this one locally, I believe the problem is the database has a zero-length WiredTiger.turtle file. Can you please confirm that for us by running ls -la on the dbpath? As previously suggested, that's likely due to filesystem corruption. |
| Comment by Keith Bostic (Inactive) [ 06/Mar/17 ] |
|
Hi kurevo18, I thought of one approach that might help: can you run your mongod command under strace, and upload that output, so we can figure out what file isn't being found when mongod starts? To be clear, I think it's likely anonymous.user is correct and there's file system corruption, but we can debug this a little further if you'd like. |
| Comment by Kelsey Schubert [ 02/Mar/17 ] |
|
Hi kurevo18, This error suggests that the filesystem was corrupted when the VPS unexpectedly shutdown. Unfortunately, when MongoDB encounters corruption of this nature, there is little it can do to recover. In this case, I would recommend restoring from a backup if possible. Kind regards, |