Hi!!

I am having a problem with errpt command, when executed it throws an
error:-

logread: unexpected end of file
Unable to process the error log file /var/adm/ras/errlog.
The supplied error log file is not valid: /var/adm/ras/errlog.

I cleared the error log file, two days back with "errclear 0"
Now interesting thing is, the size of /var/adm/ras/errlog right now is
zero while it is mentioned in manual pages of errclear that

Note: The errclear command clears the specified entries, but does not
decrease the error log file size.

Now I dont know what to do....

Any suggestions???????

Thanks & Regards,
Ashutosh

It sounds like your errlog file is corrupted. On our test server, I
renamed the errlog file and touched a new file. Using errpt returned
these errors:

0315-180 logread: UNEXPECTED EOF
0315-171 Unable to process the error log file /var/adm/ras/errlog.
0315-132 The supplied error log is not valid: /var/adm/ras/errlog.

Here's a suggestion to try:

After I renamed the existing errlog file, I rebooted the system. The
errdemon was restarted and the system generated a brand new errlog file
without the corruption.

However, I noticed that when I did this on our test system, it still
managed to pull up error messages I entered in the error log using
"errlogger" command from PRIOR to the shutdown. So I suspect that the
actual data for the errlog file may be found in another file.

I know from the man pages that errpt also reads the diag_log file so it
may be that you have another file that is corrupted and is affecting
the errlog results.

Steve

Ashutosh <hiashutosh@gmail.com> wrote:
A> Hi!!
A>
A> I am having a problem with errpt command, when executed it throws an
A> error:-
A>
A> logread: unexpected end of file
A> Unable to process the error log file /var/adm/ras/errlog.
A> The supplied error log file is not valid: /var/adm/ras/errlog.
A>
A> I cleared the error log file, two days back with "errclear 0"
A> Now interesting thing is, the size of /var/adm/ras/errlog right now is
A> zero while it is mentioned in manual pages of errclear that
A>
A> Note: The errclear command clears the specified entries, but does not
A> decrease the error log file size.
A>
A> Now I dont know what to do....
A>
A> Any suggestions???????
A>
A> Thanks & Regards,
A> Ashutosh
A>

1) Stop the error daemon
2) rm /var/adm/ras/errlog
3) Start the error daemon

--
"... I shook my family tree, and a bunch of NUTS fell out ..."

Bela,

You may want to specify the stopsrc/startsrc commands to use for the
errdemon. I tried it as a subsystem and group but both failed, so I
just figured it would be easier to reboot.

Btw, I also saw this warning in the man pages about stopping the error
reporting daemon when I was looking up info for Ash. This was specific
to the "errstop" command, and since I could not find an errstart
command, I didn't bother mentioning it:

"Normally the errdemon command is started automatically during system
initialization and stopped during system shutdown. The error log should
never be stopped during normal operations. The errstop command should
only be used during special circumstances when it is absolutely
required and the consequences are clearly understood."