Re: "Mysterious" system crashes
- From: Robert Deininger <rdeininger@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Nov 2007 08:09:51 -0500
In article <473D0765.2050904@xxxxxxxxxxx>,
bradhamilton <bradhamilton@xxxxxxxxxxx> wrote:
Robert Deininger wrote:
In article <473CF41C.1060500@xxxxxxxxxxx>,
bradhamilton <bradhamilton@xxxxxxxxxxx> wrote:
Richard B. Gilbert wrote:
[...]
Do you have a dump file? SYS$SYSTEM:SYSDUMP.DMPRABBIT::SYSTEM$ dir/dat=(cre,mod) sys$system:sysdump.dmp
Is a dump being written to it?
Directory SYS$SYSROOT:[SYSEXE]
SYSDUMP.DMP;2 245215/245248 28-DEC-2002 23:33:40.29
12-NOV-2006 22:20
:02.28
Not for a year or so...
Dunno if the modification date on the file is a good indicator.
Use ANALYZE/CRASH to see what, if anything, is in the dump file.
Hi Robert,
Just an old crash from July of this year (unrelated).
See my latest post in this thread for a possible hypothesis...
[...]
Unless you force a crash, and actually see the resulting crash dump in
the dump file, you can't rule out a configuration error. (See the
System Manager's Manual for advice on dump files and forcing a crash.)
This is 5 or 10 minutes work, and should be standard procedure whenever
VMS has been installed, upgraded, or reconfigured.
Another useful diagnostic in your situation would be a serial console,
connected to something that can log all the output.
You might be getting some useful information from the FW or from VMS,
but if you have a graphics console, and automatically reboot, the output
will be gone by the time you get home.
-- Robert
.
- References:
- Re: "Mysterious" system crashes
- From: Robert Deininger
- Re: "Mysterious" system crashes
- From: bradhamilton
- Re: "Mysterious" system crashes
- Prev by Date: Converting serial I/O to ethernet I/O
- Next by Date: Re: system constants in COBOL
- Previous by thread: Re: "Mysterious" system crashes
- Next by thread: Re: "Mysterious" system crashes
- Index(es):
Relevant Pages
|