-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.6
-
Component/s: Testing Infrastructure
-
Environment:buildbot V2.4 Linux 64-bit SSL Amazon AMI Build #109
-
ALL
Test flakiness, environment flakiness, or something else?
V2.4 Linux 64-bit SSL Amazon AMI Build #109 July 14 (rev 22df6cbb2b)
http://buildbot-special.10gen.com/builders/V2.4%20Linux%2064-bit%20SSL%20Amazon%20AMI/builds/109/steps/test_3/logs/stdio
http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20SSL%20Amazon%20AMI/builds/109/test/sharding/auth_slaveok_routing.js
Sun Jul 14 19:55:03.685 [ReplicaSetMonitorWatcher] trying reconnect to bs-e-amzn64-2.10gen.cc:31102 m31102| Sun Jul 14 19:55:03.686 [initandlisten] connection accepted from 127.0.0.1:55439 #7 (5 connections now open) Sun Jul 14 19:55:03.686 [ReplicaSetMonitorWatcher] reconnect bs-e-amzn64-2.10gen.cc:31102 ok Sun Jul 14 19:55:03.686 [ReplicaSetMonitorWatcher] DBClientCursor::init call() failed Sun Jul 14 19:55:03.686 [ReplicaSetMonitorWatcher] Detected bad connection created at 1373831659670590 microSec, clearing pool for bs-e-amzn64-2.10gen.cc:31102 m31102| Sun Jul 14 19:55:03.811 [conn3] end connection 127.0.0.1:55424 (4 connections now open) m31102| Sun Jul 14 19:55:03.811 [initandlisten] connection accepted from 127.0.0.1:55440 #8 (5 connections now open) m31102| Sun Jul 14 19:55:03.812 [conn8] authenticate db: local { authenticate: 1, nonce: "e4f6ba288ca07a70", user: "__system", key: "4785e98bd4b5ceecfcd90fa9763921be" } m30999| Sun Jul 14 19:55:04.128 [ReplicaSetMonitorWatcher] trying reconnect to bs-e-amzn64-2.10gen.cc:31102 m31102| Sun Jul 14 19:55:04.129 [initandlisten] connection accepted from 127.0.0.1:55441 #9 (6 connections now open) m30999| Sun Jul 14 19:55:04.129 [ReplicaSetMonitorWatcher] reconnect bs-e-amzn64-2.10gen.cc:31102 ok m30999| Sun Jul 14 19:55:04.129 [ReplicaSetMonitorWatcher] DBClientCursor::init call() failed m30999| Sun Jul 14 19:55:04.129 [ReplicaSetMonitorWatcher] Detected bad connection created at 1373831660117962 microSec, clearing pool for bs-e-amzn64-2.10gen.cc:31102 Awaiting bs-e-amzn64-2.10gen.cc:31100 to be { "ok" : true, "ismaster" : true } for connection to bs-e-amzn64-2.10gen.cc:30999 (rs: undefined) { "test-rs0" : { "hosts" : [ { "addr" : "bs-e-amzn64-2.10gen.cc:31100", "ok" : true, "ismaster" : true, "hidden" : false, "secondary" : false, "pingTimeMillis" : 1 }, { "addr" : "bs-e-amzn64-2.10gen.cc:31101", "ok" : true, "ismaster" : false, "hidden" : false, "secondary" : true, "pingTimeMillis" : 1 }, { "addr" : "bs-e-amzn64-2.10gen.cc:31102", "ok" : false, "ismaster" : false, "hidden" : false, "secondary" : true, "pingTimeMillis" : 0 } ], "master" : 0, "nextSlave" : 0 } } ---- Final query to SEC ---- Sun Jul 14 19:55:04.132 JavaScript execution failed: error: { "$err" : "socket exception [CONNECT_ERROR] for test-rs0/bs-e-amzn64-2.10gen.cc:31100,bs-e-amzn64-2.10gen.cc:31101,bs-e-amzn64-2.10gen.cc:31102", "code" : 11002, "shard" : "test-rs0" } at src/mongo/shell/query.js:L128 failed to load: /data/buildslaves/Linux_64bit_SSL_Amazon_AMI_V2.4/mongo/jstests/sharding/auth_slaveok_routing.js
- is duplicated by
-
SERVER-10453 Make DBClientReplicaSet::connect always return true
- Closed