Details
-
Bug
-
Resolution: Incomplete
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/tutorial/recover-data-following-unexpected-shutdown/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 SE 2.X MetaSr 1.0
*Referrer*: http://comments.gmane.org/gmane.comp.db.mongodb.user/80739
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: tutorial/recover-data-following-unexpected-shutdown
*Location*: http://docs.mongodb.org/manual/tutorial/recover-data-following-unexpected-shutdown/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 SE 2.X MetaSr 1.0 *Referrer*: http://comments.gmane.org/gmane.comp.db.mongodb.user/80739 *Screen Resolution*: 1440 x 900 *repo*: docs *source*: tutorial/recover-data-following-unexpected-shutdown
Description
rsBackgroundSync] replSet syncing to: 192.168.20.141:27017
Thu Jul 30 10:19:42 [rsSync] replSet still syncing, not yet to minValid optime 55b7295b:1
Thu Jul 30 10:19:42 [repl writer worker 1] ERROR: writer worker caught exception: bad offset:0 accessing file: /data/mongodb/master/chat/chat.0 - consider repairing database on: { ts: Timestamp 1438067035000|1, h: -1699621508567254689, v: 2, op: "i", ns: "chat.msg_91wan", o:
}
Thu Jul 30 10:19:42 [repl writer worker 1] Fatal Assertion 16360
0xb10fc1 0xad61c3 0x9adba6 0xae44dd 0xb56d39 0x3954e0673d 0x39546d3d1d
/usr/local/mongodb/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xb10fc1]
/usr/local/mongodb/bin/mongod(_ZN5mongo13fassertFailedEi+0xa3) [0xad61c3]
/usr/local/mongodb/bin/mongod(_ZN5mongo7replset14multiSyncApplyERKSt6vectorINS_7BSONObjESaIS2_EEPNS0_8SyncTailE+0x156) [0x9adba6]
/usr/local/mongodb/bin/mongod(_ZN5mongo10threadpool6Worker4loopEv+0x26d) [0xae44dd]
/usr/local/mongodb/bin/mongod [0xb56d39]
/lib64/libpthread.so.0 [0x3954e0673d]
/lib64/libc.so.6(clone+0x6d) [0x39546d3d1d]
Thu Jul 30 10:19:42 [repl writer worker 1]
***aborting after fassert() failure