Hi,
> The reported stackdump just shows a routine that was executing at
> the time when timer expired. It often shows the problem section
> (like a database access), but may just show an innocent bystander
> code which happened to be normally executing at the time.
Great, thanks. How about from a
Alex,
> I have a server that's frequently pretty busy during the day, and just
> started to notice these messages periodically:
>
> Jun 8 13:35:39 mail01 amavis[28784]: (28784-272) SA TIMED OUT,
> backtrace: at /usr/lib/perl5/5.6.0/i386-linux/IO/Select.pm line
> 104\n\tIO::Select::can_read('IO::
On Thu, 2007-11-01 at 16:28 -0400, Daryl C. W. O'Shea wrote:
> Robert Fitzpatrick wrote:
> > I have the following error message in the logs, didn't even notice until
> > tracking down an email for a user today, but been happening in all my
> > logs back the last week. All three servers running mai
Robert Fitzpatrick wrote:
I have the following error message in the logs, didn't even notice until
tracking down an email for a user today, but been happening in all my
logs back the last week. All three servers running mail filtering to
pgsql db have this error including the server which hosts t
On Tue, Dec 05, 2006 at 06:42:01PM +0100, Stefan Jakobs wrote:
> Here an other hint:
> Every day I execute the following command and force an expire of the Bayes DB:
> /usr/bin/sa-learn --dbpath /var/amavis/.spamassassin
> -p /var/amavis/.spamassassin/user_prefs -u vscan --force-expire
>
> In l
Am Dienstag, 5. Dezember 2006 18:16 schrieb Theo Van Dinter:
> On Tue, Dec 05, 2006 at 06:11:56PM +0100, Stefan Jakobs wrote:
> > > > 71\n\tMail::SpamAssassin::Locker::jittery_one_second_sleep('Mail::Spa
> > > >mAss assin::Locker::UnixNFSSafe=HASH(0x9747010)')
> > >
> > > Are you using NFS? If not
On Tue, Dec 05, 2006 at 06:11:56PM +0100, Stefan Jakobs wrote:
> > > 71\n\tMail::SpamAssassin::Locker::jittery_one_second_sleep('Mail::SpamAss
> > >assin::Locker::UnixNFSSafe=HASH(0x9747010)')
> >
> > Are you using NFS? If not, switch to flock.
>
> No, I don't use NFS. What do you mean with "swit
Am Dienstag, 5. Dezember 2006 16:12 schrieb Theo Van Dinter:
> On Tue, Dec 05, 2006 at 04:06:17PM +0100, Stefan Jakobs wrote:
> > Dec 5 15:32:58 server amavis[23505]: (23505-01-24) SA TIMED OUT,
> > backtrace: at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.pm
> > line 71\n\teval {...}
On Tue, Dec 05, 2006 at 04:06:17PM +0100, Stefan Jakobs wrote:
> Dec 5 15:32:58 server amavis[23505]: (23505-01-24) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.pm line 71\n\teval
> {...} called at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.p
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:
>
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 /usr/
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
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
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 spamassass
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 Pyzor?
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
> m
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
Gary V wrote:
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within
10 seconds, I would imagine it's unlikely it will respond - so I
wouldn't waste time waiting a
Gary V wrote:
I upgraded to SA 3.1.4 last night and now I have two issues that I'm
trying to resolve:
(1)
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
You need to enable (uncomment) the DCC plugin in v310.pre
Done and th
Matt Kettler wrote:
M. Lewis wrote:
I upgraded to SA 3.1.4 last night and now I have two issues that I'm
trying to resolve:
(1)
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
If you've not edited /etc/mail/spamassassin/v310.pre
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within 10
seconds, I would imagine it's unlikely it will respond - so I wouldn't waste
time waiting around another 8
I upgraded to SA 3.1.4 last night and now I have two issues that I'm trying
to resolve:
(1)
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
You need to enable (uncomment) the DCC plugin in v310.pre
(2)
In the logs I'm seeing
M. Lewis wrote:
>
> I upgraded to SA 3.1.4 last night and now I have two issues that I'm
> trying to resolve:
>
> (1)
> spamassassin -D --lint is giving me an error:
> [2533] warn: config: failed to parse line, skipping: dcc_timeout 18
If you've not edited /etc/mail/spamassassin/v310.pre to load th
23 matches
Mail list logo
