mongoDB非正常關閉後無法啟動問題

瓜瓜東西發表於2014-09-13
MongoDB
前段時間不小心非正常關閉了mongoDB，準備重啟卻發現不行，錯誤資訊如下：
 
01
Tue Apr 17 11:13:30
02  www.2cto.com  
Tue Apr 17 11:13:30 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
03
Tue Apr 17 11:13:30
04
Tue Apr 17 11:13:30 [initandlisten] MongoDB starting : pid=7128 port=27017 dbpath=D:\Programs\mongodb204\db 32-bit host=FALCON
05
Tue Apr 17 11:13:30 [initandlisten]
06
Tue Apr 17 11:13:30 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data
07
Tue Apr 17 11:13:30 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations
08
Tue Apr 17 11:13:30 [initandlisten] **       with --journal, the limit is lower
09
Tue Apr 17 11:13:30 [initandlisten]
10
Tue Apr 17 11:13:30 [initandlisten] db version v2.0.4, pdfile version 4.5
11  www.2cto.com  
Tue Apr 17 11:13:30 [initandlisten] git version: 329f3c47fe8136c03392c8f0e548506cb21f8ebf
12
Tue 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_42
13
Tue Apr 17 11:13:30 [initandlisten] options: { dbpath: "D:\Programs\mongodb204\db" }
14
**************
15
Unclean shutdown detected.
16
Please visit http://dochub.mongodb.org/core/repair for recovery instructions.
17
*************
18
Tue Apr 17 11:13:30 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
19
Tue Apr 17 11:13:30 dbexit:
20
Tue Apr 17 11:13:30 [initandlisten] shutdown: going to close listening sockets...
21
Tue Apr 17 11:13:30 [initandlisten] shutdown: going to flush diaglog...
22
Tue Apr 17 11:13:30 [initandlisten] shutdown: going to close sockets...
23  www.2cto.com  
Tue Apr 17 11:13:30 [initandlisten] shutdown: waiting for fs preallocator...
24
Tue Apr 17 11:13:30 [initandlisten] shutdown: closing all files...
25
Tue Apr 17 11:13:30 [initandlisten] closeAllFiles() finished
26
Tue Apr 17 11:13:30 dbexit: really exiting now
 
解決方法：
 
1、刪除%MONGO_HOME%/db下的.lock檔案
 
2、輸入命令 mongod --repair
 
3、重啟mongoDB
 
 
 
作者 在雲端-看世間變幻

相關文章