[SERVER-6619] Mongodb crashes after server failure Created: 27/Jul/12  Updated: 08/Mar/13  Resolved: 03/Dec/12

Status: Closed
Project: Core Server
Component/s: Internal Code, Stability, Storage
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Max Lapshin Assignee: Michael O'Brien
Resolution: Done Votes: 0
Labels: crash
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04 64bit, Linux 3.2.0-27 SMP, Intel Core i7, SSD


Operating System: Linux
Participants:

 Description   

Computer halted. After restart mongodb cannot start and fails with exception:

$ /usr/bin/mongod -vvvv --config /home/blh/mongodb.conf
all output going to: /var/log/blh/mongodb.log
Fri Jul 27 12:16:42 terminate() called, printing stack:
0x56de53 0x88fa3a 0x7f4978c36846 0x7f4978c36873 0x7f4978c3696e 0x577399 0x7b2a0b 0x526588 0x7f4977a3576d 0x529611
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x23) [0x56de53]
/usr/bin/mongod(_ZN5mongo11myterminateEv+0x3a) [0x88fa3a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb5846) [0x7f4978c36846]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb5873) [0x7f4978c36873]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb596e) [0x7f4978c3696e]
/usr/bin/mongod(_ZN5mongo11initLoggingERKSsb+0x549) [0x577399]
/usr/bin/mongod(_ZN5mongo7CmdLine5storeEiPPcRN5boost15program_options19options_descriptionES6_RNS4_30positional_options_descriptionERNS4_13variables_mapE+0xa8b) [0x7b2a0b]
/usr/bin/mongod(main+0xd58) [0x526588]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f4977a3576d]
/usr/bin/mongod() [0x529611]
Fri Jul 27 12:16:42 Got signal: 6 (Aborted).

Fri Jul 27 12:16:42 Backtrace:
0x56de53 0x8906ac 0x7f4977a4a4c0 0x7f4977a4a445 0x7f4977a4dbab 0x88fa3f 0x7f4978c36846 0x7f4978c36873 0x7f4978c3696e 0x577399 0x7b2a0b 0x526588 0x7f4977a3576d 0x529611
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x23) [0x56de53]
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x34c) [0x8906ac]
/lib/x86_64-linux-gnu/libc.so.6(+0x364c0) [0x7f4977a4a4c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4977a4a445]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4977a4dbab]
/usr/bin/mongod(_ZN5mongo11myterminateEv+0x3f) [0x88fa3f]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb5846) [0x7f4978c36846]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb5873) [0x7f4978c36873]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb596e) [0x7f4978c3696e]
/usr/bin/mongod(_ZN5mongo11initLoggingERKSsb+0x549) [0x577399]
/usr/bin/mongod(_ZN5mongo7CmdLine5storeEiPPcRN5boost15program_options19options_descriptionES6_RNS4_30positional_options_descriptionERNS4_13variables_mapE+0xa8b) [0x7b2a0b]
/usr/bin/mongod(main+0xd58) [0x526588]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f4977a3576d]
/usr/bin/mongod() [0x529611]

Database is valuable, so I can provide it upon request.



 Comments   
Comment by Michael O'Brien [ 03/Dec/12 ]

Hey Max,
Haven't heard from you in a while regarding this issue - if you have anything to follow up on, please feel free to re-open the ticket.

Comment by Michael O'Brien [ 31/Jul/12 ]

Max,
How were you able to determine that the directory was corrupted?
Would be good to try and figure out a way to reproduce this so we can work on a fix.

Comment by Max Lapshin [ 27/Jul/12 ]

I've found, what was the reason.

After server crash, contents of /var/log/blh/ was corrupted and thus /var/log/blh/mongodb.log wasn't available for writing.
This lead to mongodb crash.

It would be great to tell somehow about it, not crash.

Generated at Thu Feb 08 03:12:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.