Closed Bug 493928 Opened 16 years ago Closed 16 years ago

bm-xserve11 is not responsive

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: phong)

References

Details

nagios reported bm-xserve11 dropped from the Firefox3.0 waterfall (where it's doing Mac debug builds), and I can't reach it via ssh. Please investigate if it's churning the CPUs or is hung. It could be a glitch, or the disk is corrupted again.
Assignee: server-ops → phong
Flags: colo-trip+
It was not responsive. I had to powercycle the server. It's up and running again.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
I restarted tinderbox after clobbering the build dir and it's non-responsive again. This looks a lot like bug 438811, and several other xserve bugs, which were traced to corrupted OS install and fixed by applying a disk image. Please go ahead and do that using the gold 10.4 image for Intel, then pass it back to RelEng for tinderbox setup.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 494325
On second thought, we're going to use this machine for a different job. Please apply the 10.5 image for x-serves (same as bug 474544, if that helps). We'll handle our setup in bug 493928 so you can resolve here when you're done.
Oops, meant that we'll do our setup in bug 494325.
I just want to confirm that you want me to re-image this server. Should I use the image that I just took macOSX-10.5.2-xserve-ref-image I just took yesterday?
Yes, use the image from yesterday please.
re-imaged with macOSX-10.5.2-xserve-ref-image.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 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.