[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Milter (spamassassin): to error state : spamassassin milter seems to

From: Dan Nelson
Subject: Re: Milter (spamassassin): to error state : spamassassin milter seems to randomly fail
Date: Mon, 18 Aug 2003 09:54:15 -0500
User-agent: Mutt/1.5.4i

In the last episode (Aug 18), Joost van Baal said:
> OK, have build with these flags.  I am working with $Id:
> spamass-milter.cpp,v 1.52 2003/06/26 15:10:44 dnelson Exp $ (in
> spamass-milter-0.2.0, with some Debian patches).
> In the spamass-milter.cpp CVS log I see:
>  revision 1.61
>  date: 2003/08/06 04:45:46;  author: dnelson;  state: Exp;  lines: +11 -4
>  Fix two cases where we caught an error but didn't clean up the assassin
>  object.
> The revision 1.60 date: 2003/08/06 04:29:48; log looks interesting too.
> Would it be useful if I started using 1.61 or later?

Possibly.  If your milter process is dying with signal 6, then r1.61
wil most likely fix it (the code ends up throwing an uncaught exception
and abort()ing).  Beware that CVS versions 1.62 and above sometimes
leak processes due to my use of popen() to call "sendmail -bv" (I don't
think popen and pthreads play nice together); I'm trying to figure out
where the bug is.
> Anyway, my /usr/sbin/spamass-milter is an "ELF 32-bit LSB executable,
> Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs),
> not stripped".
> I have
>  address@hidden:~# ps axfww | grep '[s]pamass'
>  32217 ?        S      0:00 /usr/sbin/spamass-milter -p 
> /var/run/sendmail/spamass.sock
>  32218 ?        S      0:00  \_ /usr/sbin/spamass-milter -p 
> /var/run/sendmail/spamass.sock
>  32219 ?        S      0:00      \_ /usr/sbin/spamass-milter -p 
> /var/run/sendmail/spamass.sock

This looks fine; LinuxThreads uses one process for each thread and
creates two helper processes, so an idle milter will look like this.
> In another session, a backtrace looked like:
>  (gdb) bt
>  #0  0x400bf87e in sigsuspend () from /lib/
>  #1  0x4008b2e7 in sigwait () from /lib/
>  #2  0x08055707 in mi_signal_thread ()
>  #3  0x400880ba in pthread_start_thread () from /lib/

That's just an idle milter process.
> You said you've been able to reproduce the behaviour.  How did you
> manage to do that?

I actually block a lot of spam via domainname and netblock blacklists
in access.txt, so I just commented those out to get more spam sent to
the milter.  I don't have a message that I know kills it or anything.
        Dan Nelson

reply via email to

[Prev in Thread] Current Thread [Next in Thread]