-
Type: Question
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.5
-
Component/s: None
-
Environment:Aws Linux
Dear
I got below message during repair mongodb, any idea ?
2019-06-01T16:04:52.645+0800 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2019-06-01T16:04:52.645+0800 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=17G,session_max=20000,eviction=(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),
2019-06-01T16:04:52.654+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1559376292:654308][18993:0x7f7894659d80], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-06-01T16:04:52.654+0800 E STORAGE [initandlisten] WiredTiger (0) [1559376292:654346][18993:0x7f7894659d80], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-06-01T16:04:52.654+0800 E STORAGE [initandlisten] WiredTiger (0) [1559376292:654371][18993:0x7f7894659d80], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2019-06-01T16:04:52.654+0800 E STORAGE [initandlisten] WiredTiger (0) [1559376292:654391][18993:0x7f7894659d80], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-06-01T16:04:52.654+0800 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2019-06-01T16:04:52.654+0800 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating