pb binary.errlog

[otmani]

hello

i have a cluster tru64 V5.1B-4 (pk6) .i inserted a new member ok.
but i have pb when i reboot this new machine
i a have a new binray.errlog without a save of the binary.errlog and when
i use uerf -R a the end of file a i have this
message "Error reading syserr file." .
this message i dont have it on the others members .
thanks

best regards

[Ivan Ferreira]

What is the problem? The uerf command should not be used in V5 anymore. You should install DECEVENT and use the "dia" command, for example "dia -R".

[otmani]

thank

ok i can't use decevent
but each time a reboot this machine
the system create a new binary.errlog with
only the startup

best regards

[Kapil Jha]

Please check permission of errlog file.
BR,
Kapil

[otmani]

hello
the permission is

-rw-r----- 1 root system 65800 Mar 31 09:13 binary.errlog
-rw-r----- 1 root adm 809528 Mar 28 15:00 binary.errlog.old

thank for help
best regards

[Pieter 't Hart]

apearently at boottime a script (/sbin/rc3.d directory ?) is executed to rotate the new binary.errlog file
( kill -USR1 `cat /var/run/binlogd.pid`)
see "man binlogd", search for kill or archive.

In the binary.errlog file there is a record of the configuration. uerf cant read this record but it does display the boot-record and several other record types.
decevent base system can be installed and used without registering a license in lmf.
then you can use dia instead of uerf.

[otmani]

hello

it's a cluster member /sbin/rc3.d/S10binlog is common on cluster.
when i use dia to read binary.errlog i have error to read.

i create new binary pb is idem.so i reboot and i have a new binary.errlog .

thank for help
best regards