2013-04-23 111 views
1

我配置了一个mongodb的capped集合,容量超过3G,在多次mongod崩溃后,但mongd.log.Howerver没有出错linux abrt已经核心转储mongod的,从核心转储信息如下:mongod崩溃(终止于信号5)

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*)() 

我MongoDB是2.4.1,在CentOS的6.3,16G内存和8cpus运行。 任何人都可以帮助我?非常感谢。

回答

0

提到的内存不足的错误使我怀疑,这可能是这个bug(V8内存泄漏)的发生:

https://jira.mongodb.org/browse/SERVER-9230

可以升级到2.4.2+,看看错误仍然发生在你​​身上?

+0

非常感谢,我会尝试升级到2.4.2+ – xiaokuang 2013-04-26 07:19:38