Closed
Bug 751684
(tegra-023)
Opened 12 years ago
Closed 11 years ago
[staging] tegra-023 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslave][capacity])
[57] tegra-023.build.mtv1:tegra agent check is CRITICAL: Connection refused
Comment 1•12 years ago
|
||
Has only been down since the 1'st: 2012-05-01 13:40:18 tegra-023 s INACTIVE active OFFLINE :: SUTAgent not present; Immediately gives connection refused, possibly an unexpected IP? (Either way, I PDU Cycled and will check back shortly) foopy05:sut_tools cltbld$ telnet tegra-023 20701 Trying 10.250.49.10... telnet: connect to address 10.250.49.10: Connection refused telnet: Unable to connect to remote host
Summary: tegra-023 problem tracking → [staging] tegra-023 problem tracking
Whiteboard: [buildduty][buildslave][capacity]
Comment 2•12 years ago
|
||
nvram has been re-flashed and sdcard reinitialized
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
Sending this slave to recovery -->Automated reopening of bug
Comment 4•11 years ago
|
||
reflashed and reimaged.
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 5•11 years ago
|
||
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•