Closed
Bug 781241
Opened 12 years ago
Closed 11 years ago
node4.testing.stage.metrics.scl3 Power supply failure
Categories
(Infrastructure & Operations :: DCOps, task)
Infrastructure & Operations
DCOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ericz, Assigned: vinh)
Details
node4.testing.stage.metrics.scl3.mozilla.com:IPMI Log is CRITICAL: CRITICAL - 1 -- 08/07/2012 -- 19:10:55 -- Power Supply #0x17 -- Failure -- Asserted
Reporter | ||
Comment 1•12 years ago
|
||
Transferring to DC Ops for the RMA process.
Assignee: eziegenhorn → server-ops
Component: Server Operations → Server Operations: DCOps
QA Contact: jdow → dmoore
Updated•12 years ago
|
colo-trip: --- → scl3
Assignee | ||
Updated•12 years ago
|
Assignee: server-ops → vhua
Assignee | ||
Comment 2•12 years ago
|
||
From visually inspecting both power supplies on node4.testing.stage.metrics host, nothing looks out of the ordinary. I've unplugged and replugged both power supplies and they both powered up fine. Will have to investigate further.
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•12 years ago
|
||
I've cleared the power supply logs. Will check back in a few days to see if issue still arise.
Assignee | ||
Comment 4•12 years ago
|
||
No power supply error message alerted today. Closing ticket.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•11 years ago
|
||
I'm reopening this as I'm getting the exact same alert: [eziegenhorn@node4.research.stage.metrics.scl3 ~]$ sudo ipmitool sel list 1 | 02/21/2013 | 17:38:45 | Power Supply #0x17 | Failure detected | Asserted
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•11 years ago
|
||
Reseated the power supply. sudo ipmitool sdr type 'Power Supply' PS Status | 17h | ok | 10.1 | 0 unspecified [vhua@node4.testing.stage.metrics.scl3 ~]$ sudo ipmitool sel list SEL has no entries
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•