在mongo中恢复期间的异常 [英] exception during recovery in mongo

问题描述

我试图从mongo的突然关闭中恢复，如这篇文章所述，作者: fady mohamed osman ，但是我遇到了一些问题.这是日志文件

I tried to recover from sudden shutdown of mongo , as written in this post by: fady mohamed osman, but i am experiencing some problems. Here is the log file

我的日志是:

Tue Apr 16 17:45:25 [initandlisten] MongoDB starting : pid=3563 port=27017 dbpath=/var/lib/mongodb 64-bit host=milos-desktop
Tue Apr 16 17:45:25 [initandlisten] db version v2.0.2, pdfile version 4.5
Tue Apr 16 17:45:25 [initandlisten] git version: 514b122d308928517f5841888ceaa4246a7f18e3
Tue Apr 16 17:45:25 [initandlisten] build info: Linux bs-linux64.10gen.cc 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
Tue Apr 16 17:45:25 [initandlisten] options: { auth: "true", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", logappend: "true", logpath: "/var/log/mongodb/mongodb1.log", repair: true }
Tue Apr 16 17:45:25 [initandlisten] journal dir=/var/lib/mongodb/journal
Tue Apr 16 17:45:25 [initandlisten] recover begin
Tue Apr 16 17:45:25 [initandlisten] recover lsn: 77394770
Tue Apr 16 17:45:25 [initandlisten] recover /var/lib/mongodb/journal/j._0
Tue Apr 16 17:45:25 [initandlisten] journal file version number mismatch. recover with old version of mongod, terminate cleanly, then upgrade.
Tue Apr 16 17:45:25 [initandlisten] exception during recovery
Tue Apr 16 17:45:25 [initandlisten] exception in initAndListen: 13536 journal version number mismatch 0, terminating
Tue Apr 16 17:45:25 dbexit: 
Tue Apr 16 17:45:25 [initandlisten] shutdown: going to close listening sockets...
Tue Apr 16 17:45:25 [initandlisten] shutdown: going to flush diaglog...
Tue Apr 16 17:45:25 [initandlisten] shutdown: going to close sockets...
Tue Apr 16 17:45:25 [initandlisten] shutdown: waiting for fs preallocator...
Tue Apr 16 17:45:25 [initandlisten] shutdown: lock for final commit...
Tue Apr 16 17:45:25 [initandlisten] shutdown: final commit...
Tue Apr 16 17:45:25 [initandlisten] shutdown: closing all files...
Tue Apr 16 17:45:25 [initandlisten] closeAllFiles() finished
Tue Apr 16 17:45:25 [initandlisten] shutdown: removing fs lock...
Tue Apr 16 17:45:25 dbexit: really exiting now

推荐答案

由于错误

This can also happen because of unclean restarts/ shutdown as explained in the bug SERVER-5380. Remove all the files in /db/data/journal (maybe different for your setup, you can confirm this in the log generated while starting the service) folder and restart the service.

这篇关于在mongo中恢复期间的异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！