Re: MongoDB crash with killed by signal 5 (SIGTRAP)

[kyo19...@gmail.com]

kyo19...@gmail.com於 2013年4月26日星期五UTC+8下午4時09分31秒寫道：

I've configured a capped collection in mongodb,with capacity more than 3G, and about 20 millions records which are updated very frequent.
After that,my mongod has crashed in a sudden for many times,but there was nothing wrong can be found in mongod.log. Howerver linux abrt
has made core dump for mongod each time it was crashed.Messages from the core dump file are as following:

Program terminated with signal 5, Trace/breakpoint trap.
#0  0x00000000010b9951 in v8::internal::OS::DebugBreak() ()
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6.x86_64 libgcc-4.4.7-3.el6.x86_64 libstdc++-4.4.6-4.el6.x86_64
(gdb) where
#0  0x00000000010b9951 in v8::internal::OS::DebugBreak() ()
#1  0x00000000010ba06a in v8::internal::OS::Abort() ()
#2  0x0000000000f1c5f3 in API_Fatal(char const*, char const*, ...) ()
#3  0x0000000000ece607 in ?? ()
#4  0x0000000000ece916 in v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) ()
#5  0x000000000108c891 in v8::internal::Map::UpdateCodeCache(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::Code>) ()
#6  0x0000000001149180 in v8::internal::StubCache::ComputeKeyedLoadOrStoreElement(v8::internal::Handle<v8::internal::Map>, v8::internal::KeyedIC::StubKind, v8::internal::StrictModeFlag) ()
#7  0x0000000001000bfc in v8::internal::KeyedIC::ComputeMonomorphicStub(v8::internal::Handle<v8::internal::Map>, v8::internal::KeyedIC::StubKind, v8::internal::StrictModeFlag, v8::internal::Handle<v8::internal::Code>) ()
#8  0x000000000100779a in v8::internal::KeyedIC::ComputeStub(v8::internal::Handle<v8::internal::JSObject>, v8::internal::KeyedIC::StubKind, v8::internal::StrictModeFlag, v8::internal::Handle<v8::internal::Code>) ()
#9  0x0000000001008551 in v8::internal::KeyedLoadIC::Load(v8::internal::InlineCacheState, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, bool) ()
#10 0x000000000100894d in v8::internal::KeyedLoadIC_Miss(v8::internal::Arguments, v8::internal::Isolate*) ()

    My mongodb version is 2.4.1,running in centos 6.3,16G memeory,8 cups.

Anyone can help me?Thanks a lot.

[Andrew Morrow]

From the stack trace you provided, it looks as if mongod ran out of memory. You mention that you are running 2.4.1. I recommend upgrading MongoDB to version 2.4.3, released this week. MongoDB 2.4.1 has some known memory management issues which have been resolved in more recent releases.

--
--
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com
To unsubscribe from this group, send email to
mongodb-user...@googlegroups.com
See also the IRC channel -- freenode.net#mongodb
 
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.