[SERVER-50813] Local MongoDB Server fails to start - "WiredTiger.wt is corrupted: WT_TRY_SALVAGE: database corruption detected" Created: 09/Sep/20 Updated: 14/Sep/20 Resolved: 14/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.0, 4.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Umar Ghouse | Assignee: | Dmitry Agranat |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I cannot seem to get my local mongodb server running - I run the mongod command in my command prompt and get the following error:
The only change I did recently was to upgrade to MongoDB Compass from the Community edition of Compass. But I never accessed my local data with that, just my remote database on MongoDB Atlas. I have tried running mongod with the --repair command and the --dbpath command, but it still fails with the same error. What can I do to solve this issue? |
| Comments |
| Comment by Umar Ghouse [ 14/Sep/20 ] | ||
|
Hi Dmitry! Just one clarification - when you say removing the dbpath, simply deleting it and running mongod after that should be sufficient yes? Thanks for all the help! Umar | ||
| Comment by Dmitry Agranat [ 14/Sep/20 ] | ||
|
Hi m.umarghouse@gmail.com, yes, removing the dbpath of an old installation and re-installing sounds like a right path to follow. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Developer Community Forums or on Stack Overflow with the mongodb tag. Regards, | ||
| Comment by Umar Ghouse [ 13/Sep/20 ] | ||
|
OK - that's unfortunate. Is there anyway, I can get my mongoDB Server to work again? I don't necessarily need the data, it was only really used in my local development environment, so I'm not really concerned about retrieving the data. What I want to do is be able to run a local mongodb server, so I can use it in my development process. How can I do that? Would I need to uninstall all versions of mongo and re-install them? Or is there another way? | ||
| Comment by Dmitry Agranat [ 13/Sep/20 ] | ||
|
Thanks m.umarghouse@gmail.com, the uploaded data shows a MongoDB 4.2.0 version and data monitoring ended about a month ago. I assume this is not the data we are trying to investigate here. With no logs and diagnostic.data I am not sure what else we can do to in this case. | ||
| Comment by Umar Ghouse [ 13/Sep/20 ] | ||
|
Hi Dmitry!
I have uploaded all the files I had in my diagnostics.data folder to the upload portal you provided earlier. Do let me know if there is anything else I can provide to help solve this issue. | ||
| Comment by Dmitry Agranat [ 13/Sep/20 ] | ||
|
Hi m.umarghouse@gmail.com, please upload the diagnostic.data which might shed some lite about other data we are looking for. | ||
| Comment by Umar Ghouse [ 11/Sep/20 ] | ||
|
Sorry Dmitry, I am not very familiar with Mongo - In my dbpath, I have a jourrnal folder with some WiredTiger logs, is that what you need? Unfortunately, I don't seem to have a mongod.log file anywhere. I also have a "_repair_incomplete" file and a "_mdb_catalog.wt" file - are those of any relevance? the other files that I have are "collection" files, some "index" files and some "metrics" files in the "diagnostic.data" folder. Do let me know what is relevant to be uploaded here.
I was running this MongoDB node on my local PC, so I am fairly certain that it was not part of a replica set - is there anyway that I can confirm this? | ||
| Comment by Dmitry Agranat [ 10/Sep/20 ] | ||
|
In order for us to investigate the issue, we'll need to review the logs originating the reported event. MongoDB logs by default are located under the dbpath unless configured differently. Please check if it is still feasible to find and upload these logs. Also, is this node a part of a Replica Set and if yes, are the remaining members healthy? Thanks, | ||
| Comment by Umar Ghouse [ 10/Sep/20 ] | ||
|
Hi Dmitry,
Unfortunately, the log messages for the time of the initial error and the upgrade from 4.2 to 4.4 were printed to my command prompt and I have since closed those sessions. Is there another way to retrieve these logs?
On the repair operation, it never completed. Every time I ran it, it ended with an error. I re-ran the repair operation now and got the following logs:
And the logs of what happened when I tried running mongod again after the repair are:
I've also uploaded copies of the WiredTiger files you requested. | ||
| Comment by Dmitry Agranat [ 10/Sep/20 ] | ||
|
In order for us to investigate this issue, please provide the following information:
I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Thanks, |