[SERVER-10145] gle_with_conf_servers.js failing during sharding_auth suite on Linux 64 Created: 09/Jul/13  Updated: 11/Jul/16  Resolved: 12/Jul/13

Status: Closed
Project: Core Server
Component/s: Security, Sharding
Affects Version/s: None
Fix Version/s: 2.5.1

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

http://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_3e47b95f0de530d579f51fc0d4b588b45f8eda73_13_07_08_20_48_04_sharding_auth_linux_64

http://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_291f7c324d7361a84951bab734e3959f83ef2ba3_13_07_08_20_12_08_sharding_auth_linux_64

 m30999| Tue Jul  9 08:58:44.236 [Balancer] about to contact config servers and shards
 m30999| Tue Jul  9 08:58:44.237 [mongosMain] waiting for connections on port 30999
 m30999| Tue Jul  9 08:58:44.237 [Balancer] config servers and shards contacted successfully
 m30999| Tue Jul  9 08:58:44.237 [Balancer] balancer id: ip-10-149-29-3:30999 started at Jul  9 08:58:44
 m29000| Tue Jul  9 08:58:44.237 [conn8] build index config.mongos { _id: 1 }
 m29001| Tue Jul  9 08:58:44.237 [conn8] build index config.mongos { _id: 1 }
 m29001| Tue Jul  9 08:58:44.238 [conn8] build index done.  scanned 0 total records. 0 secs
 m29000| Tue Jul  9 08:58:44.238 [conn8] build index done.  scanned 0 total records. 0 secs
 m29002| Tue Jul  9 08:58:44.237 [conn8] build index config.mongos { _id: 1 }
 m29002| Tue Jul  9 08:58:44.238 [conn8] build index done.  scanned 0 total records. 0 secs
 m30999| Tue Jul  9 08:58:44.358 [mongosMain] connection accepted from 127.0.0.1:42742 #1 (1 connection now open)
 m30999| Tue Jul  9 08:58:44.359 [conn1] couldn't find database [admin] in config db
Authenticating to admin database as admin with mechanism MONGODB-CR on connection: connection to ip-10-149-29-3:30999
 m29001| Tue Jul  9 08:58:44.409 [conn7] build index config.databases { _id: 1 }
 m29000| Tue Jul  9 08:58:44.409 [conn7] build index config.databases { _id: 1 }
 m29000| Tue Jul  9 08:58:44.410 [conn7] build index done.  scanned 0 total records. 0 secs
 m29001| Tue Jul  9 08:58:44.410 [conn7] build index done.  scanned 0 total records. 0 secs
 m29002| Tue Jul  9 08:58:44.411 [conn7] build index config.databases { _id: 1 }
 m29002| Tue Jul  9 08:58:44.411 [conn7] build index done.  scanned 0 total records. 0 secs
 m30999| Tue Jul  9 08:58:44.480 [conn1] 	 put [admin] on: config:ip-10-149-29-3:29000,ip-10-149-29-3:29001,ip-10-149-29-3:29002
 m30999| Tue Jul  9 08:58:44.480 [conn1] note: no users configured in admin.system.users, allowing localhost access
 m30999| Tue Jul  9 08:58:44.481 [conn1]  authenticate db: admin { authenticate: 1, nonce: "fc572bf80341be98", user: "admin", key: "86d7e04d063c85e59517ef77ba52bb72" }
 m30999| Tue Jul  9 08:58:44.482 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
 m30999| Tue Jul  9 08:58:44.654 [Balancer] distributed lock 'balancer/ip-10-149-29-3:30999:1373360322:1804289383' acquired, ts : 51dbd0c4b81fcd8b304739e2
 m30999| Tue Jul  9 08:58:44.791 [Balancer] distributed lock 'balancer/ip-10-149-29-3:30999:1373360322:1804289383' unlocked. 
Authenticating to admin database as admin with mechanism MONGODB-CR on connection: connection to ip-10-149-29-3:30999
 m30999| Tue Jul  9 08:58:45.483 [conn1]  authenticate db: admin { authenticate: 1, nonce: "1da7a2c10027b5cf", user: "admin", key: "c1d92d83186778f601bd769c6ee028ba" }
 m30999| Tue Jul  9 08:58:45.483 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
------------SNIP-----------------
 m29001| Tue Jul  9 09:02:40.875 [conn1]  authenticate db: admin { authenticate: 1, nonce: "dfd96e1ec833b3d4", user: "admin", key: "31b782db942521db7cb9db077943c5b1" }
 m29001| Tue Jul  9 09:02:40.875 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
Authenticating to admin database as admin with mechanism MONGODB-CR on connection: connection to ip-10-149-29-3:29001
 m29001| Tue Jul  9 09:02:41.876 [conn1]  authenticate db: admin { authenticate: 1, nonce: "14dee8a63c69a415", user: "admin", key: "17d9d790ac1a342fe6860f1498b88f15" }
 m29001| Tue Jul  9 09:02:41.876 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
Authenticating to admin database as admin with mechanism MONGODB-CR on connection: connection to ip-10-149-29-3:29001
 m29001| Tue Jul  9 09:02:42.877 [conn1]  authenticate db: admin { authenticate: 1, nonce: "6009887802722262", user: "admin", key: "857ea393c6c51618d55d74e99a705c1c" }
 m29001| Tue Jul  9 09:02:42.877 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
 m30999| Tue Jul  9 09:02:42.921 [Balancer] distributed lock 'balancer/ip-10-149-29-3:30999:1373360322:1804289383' acquired, ts : 51dbd1b2b81fcd8b30473a08
 m30999| Tue Jul  9 09:02:43.093 [Balancer] distributed lock 'balancer/ip-10-149-29-3:30999:1373360322:1804289383' unlocked. 
Authenticating to admin database as admin with mechanism MONGODB-CR on connection: connection to ip-10-149-29-3:29001
 m29001| Tue Jul  9 09:02:43.878 [conn1]  authenticate db: admin { authenticate: 1, nonce: "45f48be53954dcb2", user: "admin", key: "c68e9e4fa6570a713fa9d917831f786e" }
 m29001| Tue Jul  9 09:02:43.878 [conn1] auth: couldn't find user admin@admin, admin.system.users
Error: 18 { code: 18, ok: 0.0, errmsg: "auth fails" }
Caught exception while authenticating connection: "[Authenticating connection: connection to ip-10-149-29-3:29001] timed out after 5000ms ( 6 tries )"
2013-07-09 05:02:46 EDT	
Tue Jul  9 09:02:46.892 [Authenticate to nodes: connection to ip-10-149-29-3:29000,connection to ip-10-149-29-3:29001,connection to ip-10-149-29-3:29002] timed out after 30000ms ( 16 tries ) at src/mongo/shell/utils.js:492
failed to load: /home/ec2-user/mci/prep/git@github.commongodb/mongo.git/master/sharding_auth/jstests/sharding/gle_with_conf_servers.js

http://buildlogs.mongodb.org/mci_0.9_linux_64/builds/108/test/sharding_auth/gle_with_conf_servers.js

This appears to have started with 291f7c324d7361a84951bab734e3959f83ef2ba3



 Comments   
Comment by auto [ 11/Jul/13 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-10145 In auth passthrough suite add user to mongos instead of directly to config servers
Branch: master
https://github.com/mongodb/mongo/commit/1d73fc675b2f437c05e48e136e7871bde128a26a

Comment by Matt Kangas [ 09/Jul/13 ]

Also on Nightly Linux 64-bit Subscription SUSE 11 Build #448

http://buildbot-special.10gen.com/builders/Nightly%20Linux%2064-bit%20Subscription%20SUSE%2011/builds/448/steps/shell_3/logs/stdio
http://buildlogs.mongodb.org/Nightly%20Linux%2064-bit%20Subscription%20SUSE%2011/builds/448/test/sharding/gle_with_conf_servers.js

Error: 18 Authentication failed.
(repeat)
Caught exception while authenticating connection: "[Authenticating connection: connection to ip-10-86-167-136:29001] timed out after 5000ms ( 6 tries )"
2013-07-09 11:39:18 EDT	
Tue Jul  9 15:39:18.656 [Authenticate to nodes: connection to ip-10-86-167-136:29000,connection to ip-10-86-167-136:29001,connection to ip-10-86-167-136:29002] timed out after 30000ms ( 16 tries ) at src/mongo/shell/utils.js:492
failed to load: /data/buildslaves/Linux_64bit_Subscription_SUSE_11_Nightly/mongo/jstests/sharding/gle_with_conf_servers.js

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