Closed Bug 465825 Opened 16 years ago Closed 16 years ago

bm-xserve08 not responsive

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

nagios reported a timeout for its checks on RAID, avg load, and root disk usage at 2pm PST, while PING is still ok. Also can't get a logon by ssh (establishes a connection but goes no further) or VNC (no response) so probably needs on-site investigation.

This box is Tier 1, doing Firefox 3.0.x nightlies for mac. That tree is semi-frozen at the moment but further checkins may need testing before 3.0.5 starts up.
Assignee: server-ops → phong
bm-xserve08 is up and running.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Did you have to force a reboot ? Any info on what happened ?
I had to do a hard reboot.  I couldn't logon with the password I knew so I didn't check anything.
Ok, I can't find anything in the system logs, and the RAID setup passes a disk verify. Thanks for the reboot.
Stopped responding again just after I started tinderbox back up. This is looking similar to bm-xserve11 (bug 438811) and bm-xserve02 (bug 462693).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Phong put a bunch of time into this box today (much appreciated!) coming to the conclusion that the disks are becoming corrupted without tripping up the built in utilites and RAID health monitors. We decided to just restore a clone of bm-xserve10 from Feb '08 as the shortest path. Now we're back in action I'll take this bug to setup tinderbox.
Assignee: phong → nthomas
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
Priority: -- → P2
QA Contact: mrz → release
Back in action.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Component: Release Engineering: Maintenance → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.