[SERVER-54130] WiredTiger Library panic error.(WT_panic) and WT_NOTFOUND Created: 29/Jan/21  Updated: 27/Oct/23  Resolved: 21/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Nagesh Dnyandeo Kamble Assignee: Dmitry Agranat
Resolution: Community Answered Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File 1.JPG     JPEG File 2.JPG     JPEG File 3.JPG     JPEG File 4.JPG    
Operating System: ALL
Participants:

 Description   

Hi Team,

Actually thing is that we are working on the restoration of data.
As a workaround, we follow the VM snapshot (i.e Windows) as a backup mechanism. We have taken the old tape backup and restore it on the new VM.
But, when we trying to start the mongod service on it we fail to start it.
We tried to start mongod with --dbpath and --logpath option with including the db data folder.
But we are getting an error of WT_PANIC : WiredTigar library panic.

And, wiredTigar.turtle: fatal turtle file read error.

Also if we would us to understand why this error nd which case it occurs.

That will be really helpful.
Necessary screenshot attached for reference.
Kindly help us!! struggling lot!!
Thanks in advance.



 Comments   
Comment by Dmitry Agranat [ 21/Feb/21 ]

Hi n.kamble@pokermagnet.com,

We haven’t heard back from you for some time, so I’m going to close this ticket.

Regards,
Dima

Comment by Dmitry Agranat [ 10/Feb/21 ]

Hi n.kamble@pokermagnet.com,

The error message leads us to suspect some form of physical corruption. It will be difficult to determine what exactly has happened w/o collecting more evidence such as mongod, syslog, dmesg logs and different wiredtiger files as well as inspecting and validating your backup process.

The ideal resolution is to perform a clean resync from an unaffected node.

You can also try mongod --repair using the latest version of MongoDB.

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

Thanks,
Dima

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