Closed
Bug 606111
Opened 14 years ago
Closed 14 years ago
talos-r3-leopard-005 failing to reach graph server
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: philor, Unassigned)
Details
(Whiteboard: [buildduty][badslave?])
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287632825.1287635231.17987.gz then http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287638023.1287640541.10968.gz Nobody else seems to be having any trouble.
|
||
Comment 1•14 years ago
|
||
buildbot.tac renamed to get this out of production.
Whiteboard: [buildduty][badslave?]
|
||
Comment 2•14 years ago
|
||
Are the graphserver posts done over port 80? I am able to reach graphs.mozilla.org on port 80. I get the same 301 on leopard-006 talos-r3-leopard-005:~ cltbld$ nc graphs.mozilla.org 80 GET / <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://graphs.mozilla.org/">here</a>.</p> <hr> <address>Apache/2.2.3 (Red Hat) Server at graphs-new.mozilla.org Port 80</address> </body></html>
|
|
||
Comment 3•14 years ago
|
||
I just checked and loading up graphs.mozilla.org/server/collect.cgi shows an exception that looks to be generated by graphserver. I am going to put machine back into production.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•