[SERVER-41450] Can not repair MongoDB Created: 01/Jun/19  Updated: 05/Jun/19  Resolved: 03/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.5
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Hanrango Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: issue
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Aws Linux


Attachments: File SERVER-41450_repair_attempt.tgz    
Participants:

 Description   

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



 Comments   
Comment by Hanrango [ 05/Jun/19 ]

It works! thank you for your help and recommendation

Comment by Eric Sedor [ 03/Jun/19 ]

I've attached a repair attempt of the files you provided as SERVER-41450_repair_attempt.tgz. Please extract these files, replace them in your $dbpath. Keep in mind this may not be successful, and that the ideal resolution is to perform a clean resync from an unaffected node.

To avoid a problem like in the future, it is our strong recommendation to:

Importantly, MongoDB 3.2 reached end of life in September 2018.

Comment by Hanrango [ 01/Jun/19 ]

Attached the wiredtiger.wt and wiredtiger.turtle for investigation

Generated at Thu Feb 08 04:57:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.