To all System Administrators,
This list and the people on it are a wonderful resource!
Many thanks to the following people who responded to my question:
Denise Simon <Denise.Simon_at_compaq.com>
John Gormley <jgormley_at_scu.edu.au>
Robert Mulley <robert_at_gnsconsulting.com.au>
Bryan Lavelle <Bryan.Lavelle_at_COMPAQ.com>
Nick Leonard <nickl_at_poole-tr.swest.nhs.uk>
Toni Harbaugh-Blackford <harbaugh_at_ncifcrf.gov>
ORIGINAL QUESTION:
The following error event occurs--and is recorded in the
binary.errlog of one of our servers--each time the server is
rebooted:
********************************* ENTRY 3.
*********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 110. MACHINE STATE
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Jul 2 18:55:03 1999
OCCURRED ON SYSTEM garrett
SYSTEM ID x0007001B
SYSTYPE x00000000
SYSTEM STATE x0003 CONFIGURATION
What does this particular error event mean?
SUMMARY OF RESPONSES:
The consensus of responses indicates that this error event is
perfectly normal and is nothing to worry about. As one respondent
pointed out, "(n)ot everything that is entered into the binary.errlog
is an error."
In this case, the event is an informational system configuration
message. It is useful in determining system hardware configuration,
and for this reason, it can be helpful in dealing with system panics.
Two repondents pointed out that uerf is not the optimal tool for
viewing these types of events. Rather, they suggested the need to
install and to use DECevent (dia), which can provide much valuable
information.
Although I did not explicitly state it in my original message, an
additional reason why the message concerned me was that it has
appeared on only one of our three Alpha servers. One respondent
echoed a similar concern about his three servers, where the event
occurs on two out of the three machines.
Fortunately, a single respondent also appears to have addressed this
issue by pointing out that the event "is generated by reasonably
up-to-date system firmware." Sure enough--in our case, at least--the
machine with the message has much newer firmware (currently) than our
remaining two servers, which have never generated the message.
Thank you all once again! I greatly appreciate your help!
Sincerely,
Gary Shimek
MSOE Library
shimek_at_msoe.edu
Received on Wed Jul 07 1999 - 15:09:32 NZST