- To: outages-list@eskimo.com
- Subject: Seattle1 reboot
- From: Robert Dinse <nanook@eskimo.com>
- Date: Fri, 5 Mar 1999 22:44:48 -0800 (PST)
- Resent-Date: Fri, 5 Mar 1999 22:44:53 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"B4opP.0.am3.axCus"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: WWW/FTP downtime this morning
- Next by Date: Smurf Attack
- Prev by thread: Smurf Attack
- Next by thread: WWW/FTP downtime this morning
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Seattle1 reboot
Seattle1 locked up and had to be rebooted about 22:15 (10:15pm)
tonight. I suspect this is related to the memory shortage but since it locked
solid I was unable to determine the exact cause.
This would have caused peoples connections to freeze (when it locked up)
and then carrier to be lost when it was rebooted, followed by several minutes
of ring-no-answer while it was booting before it finally came back online.
I do have memory now add to all of the communications servers but wanted
to do so during the time the lines are cut from the 1AESS switch to 5ESS so
we can get by with one outage for that rather than two.
Tentatively I have requested this happen on 3/19, or actually 3/20, just
after midnight but this is not yet finalized.