[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spamassassin-users
Subject:    Re: program failures of spamassassin
From:       Karsten =?ISO-8859-1?Q?Br=E4ckelmann?= <guenther () rudersport ! de>
Date:       2008-05-30 23:58:35
Message-ID: 1212191915.4984.49.camel () monkey
[Download RAW message or body]

On Fri, 2008-05-30 at 09:35 -0700, jon schatz wrote:
> hi,
> 
> i call spamassassin diretly from procmail like so:
> 
> :0fw
> |/usr/bin/spamassassin -D
> #|/usr/bin/spamassassin -D 2>/dev/null

Why do you use the SA *debug* switch in procmail?

FWIW, output on STDERR may cause procmail to lose the F from the
envelope From_ line. This may or may not be related -- I'd remove the -D
anyway, unless you got a really good reason to do so...


> (i recently started looking at debug info again to try and solve this  
> problem without much luck).
> 
> my procmail log file is full of entries like this:
[...]

> the message in question inevitably gets through to my inbox. in the  
> last few months this has gotten out of control to the point where i'm  
> seeing 40-50 of these a day.

These are the failures only. Assuming more spam than that, plus
filtering of ham. I'd suggest using spamc/d instead of starting a full
spamassassin process for each message. This will tradeoff some constant
memory consumption, for the benefit of avoiding a severe startup
penalty.


> if i put these messages into their own  
> folder and try to run sa-learn on them i get a coredump:
> 
> Core was generated by `/usr/bin/perl -T -w /usr/bin/sa-learn --spam -- 
> mbox mail/foreign'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0054de4b in __memp_fput () from /lib/libdb-4.3.so

Berkeley DB.

> (gdb) bt
> #0  0x0054de4b in __memp_fput () from /lib/libdb-4.3.so
> #1  0x00517cd3 in __db_free () from /lib/libdb-4.3.so
> #2  0x004cd112 in __ham_split_page () from /lib/libdb-4.3.so
> #3  0x004c2982 in __ham_quick_delete () from /lib/libdb-4.3.so
> #4  0x0050e968 in __db_c_put () from /lib/libdb-4.3.so
> #5  0x0050803b in __db_put () from /lib/libdb-4.3.so
> #6  0x0051441f in __db_put_pp () from /lib/libdb-4.3.so
> #7  0x00f56a47 in XS_DB_File_STORE ()
>     from /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/DB_File/DB_File.so

Berkeley DB.


> anyone have any ideas here? i'm running:
> 
> [jon@opiate ~]$ spamassassin --version
> SpamAssassin version 3.2.4
>    running on Perl version 5.8.8
> [jon@opiate ~]$ cat /etc/redhat-release
> CentOS release 5 (Final)

Issues with your distros Berkeley DB? Any updates / fixes available?

Problems with the existing (users or sitewide) Bayes or AWL database
being corrupted? In that case, try starting fresh, moving these. If it
turns out to not be the issue, swap it back in.

  guenther


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

[prev in list] [next in list] [prev in thread] [next in thread]