Closed Bug 686394 Opened 13 years ago Closed 13 years ago

bm-xserve04, bm-xserve21 not responding to ping

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

Details

nagios has been complaining for a few days now that these two machines are not responding to ping. I've deleted most of these, but here's a recent alert as an example. ***** Nagios ***** Notification Type: PROBLEM Service: PING Host: bm-xserve04.build.sjc1 Address: 10.2.71.35 State: CRITICAL Date/Time: 09-11-2011 18:01:12 Additional Info: CRITICAL - Host Unreachable (10.2.71.35) Maybe just a reboot? Maybe something more serious?
bm-xserve21 is bug 652966. bm-xserve04 is, to my memory, new. It should go on the reboots-sjc1 bug, and be acked as such. I took care of both. Guides for all of this is on the buildduty page. I don't know if that's been updated to keep status in slavealloc instead of the slave-tracking spreadsheet since that change was made.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.