Unable to start the problem after MongoDB is not properly shut down

The problem cannot be started after MongoDB is not properly closed:

http://my.oschina.net/GivingOnenessDestiny/blog/53804

http://codingstandards.iteye.com/blog/1214093

Some time ago accidentally closed MongoDB, ready to restart but found no, the error message is as follows:

?

1234567891011121314151617181920212223242526

Tue Apr 17 11:13:30Tue Apr 17 11:13:30 warning: 32-bit servers don‘t have journaling enabled by default. Please use --journal if you want durability.Tue Apr 17 11:13:30Tue Apr 17 11:13:30 [initandlisten] MongoDB starting : pid=7128 port=27017 dbpath=D:\Programs\mongodb204\db 32-bit host=FALCONTue Apr 17 11:13:30 [initandlisten]Tue Apr 17 11:13:30 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of dataTue Apr 17 11:13:30 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitationsTue Apr 17 11:13:30 [initandlisten] **       with --journal, the limit is lowerTue Apr 17 11:13:30 [initandlisten]Tue Apr 17 11:13:30 [initandlisten] db version v2.0.4, pdfile version 4.5Tue Apr 17 11:13:30 [initandlisten] git version: 329f3c47fe8136c03392c8f0e548506cb21f8ebfTue Apr 17 11:13:30 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=0, build=6002, platform=2, service_pack=‘Service Pack 2‘)BOOST_LIB_VERSION=1_42Tue Apr 17 11:13:30 [initandlisten] options: { dbpath: "D:\Programs\mongodb204\db" }**************Unclean shutdown detected.Please visit http://dochub.mongodb.org/core/repair for recovery instructions.*************Tue Apr 17 11:13:30 [initandlisten] exception in initAndListen: 12596 old lock file, terminatingTue Apr 17 11:13:30 dbexit:Tue Apr 17 11:13:30 [initandlisten] shutdown: going to close listening sockets...Tue Apr 17 11:13:30 [initandlisten] shutdown: going to flush diaglog...Tue Apr 17 11:13:30 [initandlisten] shutdown: going to close sockets...Tue Apr 17 11:13:30 [initandlisten] shutdown: waiting for fs preallocator...Tue Apr 17 11:13:30 [initandlisten] shutdown: closing all files...Tue Apr 17 11:13:30 [initandlisten] closeAllFiles() finishedTue Apr 17 11:13:30 dbexit: really exiting now

Workaround:

1. Delete the. lock file under%mongo_home%/db

2. Input command Mongod--repair

3. Restart MongoDB

Unable to start the problem after MongoDB is not properly shut down