Error Message Reference (DOCS-335)

[DOCS-19] MongoDB exit code reference Created: 28/Dec/10  Updated: 27/Jul/16  Due: 28/Sep/12  Resolved: 15/Oct/12

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Major - P3
Reporter: Michael Conigliaro Assignee: Ed Costello
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-83 Document mongod error codes. Closed
Participants:
Days since reply: 10 years, 30 weeks, 6 days ago

 Description   

I recently had a replica set go down with an error like this in my syslog:

mongodb main process (24395) terminated with status 100

Unfortunately, my (obviously misconfigured) monitoring system cleared out my mongodb.log too, so I couldn't get check for error messages. But knowing what status code 100 meant may have been able to help.



 Comments   
Comment by Tyler [ 19/Jul/13 ]

In my case, I had a mongodb that wouldn't shutdown (I had run an apt-get dist-upgrade previously, not sure if it's related). I killed the process manually, then tried to start Mongo again with service mongodb start, but this was in the daemon.log:

Jul 18 20:14:19 systemname init: mongodb main process (7456) terminated with status 100

And wouldn't start. I googled, someone suggested it may be out of space, the VM has ~2GB free, and isn't limited by a reservation for root or anything. Then the person above mentioned a permission issue, so I went to the /var/lib/mongodb, did a listing, and noticed a lock file, so I removed it (knowing that there were no mongodb processes currently running).

rm mongod.lock

and I was able to successfully service mongodb start and everything was back to normal.

Comment by auto [ 15/Oct/12 ]

Author:

{u'date': u'2012-10-15T16:02:10-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-19: editing exit code reference page.
Branch: master
https://github.com/mongodb/docs/commit/70c3fc48a7b4625c937a346563c670779ba49e00

Comment by auto [ 15/Oct/12 ]

Author:

{u'date': u'2012-10-15T15:46:42-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-19
Branch: master
https://github.com/mongodb/docs/commit/8122236c4e674cad622666325317917469d8b84b

Comment by Dominik Gehl [ 26/Jul/12 ]

In my case, the above message was due to a permission error on the data directory

Comment by Michael Conigliaro [ 28/Dec/10 ]

Found in pch.h:

enum ExitCode {
    EXIT_CLEAN = 0 ,
    EXIT_BADOPTIONS = 2 ,
    EXIT_REPLICATION_ERROR = 3 ,
    EXIT_NEED_UPGRADE = 4 ,
    EXIT_KILL = 12 ,
    EXIT_ABRUBT = 14 ,
    EXIT_NTSERVICE_ERROR = 20 ,
    EXIT_JAVA = 21 ,
    EXIT_OOM_MALLOC = 42 ,
    EXIT_OOM_REALLOC = 43 ,
    EXIT_FS = 45 ,
    EXIT_CLOCK_SKEW = 47 ,
    EXIT_NET_ERROR = 48 ,
    EXIT_POSSIBLE_CORRUPTION = 60 , // this means we detected a possible corruption situation, like a buf overflow
    EXIT_UNCAUGHT = 100 , // top level exception that wasn't caught
    EXIT_TEST = 101 ,
};

Generated at Thu Feb 08 07:37:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.