Closed Bug 689038 Opened 14 years ago Closed 14 years ago

reboot requests (sjc1)

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

nagios is consistently detecting the following errors on bm-xserve17: Subject: ** PROBLEM alert - bm-xserve17.build.sjc1/buildbot is CRITICAL ** Subject: ** PROBLEM alert - bm-xserve17.build.sjc1/disk - / is CRITICAL **
This should be on a reboots bug. Since the last (bug 686411) is already closed, I'll just re-purpose this one. bm-xserve17
Alias: reboots-sjc1
colo-trip: --- → sjc1
Summary: bm-xserve17 needs help → reboot requests (sjc1)
moz2-darwin9-slave41.build.sjc1
try-mac-slave02 try-mac-slave34 moz2-darwin9-slave12 moz2-darwin9-slave13 moz2-darwin9-slave52
try-linux-slave04
talos-r3-fed-036 talos-r3-fed64-033
ignore talos-r3-fed-036 talos-r3-fed64-033, put them in the wrong bug.
tb2-darwin10-slave71
Assignee: server-ops-releng → jdow
I rebooted: bm-xserve17 moz2-darwin9-slave41.build.sjc1 try-mac-slave02 try-mac-slave34 moz2-darwin9-slave12 moz2-darwin9-slave13 moz2-darwin9-slave52 and while there, I noticed that moz2-darwin9-slave03 is dead, just fyi. I also rebooted try-mac-slave33, which was off. This was on accident as it was next to 34 and I was going by the lights. Hope that is cool.
Assignee: jdow → server-ops-releng
moz2-darwin9-slave03 is set to be decommissioned in bug 688548. try-linux-slave04 is a VM, so I'll handle that. tb2-darwin10-slave71 got it's ram replaced, which counts as a reboot too :)
try-linux-slave04 rebooted via vmware console.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Alias: reboots-sjc1
See Also: → 690770
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.