HP3000-L Archives

May 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jim Phillips <[log in to unmask]>
Reply To:
Jim Phillips <[log in to unmask]>
Date:
Tue, 28 May 2002 11:50:54 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (108 lines)
Since we do a backup every day, holiday or not, I came in yesterday to
change the tape for the next backup.  Imagine my chagrin when I found my
venerable 3000 sitting at the "Enter boot command" prompt.  This looked
suspiciously like a power outage again, but the NT Server and another 3000
(that are on a different UPS) were still up and running.  So, I thought I
would look into the system log files and see what happened.

Using SYSDIAG>LOGTOOL, these are the log types we have enabled:

   Type         Description
  ------    ---------------------
   100      LOG FAILURE
   101      SYSTEM UP
   102      JOB INITIATION
   103      JOB TERMINATION
   104      PROCESS TERMINATION
   105      NM FILE CLOSE
   106      SYSTEM SHUTDOWN
   107      POWER FAILURE
   111      I/O ERROR
   112      PHY. MOUNT/DISMOUNT
   113      LOG. MOUNT/DISMOUNT
   114      TAPE LABEL
   115      CONSOLE LOG
   116      PROGRAM FILE EVENT
   120      NM SPOOLING
   121      FILE QUARANTINE EVNT
   130      AIFs
   131      ADD PROCESSOR LAUNCH
   134      PASSWORD CHANGE
   135      SYS LOGGING CONFIG
   136      RESTORE
   137      PRINTER ACCESS FAIL
   138      ACD CHANGE
   139      STREAM INITIATION
   140      USER LOGGING
   141      PROCESS CREATION
   143      CHGROUP
   144      FILE OPEN
   146      MAINTENANCE REQUEST
   148      UPS MONITOR LOG
   150      DIAGNOSTIC INFO
   151      HPMC
   152      LPMC
   160      CM FILE CLOSE
   205      NM FILE CLOSE
   227      CHDIR
   228      PROCESS ADOPTION
   229      FILE OWNER CHANGE
   234      PASSWORD CHANGES
   236      RESTORE
   238      ACD CHANGE
   240      USER LOGGING
   241      PROCESS CREATION
   242      SECURITY CONFIG CHG
   244      FILE OPEN
   245      CI COMMAND LOG

Aha!  I said.  I'll look at the previous log file and see what happened
using types 106 and 107.  However, no 106's (System Shutdown) were reported.
Checking type 148 reveals the following:

 ===========================================================================
===
FRI, MAY 24, 2002    5:04 AM       LOG1368.PUB.SYS              SYSTEM (PIN
60)
UPS MONITOR LOG
MONITOR STATUS   :  $FFDF0089

NMEV#200@298 UPS LDEV  reports loss of AC input power. (UPSERR 0033)

 ===========================================================================
===
FRI, MAY 24, 2002    5:04 AM       LOG1368.PUB.SYS              SYSTEM (PIN
60)
UPS MONITOR LOG
MONITOR STATUS   :  $00240089

NMEV#100@298 UPS LDEV  reports AC input power restored. (UPSWRN 0036)

 ===========================================================================
===
MON, MAY 27, 2002    5:49 AM       LOG1368.PUB.SYS              SYSTEM (PIN
60)
UPS MONITOR LOG
MONITOR STATUS   :  $FFDF0089

NMEV#200@298 UPS LDEV  reports loss of AC input power. (UPSERR 0033)


Now, it sure looks to me like the power "failed" at 5:49 AM on May 27th and
the system eventually crashed because the UPS ran out of battery power or
something.  But why isn't there a system shutdown log record?  Do I need to
log some other event type?

Thanks in advance,

Jim Phillips                           Information Systems Manager
Email: [log in to unmask]     Therm-O-Link, Inc.
Phone: 330-527-2124                         P. O. Box 285
Fax:   330-527-2123                           10513 Freedom Street
Web:   http://www.tolwire.com          Garrettsville, OH  44231

I WANT MY MPE!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2