[SERVER-24347] Mongod dies on start with Fatal assertion 28579 NoSuchKey Created: 01/Jun/16  Updated: 14/Jul/16  Resolved: 03/Jun/16

Status: Closed
Project: Core Server
Component/s: Storage, WiredTiger
Affects Version/s: 3.2.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Michael Assignee: Kelsey Schubert
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

1. Run out of log space
2. Reboot

Participants:

 Description   

Hey!

I am using Mongo DB 3.2. I have a non sharded environment. My OS is Ubuntu 14.04.

The instance ran out of log space, and thus it experienced an unclean shutdown. I followed through the standard lock removal and repair steps, but I keep getting this:

[initandlisten] Fatal assertion 28579 NoSuchKey Unable to find metadata for table:

My bug is essentially the one described here: https://jira.mongodb.org/browse/SERVER-19274

It says it was fixed in 3.2.0 but I am getting it now.

Any tips on how to fix this?



 Comments   
Comment by Michael [ 03/Jun/16 ]

Hi Thomas,

Sure. If we encounter the problem again, I'll let you know.

Best,
Michael

Comment by Kelsey Schubert [ 03/Jun/16 ]

Hi michael_xyz,

Thank you for the additional information. I'm glad that you were able to restore your database. Since you are unable to provide the files for analysis and have successfully restored your database, I am going to close this issue.

Best regards,
Thomas

Comment by Michael [ 03/Jun/16 ]

Hi Thomas

We managed to restore our data base.

Unfortunately, due to the sensitive nature of the information contained, we cannot upload our files.

If I can help you in another way, please let me know.

Best,
Michael

Comment by Kelsey Schubert [ 02/Jun/16 ]

Hi michael_xyz,

Thank you for reporting this issue. If it is possible, I would recommend creating a backup of your current database directory. To help us continue our investigation, would you please provide the following additional information?

  1. tarball of the WiredTiger files (_mdb_catalog.wt, sizeStorer.wt, WiredTiger* files)
  2. output of ls -l of the database directory
  3. output of ls -l of the journal directory
  4. last three journal files
  5. WiredTigerLog.<long number>
  6. the logs of the affected mongod

I have created a secure upload portal for you to use here. Files you upload to this portal will be visible only to MongoDB employees investigating this issue and are routinely deleted after some time.

Kind regards,
Thomas

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