[SERVER-48009] WiredTiger Error Created: 07/May/20 Updated: 06/Dec/22 Resolved: 11/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sts BMU | Assignee: | Backlog - Triage Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | repair, repairDatabase | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu, Docker |
||
| Attachments: |
|
| Assigned Teams: |
Server Triage
|
| Participants: |
| Description |
|
Hello, I have some error with MongoDB starting on Docker following server restart. Could you suggest me about fix? Here is the logs from system:
|
| Comments |
| Comment by Carl Champain (Inactive) [ 11/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Glad it worked! I will close this ticket. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Sts BMU [ 09/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Carl, I have managed to run repair from correctly by moving data folder to host. So basic solution for this issue was mongod --repair. Overall, I still need to check for completeness of data but repair did its job. Thank you for your time! Regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Sts BMU [ 09/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I have managed to run repair and start the MongoDB container but all my collections are gone. Could you suggest me what to do?
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Carl Champain (Inactive) [ 08/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Did you do mongo --repair or mongod --repair?
Thank you, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Sts BMU [ 08/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Carl,
Thanks for response! I have tried to run repair with following command: docker run --rm --volumes-from mydatabase mongo --repair But system returns exactly same logs as for startup. What do you think? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Carl Champain (Inactive) [ 07/May/20 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. Can you please try mongod --repair using the latest version of MongoDB? Thank you, |