AW: Trophie worker processes dying at a high rate: am I alone?

Hi Alain,

i think this behaviour with sig11 depends on the quality of the pattern
files. at the end of last year we had much trouble with aborting trophies
under solaris 8. the problem disappeared without any intervention. and
sometimes the behaviour changed visibly from one pattern to the next one.
these days the patterns seem to be ok. 

regards - uli


-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]Im
Auftrag von Alain Fauconnet
Gesendet: Dienstag, 17. August 2004 05:16
An: [email protected]
Betreff: [vtools] Trophie worker processes dying at a high rate: am I
alone?


Hello there,

I wonder if there are other Trophie users out there?

Recently,   my   previously   solid-as-a-rock   Trophie   has  started
misbehaving, worker processes SIGSEGVing at a high  rate.  The  master
process was staying up though, so Amavisd-new couldn't detect this and
it effectively brought our mail traffic to a standstill.  And  yes  of
course, last time it happened on a friday evening...

This caused a bunch of lines like this in the mail log:
Aug 13 23:59:59 mail-gate trophie[13034]: SIGNAL [11] caught - cleaning up
and exiting.

I haven't changed much on this box lately (Linux RH 7.3 in self-update
from  source mode now). Of course my trend-update.pl script did change
to  (partially  at this time) manage the new numbering, but well, it's
still  just  downloading the VPNs so I can't see how this would be the
reason.  No,  this  machine  isn't running my hacked Trophie yet. It's
still using the vanilla 1.12.

Anyone else experiencing this? Just to know if that's something  local
to my set-up.

Greets,
_Alain_
_______________________________________________
vtools mailing list
[email protected]
http://www.vanja.com/list/listinfo.cgi/vtools