On Friday November 3 2006 05:23, Matt Kettler wrote:
I believe the option is $sa_timeout
Not sure what the default is, probably 30. Which should be enough to
prevent that problem, unless you have a LOT of sa instances contending
for the AWL database.
Try adding a $sa_timeout = 60 to your
On 11/3/06, Mark Martinec [EMAIL PROTECTED] wrote:
On Friday November 3 2006 05:23, Matt Kettler wrote:
I believe the option is $sa_timeout
Not sure what the default is, probably 30. Which should be enough to
prevent that problem, unless you have a LOT of sa instances contending
for the AWL
Hi There,
Looks like ive solved one issue, and another crops up!... I think that
i may need to move to a mysql storage engine here? approx 17,000
messages a day incoming on this server.
Any pointers here? - Thanks!!
Nov 4 11:39:40 mx1 amavis[32148]: (32148-07) SA TIMED OUT, backtrace:
at
Simon,
Looks like ive solved one issue, and another crops up!... I think that
i may need to move to a mysql storage engine here? approx 17,000
messages a day incoming on this server.
Any pointers here? - Thanks!!
Nov 4 11:39:40 mx1 amavis[32148]: (32148-07) SA TIMED OUT, backtrace:
at
Simon wrote:
Hi There,
Using spamassassin 3.1.3-0bpo1 from backports.org on debian sarge. We
did have the standard 3.0.x sarge package. Using amavis-new to call
spamassassin and after upgrading spamassassin we are now getting these
messages in the mail.log. Would someone please be able to
On 11/3/06, Matt Kettler [EMAIL PROTECTED] wrote:
Simon wrote:
Hi There,
Using spamassassin 3.1.3-0bpo1 from backports.org on debian sarge. We
did have the standard 3.0.x sarge package. Using amavis-new to call
spamassassin and after upgrading spamassassin we are now getting these
messages
Is your amavis set with an abnormally short timeout for SA?
Hmm.. Where do find this setting in my amavis conf file?
The default is 30 seconds (at least in older versions of amavisd-new). You
can add:
$sa_timeout = 50;
As Matt says, 'lock_method flock' will also help. Are you using
Simon wrote:
On 11/3/06, Matt Kettler [EMAIL PROTECTED] wrote:
Simon wrote:
Hi There,
Using spamassassin 3.1.3-0bpo1 from backports.org on debian sarge. We
did have the standard 3.0.x sarge package. Using amavis-new to call
spamassassin and after upgrading spamassassin we are now
