[SERVER-9595] Another occasional segfault in mongo server Created: 06/May/13  Updated: 10/Dec/14  Resolved: 16/May/13

Status: Closed
Project: Core Server
Component/s: JavaScript, MapReduce
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Greenhoe Assignee: Ben Becker
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux Centos 6.3


Issue Links:
Duplicate
duplicates SERVER-9594 Occasional segfault in server Closed
Operating System: ALL
Steps To Reproduce:

This one seems similar to, but not the same as SERVER-9594.

Server under heavy load, with a complex M/R function.

I can't give more precise STR then that, unfortunately, as we have multiple complex M/R functions. When we have more precise information, we will attach it to this bug.

Participants:

 Description   

Mon Apr 22 12:14:34 Invalid access at address: 0 from thread: conn2

Mon Apr 22 12:14:34 Got signal: 11 (Segmentation fault: 11).

Mon Apr 22 12:14:34 Backtrace:
0x107fb990b 0x107c3fbe1 0x107c3fa92 0x7fff8adcc94a 0x4000 0x107f90eea 0x107d18241 0x107d1fe22 0x107d397ab 0x107d3a5f2 0x107d3af14 0x107dfa96e 0x107dfb107 0x107db062d 0x107c493a2 0x107faff3d 0x107feafc5 0x7fff8adde7a2 0x7fff8adcb1e1
0 mongod 0x0000000107fb990b _ZN5mongo15printStackTraceERSo + 43
1 mongod 0x0000000107c3fbe1 _ZN5mongo10abruptQuitEi + 225
2 mongod 0x0000000107c3fa92 ZN5mongo24abruptQuitWithAddrSignalEiP9_siginfoPv + 242
3 libsystem_c.dylib 0x00007fff8adcc94a _sigtramp + 26
4 ??? 0x0000000000004000 0x0 + 16384
5 mongod 0x0000000107f90eea _ZN5mongo7SMScope4initEPKNS_7BSONObjE + 226
6 mongod 0x0000000107d18241 _ZN5mongo2mr5State4initEv + 245
7 mongod 0x0000000107d1fe22 _ZN5mongo2mr16MapReduceCommand3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb + 2314
8 mongod 0x0000000107d397ab _ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRNS_14BSONObjBuilderEb + 91
9 mongod 0x0000000107d3a5f2 _ZN5mongo11execCommandEPNS_7CommandERNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb + 2338
10 mongod 0x0000000107d3af14 _ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi + 1076
11 mongod 0x0000000107dfa96e _ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi + 46
12 mongod 0x0000000107dfb107 ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1 + 1447
13 mongod 0x0000000107db062d _ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE + 1309
14 mongod 0x0000000107c493a2 _ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE + 206
15 mongod 0x0000000107faff3d _ZN5mongo3pms9threadRunEPNS_13MessagingPortE + 1645
16 mongod 0x0000000107feafc5 thread_proxy + 229
17 libsystem_c.dylib 0x00007fff8adde7a2 _pthread_start + 327
18 libsystem_c.dylib 0x00007fff8adcb1e1 thread_start + 13



 Comments   
Comment by Ben Becker [ 16/May/13 ]

This appears to be due to an allocation failure; similar. SMScope::init() calls two Converter functions which fail to check for error conditions (similar to SERVER-9594), but it's not clear which one caused this failure.

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