Exit Codes and Statuses for a Self-Managed Deployment
MongoDB will return one of the following codes and statuses when
exiting. Use this guide to interpret logs and when troubleshooting
issues with mongod
and mongos
instances.
Code | Cause |
---|---|
Returned by MongoDB applications upon successful exit. | |
Returned by mongod as a generic failure when no
other error codes apply. | |
The specified options are in error or are incompatible
with other options. | |
Returned by mongod if there is a mismatch between
hostnames specified on the command line and in the
local.sources collection when running a replica set. | |
The version of the database is different from the version
supported by the mongod (or
mongod.exe ) instance. The instance exits
cleanly. | |
Returned by mongos if a problem is encountered
during initialization. | |
Returned by the mongod.exe process on Windows
when it receives a Control-C, Close, Break or Shutdown event. | |
Returned by MongoDB applications which encounter an
unrecoverable error, an uncaught exception or uncaught signal.
The system exits without performing a clean shutdown. | |
Message: Returned by MongoDB applications on Windows following an error in the WSAStartup function, used to initialize the networking subsystem. Message: Returned by MongoDB applications for Windows due to failures installing, starting or removing the NT Service for the application. | |
Returned by mongod during server initialization
if it fails to fork the process. | |
Returned by mongod during server initialization
if the daemon fails to send a ready signal. The process exits
cleanly. | |
Returned by the Storage Node Watchdog if any of the
filesystems with monitored directories are unresponsive. | |
Returned by To resolve data incompatibility issues after upgrading, please refer to the release notes for your version of MongoDB and search for "Changes Affecting Compatibility." | |
Returned by mongod when the process throws an
uncaught exception. | |