[SERVER-48770] error while mongod startup Created: 12/Jun/20  Updated: 15/Jun/20  Resolved: 15/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Subhajit Chakraborty Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Receiving the below error while starting up my replica member:

 

2020-06-11T21:24:17.247-0400 E STORAGE [initandlisten] WiredTiger error (0) [1591925057:247927][35433:0x7f4665009dc0]file:WiredTiger.wt, WT_CURSOR.next: read checksum error for 28672B block at offset 233472: block header checksum of 1604728680 doesn't match expected checksum of 2821136383
2020-06-11T21:24:17.248-0400 E STORAGE [initandlisten] WiredTiger error (0) [1591925057:247999][35433:0x7f4665009dc0]file:WiredTiger.wt, WT_CURSOR.next: WiredTiger.wt: encountered an illegal file format or internal value
2020-06-11T21:24:17.248-0400 E STORAGE [initandlisten] WiredTiger error (-31804) [1591925057:248014][35433:0x7f4665009dc0]file:WiredTiger.wt, WT_CURSOR.next: the process must exit and restart: WT_PANIC: WiredTiger library panic
2020-06-11T21:24:17.248-0400 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361
2020-06-11T21:24:17.248-0400 I - [initandlisten]

***aborting after fassert() failure



 Comments   
Comment by Carl Champain (Inactive) [ 15/Jun/20 ]

Hi schakraborty@bn.com,

MongoDB 3.4 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version. If you need assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. I will now close this ticket.

Kind regards,
Carl

Comment by Subhajit Chakraborty [ 12/Jun/20 ]

Redhat 6 OS

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