stepdown.js failing on buildbot-special V2.4 Linux 64-bit Subscription SUSE 11

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.2
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • Environment:
      buildbot-special: V2.4 Linux 64-bit Subscription SUSE 11 build #144
      buildbot-special Nightly Linux 64-bit Subscription SUSE 11 Build #465
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      http://buildbot-special.10gen.com/builders/V2.4%20Linux%2064-bit%20Subscription%20SUSE%2011/builds/144
      http://buildbot-special.10gen.com/builders/V2.4%20Linux%2064-bit%20Subscription%20SUSE%2011/builds/144/steps/shell_2/logs/stdio
      http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20Subscription%20SUSE%2011/builds/144/test/replica%20sets/stepdown.js

      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 /data/buildslaves/Linux_64bit_Subscription_SUSE_11_V2.4/mongo/jstests/replsets/stepdown.js:101:10
      Sun Jul  7 08:14:46.064 JavaScript execution failed: [Finding master] timed out after 60000ms ( 31 tries ) at src/mongo/shell/replsettest.js:L413
      failed to load: /data/buildslaves/Linux_64bit_Subscription_SUSE_11_V2.4/mongo/jstests/replsets/stepdown.js
      

      Preceding this are repeated authentication failures. Possibly the cause?

      Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
      ...
      Caught exception while authenticating connection: "[Authenticating connection: connection to ip-10-86-167-136:31001] timed out after 5000ms ( 6 tries )"
      

            Assignee:
            Randolph Tan
            Reporter:
            Matt Kangas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: