[SERVER-43793] Wiredtiger.wt corrupted after power outage - node not starting Created: 03/Oct/19  Updated: 04/Dec/19  Resolved: 04/Dec/19

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

Type: Bug Priority: Major - P3
Reporter: David MZ Assignee: Carl Champain (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt    
Operating System: ALL
Participants:

 Description   

After a power outage, the node is not booting up

istics=(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-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (-31802) [1570091617:224206][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224309][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224340][8947:0x7f4131546dc0], 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-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224374][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-10-03T11:33:37.225+0300 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2019-10-03T11:33:37.225+0300 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-10-03T11:33:37.225+0300 I CONTROL [initandlisten] dbexit: rc: 100

 

I saw very old tickets where you attached WiredTiger.wt and WiredTiger.turtle

I attach those two, I saw the support team answer with a fixed version of the files



 Comments   
Comment by Carl Champain (Inactive) [ 04/Dec/19 ]

Hi david@concom.io,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Carl
 

Comment by Carl Champain (Inactive) [ 11/Nov/19 ]

Hi david@concom.io,

Any updates on this issue?

Comment by Carl Champain (Inactive) [ 03/Oct/19 ]

Hi david@concom.io,

Thanks for the report.

Unfortunately, this error message leads us to suspect some form of physical corruption.

Importantly, 3.2.1 version of MongoDB is already end-of-lifed, you should upgrade to the latest 4.2.0 or 4.0.12.

A couple questions:

1. Could you provide the log file for this node?
2. Are you using a replica set? If so, the ideal resolution is to perform a clean resync from an unaffected node and it will resolve your issue.

Kind regards,

Carl

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