binary.errlog reading error

[Kafsat Taiyus]

Hi,

I am supporting Compaq Tru64 UNIX V5.1A

I can't read binary.errlog file.
I tried creating new log using command kill -USR1 `cat /var/run/binlogd.pid`
tried stopping binlogd removing binary.errlog file and starting binlogd


but everytime give command uerf -f /var/adm/binary.errlog
getting
uerf version 4.2-011 (122)



Error reading syserr file.

The file is defenitely there
lrwxr-xr-x 1 root adm 43 Aug 20 2002 /var/adm/binary.errlog -> ../cluster/members/{memb}/adm/binary.errlog

Any idea why and what can I do about it?

TIA

Kafsat

[Johan Brusche]

Answered this same question in this forum last week.
"uerf" has been officially dropped for some time as utility for decoding binary.errlog .The format of the errorlog packets has changed and uerf does not understand the new format, which results in the error you are seeing.
You should now use DECevent (/usr/sbin/dia)
or Compaq Analyze(/usr/sbin/ca), depending on the type of CPU in your system.
For ES40,ES45,ES160,ES1280 type of systems use ca.
If these utilities are not present on your system, you must install them from the "Associated Prod's"-CD, kits DECevent or WEBES.
With the new HP it gets even more confusing, since ca has been re-baptised to wsea.

Johan.

[Michael Schulte zur Sur]

Hi,

as Johan mentioned decevent is better than uerf. But maybe the binary.errlog is corrupted. Make a copy of the file, stop bindlogd, zero it, start binlogd and do a test message with logger -b and then test uerf again.

Michael

[Johan Brusche]

Michael,

Kafsat already recycled the binary.errlog the CORRECT way by using "kill -USR1 " as posted in his initial entry.

Johan.

[Michael Schulte zur Sur]

Hi Johan,

thanks for correcting me. I missed that part of the sentence. :-(

Michael

[Ralf Puchner]

But it is also important to clean up the damaged file by using "cp /dev/null /var/adm/binary.errlog".
Otherwise a kill doesn't really solve the problem ;-)

[Michael Schulte zur Sur]

Hi Ralf,

does the start of binlogd create the binary.errlog after this has been removed?

Michael

[Johan Brusche]

Using /dev/null is the ancient pre V5.x method for creating a new binary.errlog....

The binlogd manpage cleary states that a kill -USR1 moves the current(eventually damaged)logfile to a directory linked behind /usr/adm/binlog.saved/ and that a freshly initialized binary.errlog is created.

Under certain conditions (which I still haven't found documented) the new logfile will even contain a "system configuration" event as the first entry (whithout having to reboot), which helps compaq-analyze to propose FRU part-numbers.

So please start using "kill -USR1...." !

Johan.

[Kafsat Taiyus]

Thank you all,

Now I am looking for (/usr/sbin/dia) or
(/usr/sbin/ca). Looks like none of these is installed on the system. I dont have associated products CD for Tru64 UNIX V5.1A
but I have the CD for Tru64 UNIX V5.1B.

I have looked in hpweb sites to download any of these utilities for V5.1A but failed to locate a source. If you know any link please let me know.

Thank you again and have a lovely day

Regards
Kafsat

[Johan Brusche · Accepted solution]

It is OK and supported, to install the DECevent and/or WEBES kit from the V5.1B Assoc Prod's CDs.
The DECevent kit can als be obtained from:
http://h18023.www1.hp.com/support/svctools/decevent/index.htm

Enjoy
Johan.