bm-xserve08 not responsive

RESOLVED FIXED

Status

P2
critical
RESOLVED FIXED
10 years ago
5 years ago

People

(Reporter: nthomas, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

10 years ago
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.

Updated

10 years ago
Assignee: server-ops → phong

Comment 1

10 years ago
bm-xserve08 is up and running.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

10 years ago
Did you have to force a reboot ? Any info on what happened ?

Comment 3

10 years ago
I had to do a hard reboot.  I couldn't logon with the password I knew so I didn't check anything.
(Assignee)

Comment 4

10 years ago
Ok, I can't find anything in the system logs, and the RAID setup passes a disk verify. Thanks for the reboot.
(Assignee)

Comment 5

10 years ago
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 → ---
(Assignee)

Comment 6

10 years ago
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
(Assignee)

Comment 7

10 years ago
Back in action.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → FIXED

Updated

10 years ago
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.