[SERVER-28601] Mongo start aborting after fassert() failure Created: 04/Apr/17 Updated: 31/May/17 Resolved: 04/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sasanka Uppu [X] | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by Kelsey Schubert [ 04/Apr/17 ] |
|
Hi Sasanka_uppu, I'm glad you were able to restart mongod successfully. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by Sasanka Uppu [X] [ 04/Apr/17 ] |
|
Hiii, |
| Comment by Kelsey Schubert [ 04/Apr/17 ] |
|
Hi Sasanka_uppu, Thanks for the additional information. Removing the drive as you describe would explain this type of disk corruption. Unfortunately, there is little MongoDB can do to in these circumstances. To successfully restart mongod, please remove WiredTigerLog files greater than or equal to 5020. After removing these files, the dbpath should be back in a consistent state assuming no other corruption has occurred. This process will allow mongod to recover everything up to 5019. Please note that the more recent log files may have been written as part of the restart attempts, but if they contain real data, it would be lost. Kind regards, |
| Comment by Sasanka Uppu [X] [ 04/Apr/17 ] |
|
Hi Thanks for the quick response.. 2) Yes I opened a connection in Pymongo (Python code) and removed the drive without closing the connection. Thanks! |
| Comment by Kelsey Schubert [ 04/Apr/17 ] |
|
Hi Sasanka_uppu, Thanks for reporting this behavior. It appears the WiredTigerLog.0000005020 file has been zeroed. I have a few questions to better understand what has happened.
Thank you, |
| Comment by Sasanka Uppu [X] [ 04/Apr/17 ] |
|
Just as a heads up I have been accessing the mongodb from pymongo and forgot to close the connection before removing the external drive in which db was present.. which possibly might have caused this |
| Comment by Sasanka Uppu [X] [ 04/Apr/17 ] |
|
Unfortunately doing mongodb --repair is also throwing the same error.. |
| Comment by Sasanka Uppu [X] [ 04/Apr/17 ] |
|
I put my mongo data base in my external drive and explicitly give the db path with the command (sudo mongod --dbpath ***) whenever i use mongo... |