Docs Menu

/

/

Self-Managed Deployments

/

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
`0`	Returned by MongoDB applications upon successful exit.
`2`	The specified options are in error or are incompatible with other options.
`3`	Returned by `mongod` if there is a mismatch between hostnames specified on the command line and in the `local.sources` collection, in master/slave mode.
`4`	The version of the database is different from the version supported by the `mongod` (or `mongod.exe`) instance. The instance exits cleanly.
`5`	Returned by `mongos` if a problem is encountered during initialization.
`12`	Returned by the `mongod.exe` process on Windows when it receives a Control-C, Close, Break or Shutdown event.
`14`	Returned by MongoDB applications which encounter an unrecoverable error, an uncaught exception or uncaught signal. The system exits without performing a clean shutdown.
`20`	Message: `ERROR: wsastartup failed <reason>` Returned by MongoDB applications on Windows following an error in the WSAStartup function, used to initialize the networking subsystem. Message: `NT Service Error` Returned by MongoDB applications for Windows due to failures installing, starting or removing the NT Service for the application.
`48`	A newly started `mongod` or `mongos` could not start listening for incoming connections, due to an error.
`61`	Returned by the Storage Node Watchdog if any of the filesystems with monitored directories are unresponsive.
`62`	Returned by `mongod` if the datafiles in `--dbpath` are incompatible with the version of `mongod` currently running.
`100`	Returned by `mongod` when the process throws an uncaught exception.

Back

Troubleshoot SNMP

Next

Security