[SERVER-41384] Conf Server Failed to Start Created: 30/May/19  Updated: 16/Jul/19  Resolved: 16/Jul/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding, Storage
Affects Version/s: 4.0.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Steph Auon Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Conf Server Failed to start after repair   

 [repl writer worker] WTCursor::next - c->next_key (RecordId(-976)) was not greater than _lastReturnedId (RecordId(0)) which is a bug



 Comments   
Comment by Eric Sedor [ 16/Jul/19 ]

Hi,

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.

Regards,
Eric

Comment by Eric Sedor [ 28/Jun/19 ]

stephen.auon,

We still need specific information to diagnose this issue. If they are available, can you please upload the following to the secure upload portal we've created for you.

  • mongod log files leading up to the incident
  • The mongod logs of the --repair
  • The full mongod logs of the startup attempt after the repair

Thank you,
Eric

Comment by Eric Sedor [ 12/Jun/19 ]

Hi stephen.auon

Sorry if I have been unclear... we are still hoping to get the following information to help us:

  • mongod log files leading up to the incident
  • The mongod logs of the --repair
  • The full mongod logs of the startup attempt after the repair
Comment by Steph Auon [ 12/Jun/19 ]

We are still waiting 

Comment by Steph Auon [ 09/Jun/19 ]

Uploaded using the link

Comment by Eric Sedor [ 05/Jun/19 ]

Hi stephen.auon, we apologize for the delay.

I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time.

Can you please submit the files this way?

Comment by Steph Auon [ 31/May/19 ]

First there was a sudden power loss 
The OS is Ubuntu 16.04.1 the FileSystem is XFS
Then MongoDB (it's a replica set with one node only) failed to start 
with Fatal Assertion 50853
After that a --repair was tried 
then this error occured 
here's the link for diagnositic data zip on mozilla send service 
the link expires after 1 day 1 download 
https://send.firefox.com/download/9925ebe7f7580eb8/#clkTqi7oWvrSXNgFJRnIaw

Comment by Eric Sedor [ 30/May/19 ]

Hi stephen.auon,

Can you please provide:

  • Information about what led you to run repair, including logs leading up to that incident and the replica set state of the node before then (e.g., Primary, Secondary?)
  • The logs of the repair and the method used to initiate the repair
  • The full logs of the startup attempt after the repair

Would you please also archive (tar or zip) the $dbpath/diagnostic.data directory (described here) for the affected node, and attach it to this ticket?

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