Closed Bug 720105 Opened 14 years ago Closed 14 years ago

FWSM on core1 crashed

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ravi, Assigned: ravi)

Details

At 01:37:39 PDT the FWSM module on core1 crashed. At 01:38 PDT nagios alerted the first failure. At 01:43 After noticing many unrelated alerts on-call pinged #netops. At 01:45 I noticed the question on the channel. At 01:58 I identified the FWSM module in core1 had failed and initiated a module reset. At 02:01 The recoveries started.
Isn't this where the other one would have taken over and prevent a service impact?
It did. Something must have been wedged, and without logging combined with the time of day and the already long duration of the outage doing a more in depth investigation was difficult. Things have been stable for just under 12 hours so closing out.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.