[SERVER-36480] WiredTiger error Created: 07/Aug/18 Updated: 04/Nov/18 Resolved: 01/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Zhang Meng | Assignee: | Nick Brewer |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | envns, rge, trct, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
my mongo DB crashed suddenly and I have no idea how, when I tried to restart it, the error appears:
2018-08-06T22:28:32.699-0700 I CONTROL [initandlisten] db version v3.6.0 , storage: { dbPath: "./db" } } ***aborting after fassert() failure
the attached is the WiredTiger related files, I tried to repair them with: mongod --storageEngine wiredTiger --dbpath ./db --repair --port 27018 but it did not work, could you please help to take a look? Thanks!
|
| Comments |
| Comment by Nick Brewer [ 01/Oct/18 ] |
|
mzhang11 Since there's been no activity on this ticket in some time, I'm going to close it. If you have a chance to update this ticket with the requested platform information, it would greatly assist in our tracking of this issue. Thanks, |
| Comment by Nick Brewer [ 14/Sep/18 ] |
|
mzhang11 So that we can better categorize this issue, can you confirm if this machine is a VM, container, native hardware, etc? Thanks, |
| Comment by Nick Brewer [ 08/Aug/18 ] |
|
mzhang11 There's an internal tool that we use to fix specific instances of WiredTiger metadata file corruption - it's not something we make publicly available at the moment as it can easily be misused. Is this a VM, container, etc? Thanks, Nick |
| Comment by Zhang Meng [ 08/Aug/18 ] |
|
Thanks for your reply, Nick. the power and the storage was fine(another mongo process on the same server was fine), and the log was overwritten when I tried to restart it, so I'm not sure about the root cause... in fact, I have deleted all the DB files, and recovered the DB with the latest backup. could you please share something about how to repair the wierdTiger files, maybe next time I can try to repair it myself. |
| Comment by Nick Brewer [ 07/Aug/18 ] |
|
mzhang11 I can attempt to repair the files - before I do, I'd like to confirm:
Thanks, |