Closed Bug 695690 Opened 13 years ago Closed 13 years ago

DNR bm-xserve06 and bm-xserve02

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Assigned: mlarrain)

Details

bm-xserve06 just came back from a reboot in bug 690770, but it is still inaccessible. A few other xserves have recently reached the end of their natural lives, so if someone from IT could be hands-on and see whether this box is salvageable, it would be appreciated.
Assignee: server-ops-releng → mlarrain
Severity: normal → minor
colo-trip: --- → sjc1
This boots, but it's very, very sick - beachballs just opening dmesg, and lots of errors in dmesg. DNR, with orders to keep it on ice for extra body parts. We'll bring it to mtv1 today. Inventory is not updated.
Summary: Investigate bm-xserve06 → DNR bm-xserve06
colo-trip: sjc1 → ---
bm-xserve02 was also complaining that it was down. It would not even power on, so this one will be DNRed as well.
Summary: DNR bm-xserve06 → DNR bm-xserve06 and bm-xserve02
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.