[SERVER-26103] WiredTiger.wt: encountered an illegal file format or internal value Created: 14/Sep/16 Updated: 14/Oct/21 Resolved: 15/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Price | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rpo, rps, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Hello, so after a bad server/mongod shutdown, I am unable to restart Mongod. I'm 99% confident that my issue is that same as This one. Like the above thread, I've uploaded my WiredTiger.* files in the hopes that someone can respond with fixed WiredTiger.* files. I would be extremely grateful...thank you! If anyone has any further questions, feel free to ask. Thank you!! |
| Comments |
| Comment by Edwin Zhou [ 14/Oct/21 ] |
|
Can you please file a new SERVER ticket with your issue so we can better track your particular case? Thanks! |
| Comment by pinoy cao [ 11/Oct/21 ] |
|
Hi Thomas @kelsey.schubert, I have the same problem with mongo v3.4 now Kind regards, Pinoy |
| Comment by Kelsey Schubert [ 15/Sep/16 ] |
|
Hi mattprice09, I'm glad the repair was successful! Unfortunately, I cannot share the procedure to repair these files at this time, but I can point you to an open ticket to make the --repair operation more robust with WiredTiger. Please feel free to vote for Kind regards, |
| Comment by Matt Price [ 15/Sep/16 ] |
|
That worked! Everything is all up and running now. Thanks a ton!! I'm not sure if this is something you can share or not, but what did you do to the files to remove the corruption? Have a good one, |
| Comment by Kelsey Schubert [ 15/Sep/16 ] |
|
Hi mattprice09, I've attached repair_attempt.tar.gz Thank you, |
| Comment by Kelsey Schubert [ 15/Sep/16 ] |
|
Thanks for the additional information, mattprice09. I'm reopening to take another look. |
| Comment by Matt Price [ 15/Sep/16 ] |
|
Hi Thomas, After double-checking permissions of my .sock file in /tmp/.sock and running `sudo mongod`, I still get the following error:
Thanks Thomas, |
| Comment by Kelsey Schubert [ 15/Sep/16 ] |
|
Hi mattprice09, Thank you for uploading the logs. I have examined them and do not see any evidence of WiredTiger corruption. This issue is unrelated to The fatal assertion you are seeing, 28578, instead indicates that the mongod is unable to unlink the socket file. I would recommend ensuring that the permissions on the socket file are correct to resolve this issue. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by Matt Price [ 14/Sep/16 ] |
|
Thanks for the response, Thomas. I just uploaded the mongod.log file to the portal you linked. -Matt |
| Comment by Kelsey Schubert [ 14/Sep/16 ] |
|
Hi mattprice09, Thanks for reporting this issue. Would you please upload the complete logs of the affected mongod so we can investigate this issue? Please be sure to include the events preceding the unclean shutdown and subsequent attempts to restart. I have created a secure upload portal here for you to use. Files uploaded to this portal will only be visible to MongoDB employees and are routinely deleted after some time. Thank you, |