From: Bryan Daniel (danielb@ucfv.bc.ca)
Date: Tue Apr 15 2003 - 16:17:02 EDT
Thanks to all who answered. The consensus is that there is not likely
any way to tell now why the crash occurred. There is a good possibility
it was hardware related. Apparently many people have seen similar
circumstances. At this point we will just watch the system for any sign
of trouble.
For future reference, always use the halt button rather than doing a
hard reset (I should have known this). Then enter the crash command at
the SRM console to force a crash.
Thanks to Jeffrey Hummel, Thomas Blinn, Peyton Bland, Steve Lowe,
Roberto Romani, Mike Broderick, Jeff Beck and Pat O'Brien.
Bryan Daniel
Systems Administrator
University College of the Fraser Valley
Abbotsford, BC Canada
------------
Original Message:
Late yesterday our Alphaserver DS20 running Tru64 V4.0F apparently
crashed or stopped responding. I could not ping the server remotely and
according to the person I had on the telephone, there was no response at
the console. The most recent console messages from a few days ago was
visible, but apparently the keyboard was unresponsive.
We eventually ended up doing a reset after which the system rebooted,
checked the disks and restarted databases etc with no apparent problem.
I can find no evidence in the messages log that there was a problem
prior to the reboot and there are no crash dumps to be found. Has anyone
seen this type of situation before? Is it possible that the cpu panicked
without leaving any messages or was perhaps pinned at 100% and could not
respond or even create log entries?
Bryan Daniel
Systems Administrator
University College of the Fraser Valley
Abbotsford, BC Canada
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:16 EDT