[SERVER-40760] Unable to start mongo after unclean shutdown Created: 22/Apr/19 Updated: 23/Apr/19 Resolved: 23/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jeff langston | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Greetings, I have a mongo instance that had ran out of storage room. Is the error recoverable? I have attempted to run mongod with the --repair option, but both yield similar results: } |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 23/Apr/19 ] |
|
Jeff, Unfortunately, there's nothing more we can do in the case. You may wish to try running a - In the future, we strongly recommend utilizing a replica set as one node failing can still be recoverable by syncing from another member of the set. Danny |
| Comment by jeff langston [ 23/Apr/19 ] |
|
Hi Danny, Thank you for your response. Unfortunately I still get the following: mongod --dbpath /mongodb/data } ***aborting after fassert() failure 2019-04-23T21:28:51.963+1000 F - [initandlisten] Got signal: 6 (Aborted).
I get a similar response when I run with the --repair option.
Just to make sure I copied the files over I ran md5sum: md5sum /mongodb/data/WiredTiger.wt md5sum /mongodb/repair/WiredTiger.wt
md5sum /mongodb/data/WiredTiger.turtle md5sum /mongodb/repair/WiredTiger.turtle
-Jeff |
| Comment by Danny Hatcher (Inactive) [ 22/Apr/19 ] |
|
Hello Jeff, I've attached a repair attempt: repair-attempt.tar Thanks, Danny |