[SERVER-38283] file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Created: 28/Nov/18 Updated: 03/Dec/18 Resolved: 03/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | John Narma | 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 |
|
Hello. I met a problem in mongoDB on docker container. MongoDB can't start with the following error message. Can I solve this? Thank you.
|
| Comments |
| Comment by John Narma [ 03/Dec/18 ] | |
|
Thanks for reply. I deleted journal files and started with version 3.4.8. The problem is solved. Thank you very much. | |
| Comment by Danny Hatcher (Inactive) [ 30/Nov/18 ] | |
|
Hello John, The repair functionality actually runs before any kind of version checks. The logs indicate that repair fixed the corruption then cleanly exited because oof the version. If you start the data files now with the original 3.4.8 binaries, does everything work? If you receive an "unsupported WiredTiger file version" error, please delete the journal files and try to start the process again. Thank you, Danny | |
| Comment by John Narma [ 29/Nov/18 ] | |
|
Thanks for your help. In my environment, the mongoDB is single-node. So I tried run "mongod --repair" (before trying it, I took a full-copy of dbpath) but repair didn't work. I also tried in version 3.6 and latest(4.0.4). In version 4.0.4, mongod says
Can I upgrade my data file to version 3.6 with mongod not running? Thank you.
| |
| Comment by Danny Hatcher (Inactive) [ 28/Nov/18 ] | |
|
Hello, To resolve this issue, I would recommend a clean resync from a node that is not affected. If that is not possible, I would recommend executing repairDatabase. Thank you, Danny |