[SERVER-43220] mongodb is not starting up Created: 06/Sep/19  Updated: 11/Nov/19  Resolved: 11/Nov/19

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

Type: Task Priority: Major - P3
Reporter: Sushil Rane Assignee: Carl Champain (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongod.log    
Participants:

 Description   

service mongod start

Starting mongod: 2019-09-06T18:44:47.720-0500 W CONTROL  [main] Option: storage.mmapv1.journal.commitIntervalMs is deprecated. Please use storage.journal.commitIntervalMs instead.

about to fork child process, waiting until server is ready for connections.

forked process: 3209

ERROR: child process failed, exited with error number 100

                                                           [FAILED]



 Comments   
Comment by Carl Champain (Inactive) [ 11/Nov/19 ]

Hi surane@adobe.com,

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

Regards,
Carl

Comment by Carl Champain (Inactive) [ 09/Oct/19 ]

Hi surane@adobe.com,

Any updates on this issue?

Comment by Carl Champain (Inactive) [ 10/Sep/19 ]

Hi surane@adobe.com,

Thanks for the report. 
This error message leads us to suspect some form of physical corruption. Please make a complete copy of the database's $dbpath directory to work off of and safeguard the current $dbpath.
Our ability to determine the source of this corruption depends greatly on your ability to provide:

  1. The logs for the affected node, including before, leading up to, and after the first sign of corruption.
  2. A description of the underlying storage mechanism in use, including details like:
    1. What file system and/or volume management system is in use?
    2. Is data storage locally attached or network-attached?
    3. Are disks RAIDed and if so how?
    4. Are disks SSDs or HDDs?
  3. A description of your backup method, if any.
  4. A description of your disks have been recently checked for integrity?
  5. A history of the deployment, including:
    1. a timeline of version changes
    2. a timeline of hardware upgrade/downgrade cycles or configuration changes
    3. a timeline of disaster recovery or backup restoration activities
    4. a timeline of any manipulations of the underlying database files, including copies or moves, and information about whether mongod was running during each manipulation.

The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair.

Importantly, 3.2 version of MongoDB is already end-of-lifed, you should upgrade to the latest 4.2.0 or 4.0.12.

Regards,
Carl
 

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