[SERVER-29869] DB with WiredTiger engine fails to recover Created: 27/Jun/17 Updated: 29/Jul/17 Resolved: 28/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Exozet | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
After a (clean) server shutdown/reboot our MongoDB-Server fails to start with the follow messages:
We've tried different repair attempts but all of them failed. If you need any further details or files i'll provide them as soon as possible. Thanks in advance. |
| Comments |
| Comment by Jan Schütze [ 28/Jun/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thank you! It's working again! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jan Schütze [ 27/Jun/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hey Mark, I work at Exozet and I am happy about your quick response! A quick test on a docker container with mongodb 3.4.1 and the dataset, showed this response:
Does this help you to track down the issue? [edit] I build an docker image with wiredtiger 1.8.0 wt cli tool and ran salvage command on the index checksum file in question and was able to launch mongodb right after that again. Will test tomorrow, if the database works as expected again on our production environment. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Mark Agarunov [ 27/Jun/17 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello xoz, Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:
Thanks, |