[SERVER-53610] system crashed; mongodb kept restarting but could never start Created: 04/Jan/21 Updated: 08/Feb/21 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Higgins | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
was running on OSX. Docker shows this: |
||
| Attachments: |
|
| Participants: |
| Description |
| Comments |
| Comment by Edwin Zhou [ 08/Feb/21 ] |
|
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Edwin Zhou [ 26/Jan/21 ] |
|
Were you successful in restoring your node? We'd like to hear back from you! Thanks, |
| Comment by Edwin Zhou [ 12/Jan/21 ] |
|
Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair using the latest version of MongoDB. I've also attached a repair attempt of the files you provided as WiredTiger-repair.tar.gz Best, |