Re: Timeout problem

Brian,

As I suspected, thanks for the confirmation though as I wasn't enjoying
the strace :)  Got it sorted now, as you say spam DB was upto 80mb on
10000+ email per hour was causing probs.  Great, I have had to start
again with the DB but am using purge 2 now rather than cleanup 2 2.  Do
you think this is appropriate?

Cheers,

Al

-----Original Message-----
From: Brian Burton [mailto:[email protected]] 
Sent: 30 December 2006 05:25
To: Allan Stewart; Spamprobe Users
Subject: Re: [Spamprobe-users] Timeout problem

On 12/29/06 10:11 AM, "Allan Stewart"
<[email protected]>
wrote:
> procmail: Timeout, terminating "spamprobe"
> procmail: Rescue of unfiltered data succeeded
> caught signal 15: quitting
> 
> Any ideas how to fix this?  Is it because the database is to large? Or
> perhaps something else.

Sometimes this sort of thing can happen if your spamprobe folder (where
detected spams are stored) has grown extremely large and you have a
background process taking a long time running train-spam on it when the
email arrives.  The background process can hold the database lock for
longer
than procmail is willing to wait.

Do you have a bunch of queued up spamprobe processes running?  If so,
killing them and clearing out your spamprobe folder might help.

All the best,
++Brian



This email was scanned by Postini, the leading provider in Managed Email Security.  For more information visit
www.groveis.com


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV