[SERVER-28226] WT Crash Created: 07/Mar/17 Updated: 15/Nov/21 Resolved: 21/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | hu dai | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envm, rns, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS release 6.6 (Final) |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
| Comments |
| Comment by Mark Agarunov [ 21/Mar/17 ] | |||||||
|
Hello netwrom, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Thanks, | |||||||
| Comment by Mark Agarunov [ 14/Mar/17 ] | |||||||
|
Hello netwrom, Thank you for the response. If possible, could you provide the complete logs from mongod when you attempt to start it? The errors and startup info in the logs may shed some light on the cause of this issue. Thanks, | |||||||
| Comment by hu dai [ 14/Mar/17 ] | |||||||
|
hi mark.agarunov if MongoDB Crashed, I Can't start MongoDB Server,you method may be I can not use for me | |||||||
| Comment by Mark Agarunov [ 07/Mar/17 ] | |||||||
|
Hello netwrom, Please note that the method described in the linked blog post is not supported and may lead to further corruption in some circumstances. If you would like to attempt to repair the database, the steps would be as follows:
This can be found by running the following in the mongo shell and comparing the uri with the index that is logged, in this case index-84-9204097186848499981:
Thanks, | |||||||
| Comment by hu dai [ 07/Mar/17 ] | |||||||
|
because I used qingclould service, maybe qingclould disk subsystem have problem | |||||||
| Comment by Alexander Gorrod [ 07/Mar/17 ] | |||||||
|
This error indicates that there was a data corruption in your disk subsystem that corrupted the content of your database. When MongoDB encounters a data corruption, it shuts down immediately in order to avoid introducing more wide-spread corruption of data. Our recommended resolution in this case is to:
Let us know if neither of those are options for you, and we will see if we can help further. |