Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

error with the dia -R command

AKSHAY.DANAK
Occasional Contributor

error with the dia -R command

The customer has ES40 server with Tru64 unix 5.1 installed.
The error on the server:

Event file parsing error: event 642 event trailer not found
Event file parsing error: recovered after 936 bytes were skipped.
Event file parsing error: event 1834 invalid event header type

decevent V3.4

This is the message flashed with the following command:
# dia -R |pg

Alternately I have started using the command:
# uerf -R |pg which has no such event file parsing error.

Is there something that can be done for the dia command.

Regards,

Akshay.Danak
2 REPLIES
Han Pilmeyer
Esteemed Contributor

Re: error with the dia -R command

uerf is the traditional error analysis tool. It was even available on ULTRIX. It hasn't been updated in ages and therefore can not analyze events for the later systems.

For EV5 platforms, you should use DECevent (dia) instead. However DECevent has now also been retired.

For the latest systems (EV6 and newer) you should use System Event Analyze (SEA), formerly known as Compaq Analyze which is available through WEBES. This is still being updated for the latest events for systems hardware, operating system events and storage events.
Mohamed K Ahmed
Trusted Contributor

Re: error with the dia -R command

Use the following command
# dia -R | more

If you still get problems, you can try to create a new binary.errorlog file and test it. Use the following commands:

# cd /var/adm
# mv binary.errlog binary.errlog.old
# kill `cat /var/adm/binlogd.pid` (notice the ` mark is the one next to the 1/! key on your keyboard)
# /usr/sbin/binlogd (restarts errlog process)
# /usr/bin/logger -b TEST (add a test entry)
# dia -R | more

HTH

Mohamed