Apologies for late summary (it was Easter break over here)
and thanks to:
Jem Treadwell
Bryan Lavelle
Octave Orgeron
Carl Gaines
Alan Nabeth
It turned out to be something wrong with my
binary.errorlog file (probably corrupted
after the panic). Attempts to remove the error
with /usr/lbin/binex failed, so I finally had to:
1. /sbin/init.d/desta stop
2. /sbin/init.d/binlogd stop
3. mv /var/adm/binary.errorlog /var/adm/binary.errorlog.save
4. /sbin/init.d/binlogd start
5. /sbin/init.d/desta start
Thanks Jem and Alan.
The bad logfile has gone to Compaq so that they can
investigate the looping desta.
Cheers,
Terry.
Original question:
ES40, 4 cpu, Tru64 V5.0A, pk1
After a forced crash to escape from a system hang
(which turned out to be due to a mail problem
with the Postmaster account, resulting in a message
to Postmaster, which then failed resulting in a
message to Postmaster etc etc), the machine
has started up with /usr/opt/compaq/svctools/bin/desta_exec
using 99% cpu. I've tried restarting it with
'/sbin/init.d/desta stop' then '/sbin/init.d/desta start'
The process then starts OK, with 0% cpu, but after about 10 mins
the cpu use again goes to 99%. No log files are growing abnormally,
so what is this thing up to? Any ideas before I resort to a reboot?
Received on Tue Apr 17 2001 - 09:35:13 NZST