[SERVER-10207] auth_slaveok_routing.js failure on V2.4 Linux 64-bit SSL Amazon AMI Created: 15/Jul/13  Updated: 10/Dec/14  Resolved: 19/Aug/13

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

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

buildbot V2.4 Linux 64-bit SSL Amazon AMI Build #109


Attachments: File auth_slaveok_routing.log    
Issue Links:
Duplicate
is duplicated by SERVER-10453 Make DBClientReplicaSet::connect alwa... Closed
Operating System: ALL
Participants:

 Description   

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



 Comments   
Comment by Matt Kangas [ 04/Aug/13 ]

Another example:

V2.4 Linux 64-bit SSL Amazon AMI Build #128 Aug 3

http://buildbot-special.10gen.com/builders/V2.4%20Linux%2064-bit%20SSL%20Amazon%20AMI/builds/128/steps/test_3/logs/stdio
http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20SSL%20Amazon%20AMI/builds/128/test/sharding/auth_slaveok_routing.js

Comment by Matt Kangas [ 25/Jul/13 ]

Prior examples of this failure:

V2.4 Linux 64-bit SSL Amazon AMI Build #109 on July 14
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: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

V2.4 Linux 64-bit SSL Amazon AMI Build #68 on May 29
http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20SSL%20Amazon%20AMI/builds/68/test/sharding/auth_slaveok_routing.js

Wed May 29 20:06:29.160 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

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