-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
ALL
******************************************* Test : server8070.js ... Command : /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/mongo --port 27999 --authenticationMechanism CRAM-MD5 --nodb /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js --eval TestData = new Object();TestData.testPath = "/data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js";TestData.testFile = "server8070.js";TestData.testName = "server8070";TestData.noJournal = false;TestData.noJournalPrealloc = false;TestData.auth = true;TestData.keyFile = "/data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/libs/authTestsKey";TestData.keyFileData = "Thiskeyisonlyforrunningthesuitewithauthenticationdontuseitinanytestsdirectly";TestData.authMechanism = "CRAM-MD5"; Date : Sat Jul 6 01:07:55 2013 (output suppressed; see http://buildlogs.mongodb.org/build/51d73e27d2a60f574d0000bb/test/51d76debd2a60f1562000853/) 3.2656 minutes test /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js exited with status 253
m31002| Sat Jul 6 01:08:18.866 [initandlisten] connection accepted from 127.0.0.1:36879 #1 (1 connection now open) [ connection to bs-e-amzn64:31000, connection to bs-e-amzn64:31001, connection to bs-e-amzn64:31002 ] Authenticating to admin database as admin with mechanism CRAM-MD5 on connection: connection to bs-e-amzn64:31000 m31000| Sat Jul 6 01:08:18.869 [conn1] note: no users configured in admin.system.users, allowing localhost access m31000| Sat Jul 6 01:08:18.870 [conn1] CRAM-MD5 authentication failed for admin on admin ; ProtocolError SASL(-1): generic failure: empty secret Error: 18 Authentication failed. Caught exception while authenticating connection: "[Authenticating connection: connection to bs-e-amzn64:31000] timed out after 5000ms ( 6 tries )" (many more authentication failures) ... assert.soon failed: function () { var syncingTo = member3.adminCommand({replSetGetStatus:1}).syncingTo; return syncingTo == getHostName()+":"+replSet.ports[1]; }, msg:undefined Error: Printing Stack Trace at printStackTrace (src/mongo/shell/utils.js:37:15) at doassert (src/mongo/shell/assert.js:6:5) at Function.assert.soon (src/mongo/shell/assert.js:174:60) at /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js:106:20 at Function.assert.throws (src/mongo/shell/assert.js:202:14) at fixed (/data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js:104:12) at /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js:117:1 --- pause 3's bgsync thread --- Allow 3 to apply ops 25-75 ... m31001| Sat Jul 6 01:10:59.591 [rsHealthPoll] replset info bs-e-amzn64:31000 heartbeat failed, retrying m31001| Sat Jul 6 01:10:59.595 [rsHealthPoll] couldn't connect to bs-e-amzn64:31000: couldn't connect to server bs-e-amzn64:31000 m31001| Sat Jul 6 01:10:59.600 [rsMgr] replSet I don't see a primary and I can't elect myself ... assert.soon failed: function () { var last3 = member3.getSisterDB("local").oplog.rs.find().sort({$natural:-1}).limit(1) .next(); print("primary: " + tojson(last.ts) + " secondary: " + tojson(last3.ts)); return ((last.ts.t === last3.ts.t) && (last.ts.i === last3.ts.i)) }, msg:undefined Error: Printing Stack Trace at printStackTrace (src/mongo/shell/utils.js:37:15) at doassert (src/mongo/shell/assert.js:6:5) at Function.assert.soon (src/mongo/shell/assert.js:174:60) at /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js:124:8 Sat Jul 6 01:11:09.272 assert.soon failed: function () { var last3 = member3.getSisterDB("local").oplog.rs.find().sort({$natural:-1}).limit(1) .next(); print("primary: " + tojson(last.ts) + " secondary: " + tojson(last3.ts)); return ((last.ts.t === last3.ts.t) && (last.ts.i === last3.ts.i)) }, msg:undefined at src/mongo/shell/assert.js:7 failed to load: /data/buildslaves/Linux_64bit_Subscription_Amazon_AMI_Nightly/mongo/jstests/replsets/server8070.js
Is this an intermittent issue? Or did this break due to recent authentication changes?