From: robert (rbinkl@COMCAST.NET)
Date: Sun Dec 28 2003 - 23:33:34 EST
Try the below Tech Tip
pSeries Tech Tips
Errpt is Corrupt and Is No longer Working
----------------------------------------------------------------------------
----
The errorlog can easily get corrupt. If you run out of space in the /var
directory or if the size of the /var/adm/ras/errlog file is zero, that is
a dead giveaway that it is corrupt. You may also get a " Unexpected
eof" -error every time the cron job starts. Someone could have copied
/dev/null to the /var/adm/ras/errlog file (which is a "no no") or the file
could have filed up and then a errant character was written to it.
The procedure to fix the problem is really simple....You can stop reporting,
delete the file and recreate it with the errdemon command.
#> /usr/lib/errstop
#> rm /var/adm/ras/errorlog
#> /usr/lib/errdemon should recreate it. You can also set a
size for the log file...see below
errclear 0 should clear the log after you recreate it.....
the size WILL NOT BE ZERO though... The only way you know it is empty is by
running the errpt command. It will not return any entries...and just return
to a prompt.
----------------------------------------------------------------------------
----
errorlog files
/usr/lib/nls/msg/$LANG/codepoint.cat
Contains the error log message catalog. In the United States,
the value of the
$LANG environment variable is En_US.
/usr/include/sys/err_rec.h
Contains structures defined as arguments to the errsave kernel
service and
the errlog subroutine.
/var/adm/ras/errlog
Stores instances of errors and failures encountered by the
system.
/var/adm/ras/errtmplt
Contains the Error Record Template Repository.
/dev/error
Source of error records.
/usr/lib/errdemon
Contains the errdemon daemon.
/etc/objrepos/SWservAt
Contains the software service aids attributes object class;
that is, the error
log configuration database.
----------------------------------------------------------------------------
----
Cron Entries
cron entry for root
0 11 * * * /usr/bin/errclear -d S,O 30
0 12 * * * /usr/bin/errclear -d H 90
Errdemon Manual Page
The way "errclear 0" works is that it resets a counter somewhere around byte
#5 of the errlog. This byte contains the record count of the number of
errors in the errlog. errclear sets this value to zero, but technically, the
errors are all still in the errlog. Never do a ">errlog". Always do an
errclear 0.
Robert Lee Binkley
rbinkl@Comcast.net <mailto:rbinkl@Comcast.net>
AIX-L Archives: http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
<http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2>
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
Coyle, Jack
Sent: Sunday, December 28, 2003 7:50 PM
To: aix-l@Princeton.EDU
Subject: errpt Output Format
I upgraded a stand-alone system from AIX 4.3.3 (ML 10) to AIX 5.1 (ML 4)
earlier today. The migration was performed with the CDs. Since the upgrade,
error log entries (at least those I have seen so far) no longer contain
"meaningful" text under the DESCRIPTION heading, only four digit codes. For
example, two that I get routinely on this particular server have identifiers
of A7AB4C8F and E507DCF9. On AIX 4.3.3, these would be accompanied by the
descriptive test "TAPE_MIM_SIM_RECORD" and "TAPE_DRIVE_CLEANING",
respectively. Now, the former displays the code AAA0 and the latter display
the code AAA2. Does anyone know how I can "instruct" the error logger to
report the descriptive text again instead of these codes? TIA for any and
all information.
Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
jack.coyle@rexhealth.com
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:25 EDT