Info

I cannot seem to get my local mongodb server running - I run the mongod command in my command prompt and get the following error: {"t":{"$date":"2020-09-09T19:16:15.558+05:30"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"} {"t":{"$date":"2020-09-09T19:16:15.937+05:30"},"s":"W", "c":"ASIO", "id":22601, "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"} {"t":{"$date":"2020-09-09T19:16:15.938+05:30"},"s":"I", "c":"NETWORK", "id":4648602, "ctx":"main","msg":"Implicit TCP FastOpen in use."} {"t":{"$date":"2020-09-09T19:16:15.940+05:30"},"s":"I", "c":"STORAGE", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":28352,"port":27017,"dbPath":"C:/data/db","architecture":"64-bit","host":"Vivo"}} {"t":{"$date":"2020-09-09T19:16:15.940+05:30"},"s":"I", "c":"CONTROL", "id":23398, "ctx":"initandlisten","msg":"Target operating system minimum version","attr":{"targetMinOS":"Windows 7/Windows Server 2008 R2"}} {"t":{"$date":"2020-09-09T19:16:15.940+05:30"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"4.4.0","gitVersion":"563487e100c4215e2dce98d0af2a6a5a2d67c5cf","modules":[],"allocator":"tcmalloc","environment":{"distmod":"windows","distarch":"x86_64","target_arch":"x86_64"}}}} {"t":{"$date":"2020-09-09T19:16:15.941+05:30"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Microsoft Windows 10","version":"10.0 (build 18363)"}}} {"t":{"$date":"2020-09-09T19:16:15.942+05:30"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"repair":true,"storage":{"dbPath":"C:\\data\\db"}}}} {"t":{"$date":"2020-09-09T19:16:15.945+05:30"},"s":"I", "c":"STORAGE", "id":22270, "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"C:/data/db","storageEngine":"wiredTiger"}} {"t":{"$date":"2020-09-09T19:16:15.945+05:30"},"s":"I", "c":"STORAGE", "id":22315, "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=7605M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}} {"t":{"$date":"2020-09-09T19:16:15.965+05:30"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":-31809,"message":"[1599659175:965805][28352:140715294088784], file:WiredTiger.wt, connection: __desc_read, 379: WiredTiger.wt is corrupted: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-09T19:16:15.968+05:30"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."} {"t":{"$date":"2020-09-09T19:16:15.968+05:30"},"s":"W", "c":"STORAGE", "id":22348, "ctx":"initandlisten","msg":"WiredTiger metadata corruption detected"} {"t":{"$date":"2020-09-09T19:16:15.972+05:30"},"s":"W", "c":"STORAGE", "id":22349, "ctx":"initandlisten","msg":"Attempting to salvage WiredTiger metadata"} {"t":{"$date":"2020-09-09T19:16:15.980+05:30"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":-31809,"message":"[1599659175:980070][28352:140715294088784], file:WiredTiger.wt, WT_SESSION.salvage: __desc_read, 379: WiredTiger.wt is corrupted: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-09T19:16:15.981+05:30"},"s":"F", "c":"STORAGE", "id":50947, "ctx":"initandlisten","msg":"Failed to salvage WiredTiger metadata","attr":{"details":"-31809: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-09T19:16:15.982+05:30"},"s":"F", "c":"-", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50947,"file":"src\\mongo\\db\\storage\\wiredtiger\\wiredtiger_kv_engine.cpp","line":1115}} {"t":{"$date":"2020-09-09T19:16:15.983+05:30"},"s":"F", "c":"-", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"} 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?

Top User Comments

m.umarghouse@gmail.com commented on Mon, 14 Sep 2020 08:38:38 +0000: 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 dmitry.agranat commented on Mon, 14 Sep 2020 08:22:28 +0000: 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, Dima m.umarghouse@gmail.com commented on Sun, 13 Sep 2020 13:22:20 +0000: 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? dmitry.agranat commented on Sun, 13 Sep 2020 13:08:15 +0000: 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. m.umarghouse@gmail.com commented on Sun, 13 Sep 2020 12:54:45 +0000: 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. dmitry.agranat commented on Sun, 13 Sep 2020 10:11:08 +0000: Hi m.umarghouse@gmail.com, please upload the diagnostic.data which might shed some lite about other data we are looking for. m.umarghouse@gmail.com commented on Fri, 11 Sep 2020 03:05:46 +0000: 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? dmitry.agranat commented on Thu, 10 Sep 2020 19:28:12 +0000: Hi m.umarghouse@gmail.com, 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, Dima m.umarghouse@gmail.com commented on Thu, 10 Sep 2020 10:54:52 +0000: 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: {"t":{"$date":"2020-09-10T16:22:23.139+05:30"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"} {"t":{"$date":"2020-09-10T16:22:23.503+05:30"},"s":"W", "c":"ASIO", "id":22601, "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"} {"t":{"$date":"2020-09-10T16:22:23.504+05:30"},"s":"I", "c":"NETWORK", "id":4648602, "ctx":"main","msg":"Implicit TCP FastOpen in use."} {"t":{"$date":"2020-09-10T16:22:23.505+05:30"},"s":"I", "c":"STORAGE", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":15920,"port":27017,"dbPath":"C:/data/db/","architecture":"64-bit","host":"Vivo"}} {"t":{"$date":"2020-09-10T16:22:23.505+05:30"},"s":"I", "c":"CONTROL", "id":23398, "ctx":"initandlisten","msg":"Target operating system minimum version","attr":{"targetMinOS":"Windows 7/Windows Server 2008 R2"}} {"t":{"$date":"2020-09-10T16:22:23.505+05:30"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"4.4.0","gitVersion":"563487e100c4215e2dce98d0af2a6a5a2d67c5cf","modules":[],"allocator":"tcmalloc","environment":{"distmod":"windows","distarch":"x86_64","target_arch":"x86_64"}}}} {"t":{"$date":"2020-09-10T16:22:23.505+05:30"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Microsoft Windows 10","version":"10.0 (build 18363)"}}} {"t":{"$date":"2020-09-10T16:22:23.505+05:30"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"repair":true}}} {"t":{"$date":"2020-09-10T16:22:23.510+05:30"},"s":"I", "c":"STORAGE", "id":22270, "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"C:/data/db/","storageEngine":"wiredTiger"}} {"t":{"$date":"2020-09-10T16:22:23.512+05:30"},"s":"I", "c":"STORAGE", "id":22315, "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=7605M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}} {"t":{"$date":"2020-09-10T16:22:23.541+05:30"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":-31809,"message":"[1599735143:541486][15920:140715749432912], file:WiredTiger.wt, connection: __desc_read, 379: WiredTiger.wt is corrupted: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-10T16:22:23.543+05:30"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."} {"t":{"$date":"2020-09-10T16:22:23.543+05:30"},"s":"W", "c":"STORAGE", "id":22348, "ctx":"initandlisten","msg":"WiredTiger metadata corruption detected"} {"t":{"$date":"2020-09-10T16:22:23.546+05:30"},"s":"W", "c":"STORAGE", "id":22349, "ctx":"initandlisten","msg":"Attempting to salvage WiredTiger metadata"} {"t":{"$date":"2020-09-10T16:22:23.553+05:30"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":-31809,"message":"[1599735143:552539][15920:140715749432912], file:WiredTiger.wt, WT_SESSION.salvage: __desc_read, 379: WiredTiger.wt is corrupted: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-10T16:22:23.555+05:30"},"s":"F", "c":"STORAGE", "id":50947, "ctx":"initandlisten","msg":"Failed to salvage WiredTiger metadata","attr":{"details":"-31809: WT_TRY_SALVAGE: database corruption detected"}} {"t":{"$date":"2020-09-10T16:22:23.555+05:30"},"s":"F", "c":"-", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50947,"file":"src\\mongo\\db\\storage\\wiredtiger\\wiredtiger_kv_engine.cpp","line":1115}} {"t":{"$date":"2020-09-10T16:22:23.557+05:30"},"s":"F", "c":"-", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"} And the logs of what happened when I tried running mongod again after the repair are: {"t":{"$date":"2020-09-10T16:22:39.107+05:30"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"} {"t":{"$date":"2020-09-10T16:22:39.109+05:30"},"s":"W", "c":"ASIO", "id":22601, "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"} {"t":{"$date":"2020-09-10T16:22:39.109+05:30"},"s":"I", "c":"NETWORK", "id":4648602, "ctx":"main","msg":"Implicit TCP FastOpen in use."} {"t":{"$date":"2020-09-10T16:22:39.113+05:30"},"s":"I", "c":"STORAGE", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":6064,"port":27017,"dbPath":"C:/data/db/","architecture":"64-bit","host":"Vivo"}} {"t":{"$date":"2020-09-10T16:22:39.113+05:30"},"s":"I", "c":"CONTROL", "id":23398, "ctx":"initandlisten","msg":"Target operating system minimum version","attr":{"targetMinOS":"Windows 7/Windows Server 2008 R2"}} {"t":{"$date":"2020-09-10T16:22:39.113+05:30"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"4.4.0","gitVersion":"563487e100c4215e2dce98d0af2a6a5a2d67c5cf","modules":[],"allocator":"tcmalloc","environment":{"distmod":"windows","distarch":"x86_64","target_arch":"x86_64"}}}} {"t":{"$date":"2020-09-10T16:22:39.114+05:30"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Microsoft Windows 10","version":"10.0 (build 18363)"}}} {"t":{"$date":"2020-09-10T16:22:39.114+05:30"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{}}} {"t":{"$date":"2020-09-10T16:22:39.115+05:30"},"s":"F", "c":"STORAGE", "id":50922, "ctx":"initandlisten","msg":"An incomplete repair has been detected! This is likely because a repair operation unexpectedly failed before completing. MongoDB will not start up again without --repair."} {"t":{"$date":"2020-09-10T16:22:39.116+05:30"},"s":"F", "c":"-", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50922,"file":"src\\mongo\\db\\storage\\storage_engine_init.cpp","line":85}} {"t":{"$date":"2020-09-10T16:22:39.116+05:30"},"s":"F", "c":"-", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"} I've also uploaded copies of the WiredTiger files you requested. dmitry.agranat commented on Thu, 10 Sep 2020 10:36:58 +0000: Hi m.umarghouse@gmail.com In order for us to investigate this issue, please provide the following information: The full mongod logs covering the time of the initial error (and upgrade from 4.2 to 4.4 if this is still available). The logs of the repair operation. The logs of any attempt to start mongod after the repair operation completed. Copies of the wiredTiger.wt and wiredTiger.turtle files (we can attempt a metadata-only repair effort using internal tools). 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, Dima

Steps to Reproduce