Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-11317

replsets:slavedelay1.js failed on V2.4 Linux 32-bit

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
    • Fully Compatible
    • ALL

      V2.4 Linux 32-bit Build #242 rev 8997835c0 (Tue Oct 22)
      http://buildlogs.mongodb.org/V2.4%20Linux%2032-bit/builds/242/test/replica%20sets/slavedelay1.js

      All members are now in state PRIMARY, SECONDARY, or ARBITER
      
      reconfigure slavedelay
       m31000| Tue Oct 22 06:42:25.762 [conn1] replSet replSetReconfig config object parses ok, 4 members specified
       m31000| Tue Oct 22 06:42:25.763 [conn1] replSet replSetReconfig [2]
       m31000| Tue Oct 22 06:42:25.763 [conn1] replSet info saving a newer config version to local.system.replset
       m31000| Tue Oct 22 06:42:25.764 [conn1] replSet saveConfigLocally done
      
      ...
       m31000| Tue Oct 22 06:42:25.769 [rsMgr] not electing self, bs-linux32.10gen.cc:31003 would veto with 'I don't think bs-linux32.10gen.cc:31000 is electable'
       m31001| Tue Oct 22 06:42:25.770 [rsSyncNotifier] replset tracking exception: exception: 10278 dbclient error communicating with server: bs-linux32.10gen.cc:31000
       m31000| Tue Oct 22 06:42:25.771 [rsMgr] not electing self, bs-linux32.10gen.cc:31003 would veto with 'I don't think bs-linux32.10gen.cc:31000 is electable'
       m31000| Tue Oct 22 06:42:25.771 [conn11] SocketException handling request, closing client connection: 9001 socket exception [SEND_ERROR] server [10.255.119.66:33446] 
       m31002| Tue Oct 22 06:42:25.772 [rsSyncNotifier] replset tracking exception: exception: 10278 dbclient error communicating with server: bs-linux32.10gen.cc:31000
      Tue Oct 22 06:42:25.810 ERROR: MessagingPort::call() wrong id got:1aa expect:2ac
        toSend op: 2004
        response msgid:551
        response len:  233
        response op:  1
        remote: 127.0.0.1:31000
      Tue Oct 22 06:42:25.826   Assertion failure false src/mongo/util/net/message_port.cpp 246
      0x836b17d 0x834c395 0x832e6de 0x8357537 0x83577a7 0x825fcdc 0x828e4e3 0x824fd2b 0x8268e6f 0x832286b 0x8306247 0x3fd5709c 0x41d77bf9 0x3fd0f321 0x41d77227 0x3fd5536d 0x3fd13545 0x3fd0f321 0x3fd52cc3 0x3fd54fab 
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo15printStackTraceERSo+0x2d) [0x836b17d]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo10logContextEPKc+0xa5) [0x834c395]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo12verifyFailedEPKcS1_j+0x12e) [0x832e6de]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo13MessagingPort4recvERKNS_7MessageERS1_+0x2e7) [0x8357537]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo13MessagingPort4callERNS_7MessageES2_+0x47) [0x83577a7]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo18DBClientConnection4callERNS_7MessageES2_bPSs+0x4c) [0x825fcdc]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo14DBClientCursor4initEv+0xc3) [0x828e4e3]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo12DBClientBase5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0xbb) [0x824fd2b]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo18DBClientConnection5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0x7f) [0x8268e6f]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo9mongoFindEPNS_7V8ScopeERKN2v89ArgumentsE+0x3eb) [0x832286b]
       /mnt/slaves/Linux_32bit_V2.4/mongo/mongo(_ZN5mongo7V8Scope10v8CallbackERKN2v89ArgumentsE+0xe7) [0x8306247]
       [0x3fd5709c]
       [0x41d77bf9]
       [0x3fd0f321]
       [0x41d77227]
       [0x3fd5536d]
       [0x3fd13545]
       [0x3fd0f321]
       [0x3fd52cc3]
       [0x3fd54fab]
      ReplSetTest Could not call ismaster on node 0: Error: assertion src/mongo/util/net/message_port.cpp:246
       m31001| Tue Oct 22 06:42:26.000 [rsHealthPoll] replSet member bs-linux32.10gen.cc:31000 is now in state SECONDARY
      
      ...
      ReplSetTest getMaster failed: "[Finding master] timed out after 60000ms ( 31 tries )"
      Error: Printing Stack Trace
          at printStackTrace (src/mongo/shell/utils.js:37:15)
          at ReplSetTest.getMaster (src/mongo/shell/replsettest.js:412:5)
          at reconfig (jstests/replsets/rslib.js:111:17)
          at doTest (/mnt/slaves/Linux_32bit_V2.4/mongo/jstests/replsets/slavedelay1.js:117:3)
          at /mnt/slaves/Linux_32bit_V2.4/mongo/jstests/replsets/slavedelay1.js:143:1
      Tue Oct 22 06:43:28.192 [Finding master] timed out after 60000ms ( 31 tries ) at src/mongo/shell/replsettest.js:413
      failed to load: /mnt/slaves/Linux_32bit_V2.4/mongo/jstests/replsets/slavedelay1.js
      

      What happened here? That Assertion failure repeats many times.

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            matt.kangas Matt Kangas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: