[SERVER-59748] Mongo Service started failed by WiredTiger Error Created: 02/Sep/21 Updated: 23/Sep/21 Resolved: 22/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | F C | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi~ Since 2021-08-26, Mongo Service started failed and i noticed on 2021-09-01, And I don't know why it occurs. I run Mongo-4.4.msi installer to install MongoDB Community Server on Windows 10 x64, it works very well until 2021-08-26. Then i run mongod by manually, it started fail too. I checked the log and find this, but i don't know why it occurs.
I'm attaching the files and log, and I hope it helps. |
| Comments |
| Comment by F C [ 23/Sep/21 ] |
|
Thanks for your help~ I'll protect my data throught these ways in the future. |
| Comment by Edwin Zhou [ 22/Sep/21 ] |
|
I attempted to repair the metadata files that you attached to this ticket. Unfortunately the repair attempt was not successful. To avoid a problem like this in the future, it is our strong recommendation to:
Best, |
| Comment by F C [ 18/Sep/21 ] |
|
Thanks for your reply~ The 'mongod-repair.log' shows the procedure of repairing with '--repair'. I hope it can help. And it's hard to provide other logs on Windows. After all, I hope there's a way to salvage the data by wt tool and the exists data file. I hope it can help~ |
| Comment by Edwin Zhou [ 17/Sep/21 ] |
|
Hi catfishlty1@gmail.com, this error message leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. Our ability to determine the source of this corruption depends greatly on your ability to provide:
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. In the event that a --repair operation is unsuccessful, then please also provide:
Best, |