From: Edward Brash (brash@uregina.ca)
Date: Wed Jan 08 2003 - 22:03:18 EST
Hi All,
We have an older AlphaServer running Tru64 Unix. For the last few months, it has been crashing every so often. When the crash happens,
absolutely nothing is written to any log file that is being kept. In the messages file, the only things that I get are the messages from the
reboot. Most of the time, it reboots on its own successfully (after having done a lengthy file system check). Based on the data of the last
few months, I was finally able to discern a pattern. Here is some data from the messages file (after my parsing).
Sep 18 15:15:12 regie5 vmunix: Alpha boot: available memory from 0xf1e000 to 0x1ffee000
Oct 2 15:15:37 regie5 vmunix: Alpha boot: available memory from 0xf1e000 to 0x1ffee000
Oct 16 15:15:46 regie5 vmunix: Alpha boot: available memory from 0xf1e000 to 0x1ffee000
Oct 30 15:15:50 regie5 vmunix: Alpha boot: available memory from 0xf1e000 to 0x1ffee000
Nov 13 15:15:55 regie5 vmunix: Alpha boot: available memory from 0xf1e000 to 0x1ffee000
Notice that the reboot happens at 15:15 in the afternoon, with a period of exactly two weeks !!
There is nothing in the crontab (at least of root) that indicate any kind of job that is started with this frequency. These dates are all
Wednesdays (yes, it happened this afternoon as well).
I am completely stumped, and I was hoping that some of you alpha gurus out there might have some idea where to start. A quick googling didn't
really help me.
Cheers,
Ed.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:03 EDT