[SERVER-10571] V2.2 Linux 32 segfault inside GhostSync::updateSlave Created: 19/Aug/13  Updated: 10/Dec/14  Resolved: 16/Jan/14

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 2.2.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Matt Kangas
Resolution: Won't Fix Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

buildbot V2.2 Linux 32 bit


Participants:

 Description   

V2.2 Linux 32-bit recently segfaulted during replsets/tags2.js

Regrettably there is NO additional history in buildlogger to be examined. Older failures have all been aged out.

Were there any fixes to GhostSync that made it into 2.4 but not 2.2? The only relevant ghostsync tickets I see are SERVER-9853 and SERVER-8420


V2.2 Linux 32 build 315

 m31000| Sun Aug 18 07:24:32 [conn1] command test.$cmd command: { getLastError: 1.0, w: "backedUp", wtimeout: 20000.0 } ntoreturn:1 keyUpdates:0  reslen:94 1271ms
 m31000| Sun Aug 18 07:24:32 [conn1] replSet replSetReconfig config object parses ok, 3 members specified
 m31000| Sun Aug 18 07:24:32 [conn1] replSet replSetReconfig [2]
 m31000| Sun Aug 18 07:24:32 [conn1] replSet info saving a newer config version to local.system.replset
 m31000| Sun Aug 18 07:24:33 [conn1] replSet saveConfigLocally done
 m31000| Sun Aug 18 07:24:33 [conn1] replSet info : additive change to configuration
 m31000| Sun Aug 18 07:24:33 Invalid access at address: 0x20 from thread: conn10
 m31000| 
 m31000| Sun Aug 18 07:24:33 Got signal: 11 (Segmentation fault).
 m31000| 
 m31000| Sun Aug 18 07:24:33 [conn1] replSet replSetReconfig new config saved locally
 m31000| Sun Aug 18 07:24:33 Backtrace:
 m31000| 0x876a15a 0x817189a 0x8171f5f 0x110440 0x85be66d 0x85f92f2 0x85fd746 0x828c57e 0x8471420 0x83e8344 0x83eb8eb 0x81922c4 0x875683d 0xc2e542 0x812b6e 
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo15printStackTraceERSo+0x2a) [0x876a15a]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo10abruptQuitEi+0x3ba) [0x817189a]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x2af) [0x8171f5f]
 m31000|  [0x110440]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo13ReplSetConfig11TagSubgroup10updateLastERKNS_6OpTimeE+0x1d) [0x85be66d]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo9GhostSync11updateSlaveERKNS_3OIDERKNS_6OpTimeE+0x3d2) [0x85f92f2]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo19updateSlaveLocationERNS_5CurOpEPKcNS_6OpTimeE+0x326) [0x85fd746]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo12ClientCursor19updateSlaveLocationERNS_5CurOpE+0x3e) [0x828c57e]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo14processGetMoreEPKcixRNS_5CurOpEiRb+0x8a0) [0x8471420]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo15receivedGetMoreERNS_10DbResponseERNS_7MessageERNS_5CurOpE+0x10a4) [0x83e8344]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x9fb) [0x83eb8eb]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x84) [0x81922c4]
 m31000|  /mnt/slaves/Linux_32bit_V2.2/mongo/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x42d) [0x875683d]
 m31000|  /lib/i686/nosegneg/libpthread.so.0 [0xc2e542]
 m31000|  /lib/i686/nosegneg/libc.so.6(clone+0x5e) [0x812b6e]



 Comments   
Comment by Eric Milkie [ 19/Aug/13 ]

I think this segfault can be avoided if we backport SERVER-9333

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