[SERVER-47347] [TTLMonitor] WiredTiger error (-31802) - Got signal: 6 (Aborted) Created: 06/Apr/20  Updated: 07/Apr/20  Resolved: 06/Apr/20

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

Type: Bug Priority: Major - P3
Reporter: Alessandro Maggio Assignee: Carl Champain (Inactive)
Resolution: Done 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   

Hi, I've a problem with mondodb. After the mongod command It's start and I'm able to connect and see the collections, after xx times he going to crash

2020-04-06T14:55:36.653+0200 E STORAGE [TTLMonitor] WiredTiger error (-31802) [1586177736:653098][13842:0x7f7358b21700], file:collection-4-1458677614254779015.wt, WT_SESSION.open_cursor: __posix_file_read, 449: $
/dbpath//collection-4-1458677614254779015.wt: handle-read: pread: failed to read 4096 bytes at offset 0: WT_ERROR: non-specific WiredTiger error Raw: [1586177736:653098][13842:0x7f7358b21700], file:collect$
on-4-1458677614254779015.wt, WT_SESSION.open_cursor: __posix_file_read, 449: ./dbpath//collection-4-1458677614254779015.wt: handle-read: pread: failed to read 4096 bytes at offset 0: WT_ERROR: non-specific
WiredTiger error 
2020-04-06T14:55:36.653+0200 E STORAGE [TTLMonitor] An unsupported journal format detected - If you are trying to rollback from version 4.0 to 3.6, please re-start a 4.0 binary and cleanly shut it down so that t$
e journal format will be downgraded. 
2020-04-06T14:55:36.653+0200 F - [TTLMonitor] Invariant failure: ret resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src/mongo/db/storage/wiredtiger/wiredtiger_session_ca
che.cpp 130 
2020-04-06T14:55:36.653+0200 F - [TTLMonitor]
 
***aborting after invariant() failure 
 
 
2020-04-06T14:55:36.672+0200 F - [TTLMonitor] Got signal: 6 (Aborted).



 Comments   
Comment by Carl Champain (Inactive) [ 06/Apr/20 ]

Thank you for following up alex.tkd.alex@gmail.com!

I will close this ticket.

Comment by Alessandro Maggio [ 06/Apr/20 ]

I've solved by do mongoexport all the json file and import into new database.

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