For some reason, I couldn’t run mongo shell and the console was overrun by the same error message like the following.
8/1/11 6:49:15 PMcom.apple.launchd
\[1\](org.mongodb.mongod) Throttling respawn: Will start in 10 seconds
8/1/11 6:49:25 PMcom.apple.launchd
\[1\](org.mongodb.mongod
\[394\]) Exited with exit code: 100
8/1/11 6:49:15 PM com.apple.launchd[1] (org.mongodb.mongod) Throttling respawn: Will start in 10 seconds
8/1/11 6:49:25 PM com.apple.launchd[1] (org.mongodb.mongod[394]) Exited with exit code: 100And searching on Google didn’t turn up any interesting results.
IT PAYS TO LOOK AT YOUR LOG FILE! Well, this shouldn’t be new, but it somehow skipped my mind until I saw the config file.
In the log file was the following helpful error message.
**************
old lock file: /usr/local/mongodb_data/mongod.lock. probably means unclean shutdown
recommend removing file and running --repair
see: http://dochub.mongodb.org/core/repair for more information
*************
Mon Aug 1 18:49:35 [initandlisten] exception in initAndListen std::exception: old lock file, terminatingMon Aug 1 18:49:35 dbexit:
Mon Aug 1 18:49:35 [initandlisten] shutdown: going to close listening sockets...
Mon Aug 1 18:49:35 [initandlisten] shutdown: going to flush diaglog...
Mon Aug 1 18:49:35 [initandlisten] shutdown: going to close sockets...
Mon Aug 1 18:49:35 [initandlisten] shutdown: waiting for fs preallocator...
Mon Aug 1 18:49:35 [initandlisten] shutdown: closing all files...
Mon Aug 1 18:49:35 closeAllFiles() finished
Mon Aug 1 18:49:35 dbexit: really exiting nowWell, after deleting the lock file, everything was back to normal.