[SERVER-32026] Mongo fails to restart after unusual shutdown Created: 17/Nov/17  Updated: 27/Jul/18  Resolved: 01/Dec/17

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

Type: Bug Priority: Major - P3
Reporter: Lakshika Balasuriya Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: envns, rns, rpns, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair-SERVER-32026.tar.gz    
Operating System: ALL
Participants:

 Description   

I am trying to restart mongod service but it fails. I get * Fatal Assertion 28558* error when it tries to recover from the last checkpoint. Please find the attached WiredTiger.wt and WiredTiger.turtle files.

Detected WT journal files. Running recovery from last checkpoint.
2017-11-17T21:36:30.374+0000 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=74G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-11-17T21:36:35.633+0000 E STORAGE [initandlisten] WiredTiger (0) [1510954595:633534][30757:0x7f6f3bcebcc0], file:WiredTiger.wt, WT_CURSOR.search_near: read checksum error for 28672B block at offset 16384: block header checksum of 0 doesn't match expected checksum of 3341117329
2017-11-17T21:36:35.633+0000 E STORAGE [initandlisten] WiredTiger (0) [1510954595:633666][30757:0x7f6f3bcebcc0], file:WiredTiger.wt, WT_CURSOR.search_near: WiredTiger.wt: encountered an illegal file format or internal value
2017-11-17T21:36:35.633+0000 E STORAGE [initandlisten] WiredTiger (-31804) [1510954595:633685][30757:0x7f6f3bcebcc0], file:WiredTiger.wt, WT_CURSOR.search_near: the process must exit and restart: WT_PANIC: WiredTiger library panic
2017-11-17T21:36:35.633+0000 I - [initandlisten] Fatal Assertion 28558
2017-11-17T21:36:35.633+0000 I - [initandlisten]

***aborting after fassert() failure



 Comments   
Comment by Mark Agarunov [ 01/Dec/17 ]

Hello lakindi,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Thanks,
Mark

Comment by Mark Agarunov [ 20/Nov/17 ]

Hello lakindi,

Thank you for the report. I've attached a repair attempt of the files you've provided. Would you please extract these files and replace them in your $dbpath and let us know if it resolves the issue? If you are still seeing errors after replacing these files, please provide the complete logs from mongod so that we can further investigate. Additionally, if this issue persists, please provide the following information:

  1. What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using?
  2. Would you please check the integrity of your disks?
  3. Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through.
  4. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running?
  5. Have you ever restored this instance from backups?
  6. What method do you use to create backups?
  7. When was the underlying filesystem last checked and is it currently marked clean?

Thanks,
Mark

Generated at Thu Feb 08 04:28:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.