MongoDB service error 1067 Issue : service not starting
This is a very annoying error that we cannot see origin. Some blogs refers that is a space limitation issue.
In the file mongodb.log, you will see the following things :
Tue Jan 15 19:45:39 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data Tue Jan 15 19:45:39 [initandlisten] ** see http://blog.mongodb.org/post/137788967/32-bit-limitations Tue Jan 15 19:45:39 [initandlisten] ** with --journal, the limit is lower Tue Jan 15 19:45:39 [initandlisten] Tue Jan 15 19:45:39 [initandlisten] db version v2.2.2, pdfile version 4.5 Tue Jan 15 19:45:39 [initandlisten] git version: d1b43b61a5308c4ad0679d34b262c5af9d664267 Tue Jan 15 19:45:39 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=0, build=6002, platform=2, service_pack='Service Pack 2') BOOST_LIB_VERSION=1_49 Tue Jan 15 19:45:39 [initandlisten] options: { bind_ip: "127.0.0.1", config: "c:wampbinmongodbmongodb-win32-i386-2.2.2confmongodb.conf", dbpath: "C:wampbinmongodbmongodb-win32-i386-2.2.2datadb", logappend: "true", logpath: "c:wampbinmongodbmongodb-win32-i386-2.2.2logsmongodb.log", port: 27017, rest: "true", service: true } Tue Jan 15 19:45:39 [initandlisten] Unable to check for journal files due to: boost::filesystem::basic_directory_iterator constructor: Le chemin d'accès spécifié est introuvable: "C:wampbinmongodbmongodb-win32-i386-2.2.2datadbjournal" Tue Jan 15 19:45:39 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
The solution :
To start mongodb after a forced shutdown, you’ll need to access folder /mongodb-2.0/data/into your Mongo database Application node, and remove the mongodb.lock file. Then you can start your mongodb service instance
Enjoy!