[SERVER-77820] file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value: Created: 05/Jun/23 Updated: 29/Jun/23 Resolved: 29/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Volodymyr Victorovich | Assignee: | Chris Kelly |
| 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, We had a major power outage and it knocked down our mongo db running in docker as part of a stack. Now it won't come back up. Mongo had it's own volume mounted to /data/db.
I also ran this command "mongod --repair --dbpath /data/db"
|
| Comments |
| Comment by Chris Kelly [ 29/Jun/23 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
MongoDB 3.6 reached end of life in April 2021 and is no longer supported. The oldest supported version of MongoDB is currently 4.4. I am going to close this ticket, but leave some final remarks that may be of assistance. If --repair is failing on 3.6, there have been updates made to it over the years, and there is some possibility --repair will work on a newer version of MongoDB. Failing that, you should first consider resyncing the affected node from a good node. To avoid a problem like this in the future, it is our strong recommendation to:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Volodymyr Victorovich [ 07/Jun/23 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The entire log is in the file in the mongod.log mongod --dbpath . --repair
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Chris Kelly [ 06/Jun/23 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair using the latest patch release of your version of MongoDB. Since you haven't specified what version you are using, I cannot advise the exact one and I'm not sure if you're using the latest patch release already. In the event that a --repair operation is unsuccessful, then please also provide:
Christopher
|