Hi all,
currently we are experiencing problems with the caa daemon process on our
Tru64 5.1b Rev 2650 PK3 cluster. When one node is coming under heavy load
during nightly incremental backup runs of some file systems (around 7TB
used space); the caa daemon process on this node starts to produce lots of
<defunct> processes. At the same time the EVM sends out a warning mail
("EVM ALERT [600]: EVM daemon: High event activity - exceeds 500 in 10
minutes"). After doing "/sbin/init.d/clu_caa stop" a new caa daemon starts
and all the <defunct> processes are gone.
Does anybody know how to prevent the caa from forking so many processes or
even better from not defuncting them ?
Regards,
Juergen
--
email: wolf_at_idmt.fhg.de
gilb: Fraunhofer-Institut fuer Digitale Medientechnologie IDMT
98693 Ilmenau, Helmholtzring 1
Tel.: +49 3677 69-4882 Fax: +49 3677 69-4399
Received on Tue May 25 2004 - 13:32:33 NZST