什么会导致mongodb中出现分段错误

什么会导致mongodb中出现分段错误,mongodb,Mongodb,我们有一个mongodb副本集,在一个因分段错误而崩溃的成员上。是什么导致了这个问题?我们正在运行版本2.2.2 谢谢。这是坠机日志 Mon Sep 2 03:37:26 Invalid access at address: 0xfffffd7d00680038 from thread: conn2014070 Mon Sep 2 03:37:26 Got signal: 11 (Segmentation Fault). Mon Sep 2 03:37:26 Backtrace: 0x

我们有一个mongodb副本集,在一个因分段错误而崩溃的成员上。是什么导致了这个问题?我们正在运行版本2.2.2

谢谢。这是坠机日志

Mon Sep  2 03:37:26 Invalid access at address: 0xfffffd7d00680038 from thread: conn2014070

Mon Sep  2 03:37:26 Got signal: 11 (Segmentation Fault).

Mon Sep  2 03:37:26 Backtrace:
0xb331b8 0x7bd48b 0x7bd695 0xfffffd7fff1d7666 0xfffffd7fff1ca35c 0x9ff980 0x873f13 0x873fcb 0x981331 0x982af2 0x92d2da 0x93183b 0x7cead0 0xb2539a 0xfffffd7ff95f364c 0xfffffd7fff1d72d4 0xfffffd7fff1d75a0 
 /opt/local/bin/mongod'_ZN5mongo15printStackTraceERSo+0x28 [0xb331b8]
 /opt/local/bin/mongod'_ZN5mongo10abruptQuitEi+0x11b [0x7bd48b]
 /opt/local/bin/mongod'_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x125 [0x7bd695]
 /lib/amd64/libc.so.1'__sighndlr+0x6 [0xfffffd7fff1d7666]
 /lib/amd64/libc.so.1'call_user_handler+0x2a4 [0xfffffd7fff1ca35c]
 /opt/local/bin/mongod'_ZNK5mongo6Record5touchEb+0x0 [0x9ff980]
 /opt/local/bin/mongod'_ZN5mongo12ClientCursor5yieldEiPNS_6RecordE+0x63 [0x873f13]
 /opt/local/bin/mongod'_ZN5mongo12ClientCursor14yieldSometimesENS0_11RecordNeedsEPb+0x6b [0x873fcb]
 /opt/local/bin/mongod'_ZN5mongo14_updateObjectsEbPKcRKNS_7BSONObjES4_bbbRNS_7OpDebugEPNS_11RemoveSaverEbRKNS_24QueryPlanSelectionPolicyEb+0x9a1 [0x981331]
 /opt/local/bin/mongod'_ZN5mongo13updateObjectsEPKcRKNS_7BSONObjES4_bbbRNS_7OpDebugEbRKNS_24QueryPlanSelectionPolicyE+0xa2 [0x982af2]
 /opt/local/bin/mongod'_ZN5mongo14receivedUpdateERNS_7MessageERNS_5CurOpE+0x27a [0x92d2da]
 /opt/local/bin/mongod'_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xe9b [0x93183b]
 /opt/local/bin/mongod'_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x90 [0x7cead0]
 /opt/local/bin/mongod'_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x32a [0xb2539a]
 /opt/local/lib/libboost_thread.so.1.49.0'thread_proxy+0x6c [0xfffffd7ff95f364c] /lib/amd64/libc.so.1'_thrp_setup+0xbc [0xfffffd7fff1d72d4]
 /lib/amd64/libc.so.1'_lwp_start+0x0 [0xfffffd7fff1d75a0]
此外,我在崩溃之前看到一些断言失败,我不确定它们是否相关。除此之外,就我所知,没有什么是不寻常的

Wed Sep  4 02:19:04 [conn988803]  cratefm Assertion failure !e.eoo() src/mongo/db/../bson/bsonobjbuilder.h 131
0xb331b8 0xb01e70 0x7cbe04 0x88e7ec 0x8b5f18 0x8b6b66 0x8b714a 0x978044 0x97ab32 0x931065 0x7cead0 0xb2539a 0xfffffd7fdd1a364c 0xfffffd7fff1d72d4 0xfffffd7fff1d75a0 
 /opt/local/bin/mongod'_ZN5mongo15printStackTraceERSo+0x28 [0xb331b8]
 /opt/local/bin/mongod'_ZN5mongo12verifyFailedEPKcS1_j+0xc0 [0xb01e70]
 /opt/local/bin/mongod'0x3cbe04 [0x7cbe04]
 /opt/local/bin/mongod'_ZN5mongo16CmdFindAndModify3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x65c [0x88e7ec]
 /opt/local/bin/mongod'_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRNS_14BSONObjBuilderEb+0x48 [0x8b5f18]
 /opt/local/bin/mongod'_ZN5mongo11execCommandEPNS_7CommandERNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0xa26 [0x8b6b66]
 /opt/local/bin/mongod'_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x37a [0x8b714a]
 /opt/local/bin/mongod'_ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x34 [0x978044]
 /opt/local/bin/mongod'_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x6c2 [0x97ab32]
 /opt/local/bin/mongod'_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x6c5 [0x931065]
 /opt/local/bin/mongod'_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x90 [0x7cead0]
 /opt/local/bin/mongod'_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x32a [0xb2539a]
 /opt/local/lib/libboost_thread.so.1.49.0'thread_proxy+0x6c [0xfffffd7fdd1a364c]
 /lib/amd64/libc.so.1'_thrp_setup+0xbc [0xfffffd7fff1d72d4]
 /lib/amd64/libc.so.1'_lwp_start+0x0 [0xfffffd7fff1d75a0]

确保您的客户端版本>=服务器版本


查看

在更新包含128个以上BSON元素的文档上的数组时,这是2.6版本的一个错误:


正如他们所说,它是自2.6.1版本以来修正的,所以我鼓励你像我一样升级,现在一切都很适合我

我有好几次sig故障。您应该发布此消息以考虑升级到最新的2.2版本吗?2.2.6是当前版本-自2.2.2以来,许多错误已修复。此外,没有提供足够的日志-导致坠机的直接原因是什么?坠机前没有任何异常情况。这已经开始比最近随机发生的更频繁了。我可能会升级到2.2.6,但在此之前,我想确保我没有遗漏任何东西。我们的机器托管在joyent,我发现了以下错误的引用-可能是它吗?