HELP : Fatal Assertion 28558
Ketsume Harn
Hi all, does anyone encounter "Fatal Assertion 28558" error before? My mongoDB is under windows platform and I try to restart mongoDB service but show error 1067. When I open the log, I saw fatal assertion 28558. Can I know how to solve it please? I not yet restart the server still and the server still have enough space (40GB+). Thanks and highly appreciate.
---------------------------------------
2019-03-11T09:28:17.559+1100 I CONTROL [main] ***** SERVER RESTARTED *****
2019-03-11T09:28:18.151+1100 I CONTROL [main] Trying to start Windows service 'MongoDB'
2019-03-11T09:28:18.153+1100 I CONTROL [initandlisten] MongoDB starting : pid=536148 port=27017 dbpath=C:\mongodb\data\db 64-bit host=mongoDBServer01
2019-03-11T09:28:18.153+1100 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2019-03-11T09:28:18.153+1100 I CONTROL [initandlisten] db version v3.6.3
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] git version: 9586e557d54ef70f9ca4b43c26892cd55257e1a5
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1u-fips 22 Sep 2016
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] allocator: tcmalloc
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] modules: none
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] build environment:
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] distmod: 2008plus-ssl
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] distarch: x86_64
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] target_arch: x86_64
2019-03-11T09:28:18.154+1100 I CONTROL [initandlisten] options: { config: "C:\mongodb\mongod.cfg", net: { bindIp: "mongoDBServer01", port: 27017 }, replication: { oplogSizeMB: 5120, replSetName: "rs01" }, security: { authorization: "enabled", keyFile: "C:\mongodb\keyfile\mongoDBReplica.key" }, service: true, storage: { dbPath: "C:\mongodb\data\db", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "C:\mongodb\data\log\mongod.log" } }
2019-03-11T09:28:18.154+1100 W - [initandlisten] Detected unclean shutdown - C:\mongodb\data\db\mongod.lock is not empty.
2019-03-11T09:28:18.159+1100 I - [initandlisten] Detected data files in C:\mongodb\data\db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-03-11T09:28:18.159+1100 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2019-03-11T09:28:18.159+1100 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7674M,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),statistics_log=(wait=0),verbose=(recovery_progress),
2019-03-11T09:28:18.632+1100 I STORAGE [initandlisten] WiredTiger message [1552256898:632994][536148:1992766336], txn-recover: Main recovery loop: starting at 36/256
2019-03-11T09:28:18.642+1100 I STORAGE [initandlisten] WiredTiger message [1552256898:642995][536148:1992766336], txn-recover: Recovering log 36 through 37
2019-03-11T09:28:18.837+1100 I STORAGE [initandlisten] WiredTiger message [1552256898:837014][536148:1992766336], txn-recover: Recovering log 37 through 37
2019-03-11T09:28:19.146+1100 E STORAGE [initandlisten] WiredTiger error (16) [1552256899:146045][536148:1992766336], connection: C:\mongodb\data\db\WiredTigerLAS.wt: file-remove: DeleteFileW: The process cannot access the file because it is being used by another process.
: Resource device
2019-03-11T09:28:19.146+1100 E STORAGE [initandlisten] WiredTiger error (16) [1552256899:146045][536148:1992766336], connection: metadata remove dropped file WiredTigerLAS.wt: Resource device
2019-03-11T09:28:19.146+1100 E STORAGE [initandlisten] WiredTiger error (16) [1552256899:146045][536148:1992766336], connection: failed to apply or unroll all tracked operations: Resource device
2019-03-11T09:28:19.146+1100 E STORAGE [initandlisten] WiredTiger error (-31804) [1552256899:146045][536148:1992766336], connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2019-03-11T09:28:19.146+1100 F - [initandlisten] Fatal Assertion 28558 at src\mongo\db\storage\wiredtiger\wiredtiger_util.cpp 361
2019-03-11T09:28:19.146+1100 F - [initandlisten]
***aborting after fassert() failure
2019-03-11T09:28:19.258+1100 E STORAGE [thread1] WiredTiger error (-31804) [1552256899:258056][536148:1992766336], log-server: journal\WiredTigerTmplog.0000000003: fatal log failure: WT_PANIC: WiredTiger library panic
2019-03-11T09:28:19.258+1100 F - [thread1] Fatal Assertion 28558 at src\mongo\db\storage\wiredtiger\wiredtiger_util.cpp 361
2019-03-11T09:28:19.258+1100 F - [thread1]
***aborting after fassert() failure
-----------------------
Kevin Adistambha
Hi,
I’m not entirely sure what happened, but this line provides a hint:
2019-03-11T09:28:19.146+1100 E STORAGE [initandlisten] WiredTiger error (16) [1552256899:146045][536148:1992766336], connection: C:\mongodb\data\db\WiredTigerLAS.wt: file-remove: DeleteFileW: The process cannot access the file because it is being used by another process.
It seems like more than one process is trying to access the dbpath at the same time. Do you have a virus scanner active, or similar process e.g. monitoring? WiredTiger needs exclusive access to the dbpath for it to function correctly.
Also, does this error happen again when you try to restart the server again?
Best regards,
Kevin