[SERVER-77675] WiredTiger (-31804) // Fatal Assertion 28558 Created: 01/Jun/23 Updated: 06/Jun/23 Resolved: 06/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.22 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | 승규 이 | Assignee: | Chris Kelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
centos 6.9 |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
mongodb not working since server power down I also tried --repair but it didn't work Please check the attached log and wiredtiger files. |
| Comments |
| Comment by Chris Kelly [ 06/Jun/23 ] |
|
MongoDB 3.2 reached end of life in September 2018 and is no longer supported. MongoDB 4.4+ is currently supported. This error message leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. The ideal resolution is to perform a clean resync from an unaffected node. This is the only recommended option outside of external backups if mongod --repair did not resolve your issue, however, there have been suggestions from prior users that using newer release binaries resolved these issues for them as well, and running --repair, because of improvements in the repair functionality in later versions ( Hopefully this is enough to work from to resolve your issue until you get onto a supported version of MongoDB! |