Closed Bug 646305 Opened 14 years ago Closed 14 years ago

new linux64-ix-slaveXX machines unable to post to graphs-stage

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhford, Unassigned)

References

Details

I don't know why, but the new linux64 ix machines aren't able to post to graphs-stage. I am getting the response "No machine_name called 'Linux_x86-64_tryserver' can be found" back. I got catlee to run "select * from machine where name like "Linux_x86-64%" and it showed that it is in the machines table. I dont know if this is something that blocks the rollout of the linux64-ix machines, but all other branches are posting properly. Worst case, I can put all of these slaves into the production pool instead of the try pool until this is sorted out OUTPUT BELOW ============================================================================= Calling <function run_with_timeout at 0x2aaaaed199b0> with args: (['python', '/builds/slave/try-lnx64/tools/buildfarm/utils/graph_server_post.py', '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', '--branch', 'MozillaTest', '--buildid', '20110329173900', '--sourcestamp', '6bc9bfd8324b', '--resultsname', 'Linux_x86-64_tryserver', '--properties-file', 'properties.json', '--timestamp', '1301445508'], 120, None, None, False, True), kwargs: {}, attempt #2 Executing: ['python', '/builds/slave/try-lnx64/tools/buildfarm/utils/graph_server_post.py', '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', '--branch', 'MozillaTest', '--buildid', '20110329173900', '--sourcestamp', '6bc9bfd8324b', '--resultsname', 'Linux_x86-64_tryserver', '--properties-file', 'properties.json', '--timestamp', '1301445508'] Process stdio: Process stderr: results not added, response: No machine_name called 'Linux_x86-64_tryserver' can be found File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 264, in handleRequest metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream) File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 59, in __init__ self.doDatabaseThings(databaseCursor) File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 88, in doDatabaseThings raise DatabaseException("No machine_name called '%s' can be found" % self.machine_name)
(In reply to comment #0) > I don't know why, but the new linux64 ix machines aren't able to post to > graphs-stage. I am getting the response > "No machine_name called 'Linux_x86-64_tryserver' can be found" > back. I got catlee to run "select * from machine where name like > "Linux_x86-64%" and it showed that it is in the machines table. > > I dont know if this is something that blocks the rollout of the linux64-ix > machines, but all other branches are posting properly. Worst case, I can put > all of these slaves into the production pool instead of the try pool until this > is sorted out > > OUTPUT BELOW > ============================================================================= > > Calling <function run_with_timeout at 0x2aaaaed199b0> with args: (['python', > '/builds/slave/try-lnx64/tools/buildfarm/utils/graph_server_post.py', > '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', > '--branch', 'MozillaTest', '--buildid', '20110329173900', '--sourcestamp', > '6bc9bfd8324b', '--resultsname', 'Linux_x86-64_tryserver', '--properties-file', > 'properties.json', '--timestamp', '1301445508'], 120, None, None, False, True), > kwargs: {}, attempt #2 > Executing: ['python', > '/builds/slave/try-lnx64/tools/buildfarm/utils/graph_server_post.py', > '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', > '--branch', 'MozillaTest', '--buildid', '20110329173900', '--sourcestamp', > '6bc9bfd8324b', '--resultsname', 'Linux_x86-64_tryserver', '--properties-file', > 'properties.json', '--timestamp', '1301445508'] > Process stdio: > > Process stderr: > results not added, response: > No machine_name called 'Linux_x86-64_tryserver' can be found > File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 264, in > handleRequest > metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream) > File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 59, in > __init__ > self.doDatabaseThings(databaseCursor) > File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 88, in > doDatabaseThings > raise DatabaseException("No machine_name called '%s' can be found" % > self.machine_name) mea culpa, I think I was looking at the wrong db on graphs-stage. I've added 'Linux_x86-64_tryserver' and 'Linux_x86-64_tryserver_leak_test' to the other (correct?) one. Hopefully that will clear it up. FTR, I was looking at the graphs_stage2_prod DB before, and have just added them to the graphs_stage2 DB.
Awesome! Thanks catlee! :D Calling <function run_with_timeout at 0x2aaaaed199b0> with args: (['python', '/builds/slave/try-lnx64-dbg/tools/buildfarm/utils/graph_server_post.py', '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', '--branch', 'MozillaTest', '--buildid', '20110329183857', '--sourcestamp', 'c686b62bac05', '--resultsname', 'Linux_x86-64_tryserver_leak_test', '--properties-file', 'properties.json', '--timestamp', '1301449115'], 120, None, None, False, True), kwargs: {}, attempt #1 Executing: ['python', '/builds/slave/try-lnx64-dbg/tools/buildfarm/utils/graph_server_post.py', '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', '--branch', 'MozillaTest', '--buildid', '20110329183857', '--sourcestamp', 'c686b62bac05', '--resultsname', 'Linux_x86-64_tryserver_leak_test', '--properties-file', 'properties.json', '--timestamp', '1301449115'] Process stdio: TinderboxPrint: <a title="num_ctors" href='http://graphs-stage.mozilla.org/graph.html#tests=[{"test":80,"branch":6,"machine":1022}]'>num_ctors:358</a> Process stderr: program finished with exit code 0
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.