0

We have a major issues on our MongoDB and I've attached the latest logs and files. In previous forumns I've seen this get fixed by your team. Can you please help as soon as possible please, we are a medical facility and need this fixed.

We are running on Windows 2016 Server and running fine until a power outage.

2020-09-11T14:34:18.780-0400 I CONTROL [main] Trying to start Windows service 'MongoDB' 2020-09-11T14:34:18.781-0400 I CONTROL [initandlisten] MongoDB starting : pid=1816 port=27017 dbpath=C:\Program Files\DELL\WMS\Database\Mongo 64-bit host=VLDATAWMS02 2020-09-11T14:34:18.781-0400 I CONTROL [initandlisten] targetMinOS: Windows Vista/Windows Server 2008 2020-09-11T14:34:18.781-0400 I CONTROL [initandlisten] db version v3.4.10 2020-09-11T14:34:18.781-0400 I CONTROL [initandlisten] git version: 078f28920cb24de0dd479b5ea6c66c644f6326e9 2020-09-11T14:34:18.781-0400 I CONTROL [initandlisten] allocator: tcmalloc 2020-09-11T14:34:18.782-0400 I CONTROL [initandlisten] modules: none 2020-09-11T14:34:18.784-0400 I CONTROL [initandlisten] build environment: 2020-09-11T14:34:18.784-0400 I CONTROL [initandlisten] distarch: x86_64 2020-09-11T14:34:18.784-0400 I CONTROL [initandlisten] target_arch: x86_64 2020-09-11T14:34:18.785-0400 I CONTROL [initandlisten] options: { config: "C:\Program Files\DELL\WMS\MongoDB\mongod.cfg", net: { bindIp: "localhost", port: 27017 }, security: { authorization: "enabled" }, service: true, storage: { dbPath: "C:\Program Files\DELL\WMS\Database\Mongo" }, systemLog: { destination: "file", path: "C:\Program Files\DELL\WMS\MongoDb\mongod.log" } } 2020-09-11T14:34:18.785-0400 I - [initandlisten] Detected data files in C:\Program Files\DELL\WMS\Database\Mongo created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2020-09-11T14:34:18.786-0400 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3583M,session_max=20000,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),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0), 2020-09-11T14:34:18.797-0400 E STORAGE [initandlisten] WiredTiger error (0) [1599849258:797507][1816:140721228962256], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 24576: block header checksum of 1919248233 doesn't match expected checksum of 3720300442 2020-09-11T14:34:18.797-0400 E STORAGE [initandlisten] WiredTiger error (0) [1599849258:797507][1816:140721228962256], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value 2020-09-11T14:34:18.797-0400 E STORAGE [initandlisten] WiredTiger error (-31804) [1599849258:797507][1816:140721228962256], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic 2020-09-11T14:34:18.797-0400 I - [initandlisten] Fatal Assertion 28558 at src\mongo\db\storage\wiredtiger\wiredtiger_util.cpp 361 2020-09-11T14:34:18.797-0400 I - [initandlisten]

***aborting after fassert() failure

Thank You,

2
  • You can close this I thought I was on MongoDB site. – Bob Beard Sep 11 '20 at 18:42
  • 1
    You can delete your question yourself, you know. – mustaccio Sep 11 '20 at 19:17
0

Even you are at the "wrong place"... Command 'wt salvage' of wiretiger tools probably will solve this problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.