[SERVER-41173] Can't repair corrupted database from bad shutdown: Segmentation Fault 11 Created: 16/May/19 Updated: 28/May/19 Resolved: 28/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lokasa Mawati | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | driver | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac 10.13.6 with mongod v4.0.3. |
||
| Participants: |
| Description |
|
(edit: Transferring content from here) I just ran into a problem in my Node.js script. All the script did was write collection.update(...) and did an upsert of a single record. Nothing fancy. And it throws this error:
So then I ran mongod --repair:
...which gave this output (the final result of tail -f /usr/local/var/log/mongodb/mongo.log).
It failed :/. So I tried restarting the mongod process, and got this in the logs:
Wondering what I can do given I have no backups. I am not very far along but I would like to not have to rebuild the database. Wondering if I can recover anything and get it to restart again. I'm also not really sure what exactly I did to cause this. This is related to the error.
Now, I upgraded to > 4.0, and ran start and repair, which ends up just seg faulting:
The logs from that show:
Original descriptionI have written up the detailed description here Essentially what I'm getting now is this: {{}}
{{$ mongod -v --config /usr/local/etc/mongod.conf --dbpath /Volumes/My\ Passport\ for\ Mac/mongo 2019-05-15T21:28:12.894-0700 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' Error 100 }} And the logs show:
|
| Comments |
| Comment by Eric Sedor [ 28/May/19 ] |
|
mawati, based on the information you've provided you may be able to restart with MongoDB 3.0 if you address the old lock file issue. But importantly, we aren't able to support MongoDB 3.0 here. The SERVER project is for bugs and feature suggestions for supported versions of the MongoDB server, so I'm going to close this ticket. If your superuser post does not get any traction, you may find someone who can help if you post on the mongodb-user group or on Stack Overflow with the mongodb tag. |
| Comment by Eric Sedor [ 17/May/19 ] |
|
mawati, we are reviewing this information and will let you know if we have questions. For future reference, a TransientTransactionError is not intended as an indication that a repair operation is necessary. Please also be aware that MongoDB 3.0 reached end of life on February 2018, so our ability to investigate whether or not this behavior is the result of a bug could be very limited. If you can provide steps to reproduce this problem on MongoDB 3.4 starting from an empty database it will be helpful. |