Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Mongodb fail to start after showing this error...and not able to start it again..?Can u help me find out?

   *** glibc detected *** /usr/lib/mongodb/mongo: corrupted double-linked list: 0x000000000f750b50 ***
   Mon Nov 26 19:01:29 mongo got signal 11 (Segmentation fault), stack trace: 

======= Backtrace: =========


 ======= Memory map: ========
  00400000-0055c000 r-xp 00000000 fd:03 32385496     

   0075c000-00762000 r--p 0015c000 fd:03 32385496                                /usr/lib/mongodb/mongo

00762000-00765000 rw-p 00162000 fd:03 32385496 /usr/lib/mongodb/mongo

 00765000-00767000 rw-p 00765000 00:00 0 
0f74e000-0f961000 rw-p 0f74e000 00:00 0                                  [heap]

2b2db730d000-2b2db732e000 r-xp 00000000 fd:03 32112840 /lib/x86_64-linux-gnu/ 2b2db732e000-2b2db7331000 rw-p 2b2db732e000 00:00 0 2b2db7331000-2b2db7351000 rwxp 2b2db7331000 00:00 0 2b2db752d000-2b2db752e000 r--p 00020000 fd:03 32112840 /lib/x86_64-linux-gnu/ 2b2db752e000-2b2db7530000 rw-p 00021000 fd:03 32112840 /lib/x86_64-linux-gnu/ 2b2db7530000-2b2db7548000 r-xp 00000000 fd:03 32112843 /lib/x86_64-linux-gnu/ 2b2db7548000-2b2db7748000 ---p 00018000 fd:03 32112843 /lib/x86_64-linux-gnu/ 2b2db7748000-2b2db7749000 r--p 00018000 fd:03 32112843 /lib/x86_64-linux-gnu/ 2b2db7749000-2b2db774a000 rw-p 00019000 fd:03 32112843 /lib/x86_64-linux-gnu/ 2b2db774a000-2b2db774e000 rw-p 2b2db774a000 00:00 0 2b2db774e000-2b2db7836000 r-xp 00000000 fd:03 32380634 /usr/lib/x86_64-linux-gnu/ 2b2db7836000-2b2db7a35000 ---p 000e8000 fd:03 32380634 /usr/lib/x86_64-linux-gnu/ 2b2db7a35000-2b2db7a3d000 r--p 000e7000 fd:03 32380634 /usr/lib/x86_64-linux-gnu/ 2b2db7a3d000-2b2db7a3f000 rw-p 000ef000 fd:03 32380634 /usr/lib/x86_64-linux-gnu/ 2b2db7a3f000-2b2db7a55000 rw-p 2b2db7a3f000 00:00 0 2b2db7a55000-2b2db7a58000 r-xp 00000000 fd:03 32244866 /usr/lib/ 2b2db7a58000-2b2db7c57000 ---p 00003000 fd:03 32244866 /usr/lib/ 2b2db7c57000-2b2db7c58000 r--p 00002000 fd:03 32244866 /usr/lib/ 2b2db7c58000-2b2db7c59000 rw-p 00003000 fd:03 32244866 /usr/lib/ 2b2db7c59000-2b2db7c6d000 r-xp 00000000 fd:03 32244882 /usr/lib/ 2b2db7c6d000-2b2db7e6c000 ---p 00014000 fd:03 32244882 /usr/lib/ 2b2db7e6c000-2b2db7e6e000 r--p 00013000 fd:03 32244882 /usr/lib/ 2b2db7e6e000-2b2db7e6f000 rw-p 00015000 fd:03 32244882 /usr/lib/ 2b2db7e6f000-2b2db7e83000 r-xp 00000000 fd:03 32244880 /usr/lib/ 2b2db7e83000-2b2db8082000 ---p 00014000 fd:03 32244880

      Mon Nov 26 19:01:29 mongo got signal 6 (Aborted), stack trace: 

      Mon Nov 26 19:01:29 0x45e03f 0x457694 0x2b2db93d4d80 0x2b2db93d4d05 0x2b2db93d8ab6 0x2b2db940fa9b 0x2b2db94198d6 0x2b2db941b841 0x2b2db941f603 0x45bd92 0x45d319 0x2b2db93da961 0x458043 0x2b2db753fc60 0x2b2db93d4fe7 0x2b2db889b888 0x2b2db889d9de 0x2b2db889e0c8 0x2b2db8889061 0x2b2db88895b5 
 /usr/lib/mongodb/mongo(_ZN5mongo15printStackTraceERSo+0x1f) [0x45e03f]
 /usr/lib/mongodb/mongo(_Z12quitAbruptlyi+0x324) [0x457694]
 /lib/x86_64-linux-gnu/ [0x2b2db93d4d80]
 /lib/x86_64-linux-gnu/ [0x2b2db93d4d05]
 /lib/x86_64-linux-gnu/ [0x2b2db93d8ab6]
  /lib/x86_64-linux-gnu/ [0x2b2db940fa9b]
  /lib/x86_64-linux-gnu/ [0x2b2db94198d6]
  /lib/x86_64-linux-gnu/ [0x2b2db941b841]
  /lib/x86_64-linux-gnu/ [0x2b2db941f603]
 /usr/lib/mongodb/mongo(_ZN5boost6detail17sp_counted_impl_pIN5mongo7BSONObj6HolderEE7disposeEv+0x12) [0x45bd92]
  /usr/lib/mongodb/mongo(_ZN5boost6detail12shared_countD2Ev+0x49) [0x45d319]

/lib/x86_64-linux-gnu/ [0x2b2db93da961] /usr/lib/mongodb/mongo(_Z10quitNicelyi+0x53) [0x458043] /lib/x86_64-linux-gnu/ [0x2b2db753fc60] /lib/x86_64-linux-gnu/ [0x2b2db93d4fe7] /lib/ [0x2b2db889b888] /lib/ [0x2b2db889d9de] /lib/ [0x2b2db889e0c8] /lib/ [0x2b2db8889061] /lib/ [0x2b2db88895b5]

Any One have any idea?Why MongoDb Crashed?

OS:ubuntu 11.04 2.6.32-pony6-3



share|improve this question

closed as not a real question by EEAA, Ward, voretaq7 Dec 3 '12 at 3:25

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Throwing a badly formatted crash dump at us and expecting us to wade through it is poor form - you need to do some troubleshooting on your own and come to us with data. See here for some tips. – voretaq7 Dec 3 '12 at 3:25
up vote 1 down vote accepted

Delete lock file first located in /data/db/mongod.lock.

Repair mongo by running following command in terminal

mongod --repair
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.