[SERVER-14903] smoke.py probable bug: self.proc unset in stop Created: 14/Aug/14  Updated: 25/Apr/16  Resolved: 18/Aug/14

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

 [2014/08/14 15:38:04.066] Task logger initialized.
 [2014/08/14 15:38:04.066] Running Agent without an https cert
 [2014/08/14 15:38:04.123] Running command expansions.fetch (step 1 of 2)
 [2014/08/14 15:38:04.125] [expansions.fetch] Updating local key aws_key with remote key project_aws_key
 [2014/08/14 15:38:04.125] [expansions.fetch] Updating local key aws_secret with remote key project_aws_secret
 [2014/08/14 15:38:04.125] [expansions.fetch] Done updating expansions from remote.
 [2014/08/14 15:38:04.125] Running command shell.exec (step 2 of 2)
 [2014/08/14 15:38:04.142] rm -rf src || true
 [2014/08/14 15:38:04.351] pkill mongo; pkill -9 mongod; pkill -9 mongos; pkill -f buildlogger.py; pkill -f smoke.py
 [2014/08/14 15:38:04.366] rm -rf /data/db/*
 [2014/08/14 15:38:04.367] true
 [2014/08/14 15:38:04.368] Running command s3.get (step 1 of 4)
 [2014/08/14 15:38:04.368] [s3.get] Fetching mongodb-mongo-master/linux-64/10827279fbc6380d4d7774837022b65b3204a988/artifacts/mongodb_mongo_master_linux_64_10827279fbc6380d4d7774837022b65b3204a988_14_08_14_19_21_36.tgz from s3 bucket mciuploads
 [2014/08/14 15:38:19.472] Running command s3.get (step 2 of 4)
 [2014/08/14 15:38:19.473] [s3.get] Fetching mongodb-mongo-master/linux-64/10827279fbc6380d4d7774837022b65b3204a988/binaries/mongo-mongodb_mongo_master_linux_64_10827279fbc6380d4d7774837022b65b3204a988_14_08_14_19_21_36.tgz from s3 bucket mciuploads
 [2014/08/14 15:38:20.791] Running command shell.exec (step 3 of 4)
 [2014/08/14 15:38:20.817] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/README
 [2014/08/14 15:38:20.817] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/THIRD-PARTY-NOTICES
 [2014/08/14 15:38:20.825] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/GNU-AGPL-3.0
 [2014/08/14 15:38:20.825] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongodump
 [2014/08/14 15:38:21.073] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongorestore
 [2014/08/14 15:38:21.330] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongoexport
 [2014/08/14 15:38:21.586] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongoimport
 [2014/08/14 15:38:21.842] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongostat
 [2014/08/14 15:38:22.097] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongotop
 [2014/08/14 15:38:22.353] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongooplog
 [2014/08/14 15:38:22.608] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongofiles
 [2014/08/14 15:38:22.864] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/bsondump
 [2014/08/14 15:38:23.119] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongoperf
 [2014/08/14 15:38:23.371] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongod
 [2014/08/14 15:38:23.630] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongos
 [2014/08/14 15:38:23.825] mongodb-linux-x86_64-10827279fbc6380d4d7774837022b65b3204a988-2014-08-14/bin/mongo
 [2014/08/14 15:38:23.956] Running command shell.exec (step 4 of 4)
 [2014/08/14 15:38:24.654] [Errno 111] Connection refused
 [2014/08/14 15:38:24.654] probable bug: self.proc unset in stop()
 [2014/08/14 15:38:24.654] [Errno 111] Connection refused
 [2014/08/14 15:38:24.655] Creating dir: /tmp/unittest/
 [2014/08/14 15:38:24.655] 0 tests succeeded
 [2014/08/14 15:38:24.655] 6 tests didn't get run
 [2014/08/14 15:38:24.655] Traceback (most recent call last):
 [2014/08/14 15:38:24.655]   File "buildscripts/smoke.py", line 1342, in <module>
 [2014/08/14 15:38:24.655]     main()
 [2014/08/14 15:38:24.655]   File "buildscripts/smoke.py", line 1326, in main
 [2014/08/14 15:38:24.655]     run_tests(tests)
 [2014/08/14 15:38:24.655]   File "buildscripts/smoke.py", line 668, in run_tests
 [2014/08/14 15:38:24.655]     master.start()
 [2014/08/14 15:38:24.655]   File "buildscripts/smoke.py", line 207, in start
 [2014/08/14 15:38:24.655] self.ensure_test_dirs()
 [2014/08/14 15:38:24.655]   File "buildscripts/smoke.py", line 170, in ensure_test_dirs
 [2014/08/14 15:38:24.655] utils.ensureDir(smoke_db_prefix + "/tmp/unittest/")
 [2014/08/14 15:38:24.655]   File "/data/mci/shell/src/buildscripts/utils.py", line 125, in ensureDir
 [2014/08/14 15:38:24.655]     os.makedirs( d )
 [2014/08/14 15:38:24.655]   File "/usr/lib64/python2.6/os.py", line 157, in makedirs
 [2014/08/14 15:38:24.656]     mkdir(name, mode)
 [2014/08/14 15:38:24.656] OSError
 [2014/08/14 15:38:24.656] : [Errno 17] File exists: '/tmp/unittest'
 [2014/08/14 15:38:24.662] Command failed: exit status 1
 [2014/08/14 15:38:24.662] Task completed - FAILURE.
 [2014/08/14 15:38:24.662] Executing post-task commands...
 [2014/08/14 15:38:24.666] Running command attach.results (step 1 of 2)
 [2014/08/14 15:38:24.669] [attach.results] Attach test results succeeded
 [2014/08/14 15:38:24.669] Running command shell.exec (step 2 of 2)
 [2014/08/14 15:38:24.692] Command failed: exit status 1

https://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_10827279fbc6380d4d7774837022b65b3204a988_14_08_14_19_21_36_aggregation_linux_64



 Comments   
Comment by Randolph Tan [ 14/Aug/14 ]

Did a quick glance and it appears to be storing the proc (object?) for the mongod it started. There is a check right after it gets assigned if the mongod is running so either: proc was somehow unset or it was never set to something in the first place and it passed the check because some other mongod happens to be running.

Comment by Michael O'Brien [ 14/Aug/14 ]

It looks like that error message comes from smoke.py:
https://github.com/mongodb/mongo/blob/master/buildscripts/smoke.py#L309

any idea what it means?

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