[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: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi Team, Actually thing is that we are working on the restoration of data. 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. |
| Comments |
| Comment by Dmitry Agranat [ 21/Feb/21 ] |
|
We haven’t heard back from you for some time, so I’m going to close this ticket. Regards, |
| Comment by Dmitry Agranat [ 10/Feb/21 ] |
|
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, |