[SERVER-53424] WiredTiger has failed to open its metadata Created: 17/Dec/20 Updated: 07/Jan/21 Resolved: 07/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.0.21 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Camilo Barreto | Assignee: | Eric Sedor |
| 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!, Im new, sorry if i don't understand and my english skills... In short: due a crash/error in GCP, my mongo pod was restarted, this caused that when starting the mongo the following error appeared:
I don't know why it gives a version problem. maybe mongo version got updated on GCP reboot. So, I downloaded the /data/bin folder with the mongo data and installed Mongo Server 4.0 trying to retrieve my information. When I try to start the mongo I get the following error:
When I run the "mongod --dbpath /data/db --repair" command it shows the following:
If anyone can help me I appreciate it, thank you. |
| Comments |
| Comment by Eric Sedor [ 07/Jan/21 ] | |
|
Thanks for following up camilobarreto2201@gmail.com, and glad to hear; be well! | |
| Comment by Camilo Barreto [ 07/Jan/21 ] | |
|
Thanks for the answer, I already solved my problem running the following command in GCP:
then i restarted the pod and it started successfully... I appreciate the answer, I hope this can help more people. Thanks! | |
| Comment by Eric Sedor [ 05/Jan/21 ] | |
|
Hi camilobarreto2201@gmail.com, and thanks for your patience with the delay. I think your suspicion about a mongo update on reboot seems reasonable. So it sounds like the timeline of the issue is this: 1) Server is running 4.0.21 until a restart. Presumably this is an unclean shutdown. Is that right? If so, then as a first step, please make sure you are preserving a copy of the dbpath from after the failed 4.4 startup attempt (step 2). Work off of a copy.
If this does not work, can you please provide the following logs in file form:
Unfortunately, the screenshots are not as helpful as the log files themselves would be. I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. |