subject:"SA Timeouts"

SA Timeouts

2009-08-19 Thread Cory Hawkless

Hi All,

 

Having a problem with my SA setup. I'm using amavisd and Postfix. For some
reason I get the following occasionally

 

Aug 19 15:37:20.176 ceg.caznet.com.au /usr/sbin/amavisd[5]: (5-01-6)
SA dbg: bayes: database connection established

Aug 19 15:37:20.177 ceg.caznet.com.au /usr/sbin/amavisd[5]: (5-01-6)
SA dbg: bayes: found bayes db version 3

Aug 19 15:37:20.179 ceg.caznet.com.au /usr/sbin/amavisd[5]: (5-01-6)
SA dbg: bayes: Using userid: 4

Aug 19 15:37:20.184 ceg.caznet.com.au /usr/sbin/amavisd[5]: (5-01-6)
SA dbg: bayes: corpus size: nspam = 5993, nham = 24505

Aug 19 15:39:30.977 ceg.caznet.com.au /usr/sbin/amavisd[4]: (4-02-4)
(!)SA TIMED OUT, backtrace: at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm line
1961\n\teval {...} called at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm line
1961\n\tMail::SpamAssassin::PerMsgStatus::_get_parsed_uri_list('Mail::SpamAs
sassin::PerMsgStatus=HASH(0xb0945cc)') called at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm line
1852\n\tMail::SpamAssassin::PerMsgStatus::get_uri_detail_list('Mail::SpamAss
assin::PerMsgStatus=HASH(0xb0945cc)') called at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin/URIDNSBL.pm line
207\n\tMail::SpamAssassin::Plugin::URIDNSBL::parsed_metadata('Mail::SpamAssa
ssin::Plugin::URIDNSBL=HASH(0xae5421c)', 'HASH(0xb05f97c)') called at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PluginHandler.pm line
202\n\teval {...} called at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin[...]

 

 

Any ideas?

Re: SA Timeouts

2009-08-19 Thread Matt Kettler

Cory Hawkless wrote:

 Hi All,

  

 Having a problem with my SA setup. I’m using amavisd and Postfix. For
 some reason I get the following occasionally

  

 Aug 19 15:37:20.176 ceg.caznet.com.au /usr/sbin/amavisd[5]:
 (5-01-6) SA dbg: bayes: database connection established

 Aug 19 15:37:20.177 ceg.caznet.com.au /usr/sbin/amavisd[5]:
 (5-01-6) SA dbg: bayes: found bayes db version 3

 Aug 19 15:37:20.179 ceg.caznet.com.au /usr/sbin/amavisd[5]:
 (5-01-6) SA dbg: bayes: Using userid: 4

 Aug 19 15:37:20.184 ceg.caznet.com.au /usr/sbin/amavisd[5]:
 (5-01-6) SA dbg: bayes: corpus size: nspam = 5993, nham = 24505

 Aug 19 15:39:30.977 ceg.caznet.com.au /usr/sbin/amavisd[4]:
 (4-02-4) (!)SA TIMED OUT, backtrace: at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
 line 1961\n\teval {...} called at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
 line
 1961\n\tMail::SpamAssassin::PerMsgStatus::_get_parsed_uri_list('Mail::SpamAssassin::PerMsgStatus=HASH(0xb0945cc)')
 called at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
 line
 1852\n\tMail::SpamAssassin::PerMsgStatus::get_uri_detail_list('Mail::SpamAssassin::PerMsgStatus=HASH(0xb0945cc)')
 called at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin/URIDNSBL.pm
 line
 207\n\tMail::SpamAssassin::Plugin::URIDNSBL::parsed_metadata('Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0xae5421c)',
 'HASH(0xb05f97c)') called at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PluginHandler.pm
 line 202\n\teval {...} called at
 /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin[...]

  


Roughly twice a day?

If so, I'm guessing a bayes expire run makes the SA run just long enough
to get killed (expiry does take a while, depending on hardware and DB
size, it adds around 1-2 minutes to a run.

. Try either:
1) extend the amavis timeout by 30 seconds
2) disable SA's bayes_auto_expire, and use a cronjob to run sa-learn
--force-expire instead.

and see if it goes away.

Botnet.pm causing SA timeouts

2008-04-10 Thread Koopmann, Jan-Peter

Hi, 

 

I just noticed BotNet (0.8) causing SA timeouts when used with
MailScanner. This is what the log gives me:

 

[21308] dbg: spf: query for
[EMAIL PROTECTED]/75.117.130.5/unknown: result: fail,
comment: Please see
http://www.openspf.org/Why?id=esuapmet_1966%40mater.ustb.edu.cnip=75.11
7.130.5receiver=proxy.aclick.de, text: Mechanism '-all' matched

[21308] dbg: Botnet: starting

[21308] dbg: Botnet: no trusted relays

[21308] dbg: Botnet: get_relay good RDNS

[21308] dbg: Botnet: IP is '75.117.130.5'

[21308] dbg: Botnet: RDNS is '!75.117.130.5!'

[21308] dbg: Botnet: HELO is ''

[21308] dbg: Botnet: sender '[EMAIL PROTECTED]'

 

Then it just hangs for quite some time and finally runs into the
timeout. Any idea?

 

Regards, 

  JP

Re: Botnet.pm causing SA timeouts

2008-04-10 Thread Mark Martinec

Jan-Peter,

 I just noticed BotNet (0.8) causing SA timeouts

 Then it just hangs for quite some time and finally runs into the
 timeout. Any idea?

A known problem, it uses a default timeout of Net::DNS,
which is very long for certain unresolvable DNS queries.
Try the following patch:


--- Botnet.pm.ori   2007-08-06 15:59:16.0 +0200
+++ Botnet.pm   2007-08-06 16:02:43.0 +0200
@@ -711,5 +711,14 @@
 (defined $max) 
 ($max =~ /^-?\d+$/) ) {
-  $resolver = Net::DNS::Resolver-new();
+  $resolver = Net::DNS::Resolver-new(
+   udp_timeout = 5,
+   tcp_timeout = 5,
+   retrans = 0,
+   retry = 1,
+   persistent_tcp = 0,
+   persistent_udp = 0,
+   dnsrch = 0,
+   defnames = 0,
+   );
   if ($query = $resolver-search($name, $type)) {
  # found matches
@@ -834,5 +843,14 @@
my ($ip) = @_;
my ($query, @answer, $rr);
-   my $resolver = Net::DNS::Resolver-new();
+   my $resolver = Net::DNS::Resolver-new(
+   udp_timeout = 5,
+   tcp_timeout = 5,
+   retrans = 0,
+   retry = 1,
+   persistent_tcp = 0,
+   persistent_udp = 0,
+   dnsrch = 0,
+   defnames = 0,
+   );
my $name = ;
 


Mark

RE: Botnet.pm causing SA timeouts

2008-04-10 Thread Koopmann, Jan-Peter

  Then it just hangs for quite some time and finally runs into the
  timeout. Any idea?
 
 A known problem, it uses a default timeout of Net::DNS,
 which is very long for certain unresolvable DNS queries.
 Try the following patch:

Looks like this did the trick!

Great. Thanks!

Re: Botnet.pm causing SA timeouts

2008-04-10 Thread John Rudd



Mark,

Thanks, I'll try to work that into 0.9.


John



Mark Martinec wrote:

Jan-Peter,


I just noticed BotNet (0.8) causing SA timeouts



Then it just hangs for quite some time and finally runs into the
timeout. Any idea?


A known problem, it uses a default timeout of Net::DNS,
which is very long for certain unresolvable DNS queries.
Try the following patch:


--- Botnet.pm.ori   2007-08-06 15:59:16.0 +0200
+++ Botnet.pm   2007-08-06 16:02:43.0 +0200
@@ -711,5 +711,14 @@
 (defined $max) 
 ($max =~ /^-?\d+$/) ) {
-  $resolver = Net::DNS::Resolver-new();
+  $resolver = Net::DNS::Resolver-new(
+   udp_timeout = 5,
+   tcp_timeout = 5,
+   retrans = 0,
+   retry = 1,
+   persistent_tcp = 0,
+   persistent_udp = 0,
+   dnsrch = 0,
+   defnames = 0,
+   );
   if ($query = $resolver-search($name, $type)) {
  # found matches
@@ -834,5 +843,14 @@
my ($ip) = @_;
my ($query, @answer, $rr);
-   my $resolver = Net::DNS::Resolver-new();
+   my $resolver = Net::DNS::Resolver-new(
+   udp_timeout = 5,
+   tcp_timeout = 5,
+   retrans = 0,
+   retry = 1,
+   persistent_tcp = 0,
+   persistent_udp = 0,
+   dnsrch = 0,
+   defnames = 0,
+   );
my $name = ;
 



Mark

SA Timeouts

Re: SA Timeouts

Botnet.pm causing SA timeouts

Re: Botnet.pm causing SA timeouts

RE: Botnet.pm causing SA timeouts

Re: Botnet.pm causing SA timeouts

6 matches

Site Navigation

Mail list logo

Footer information