You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Sandeep Agarwal <sa...@gmail.com> on 2007/03/02 08:50:37 UTC
spamd child processing timeout
hello list,
i am facing spamd child processing timeout errors in my maillog and
after that it does not scan mails and SPAMs are passed through. i am
having qmail installation, spamassassin 3.1.8 on perl 5.8.7, with
bayes, awl and userpref on postgresql on a remote machine.
here is my local.cf
rewrite_header Subject [SPAM]
trusted_networks 192.168.100.
required_score 8.0
use_bayes 1
bayes_auto_learn 1
use_auto_whitelist 1
report_safe 0
skip_rbl_checks 0
bayes_store_module Mail::SpamAssassin::BayesStore::PgSQL
bayes_sql_dsn DBI:Pg:dbname=spamassassin;host=[IP ADDRESS]
bayes_sql_username [USER]
bayes_sql_password [PASSWORD]
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList
user_awl_dsn DBI:Pg:dbname=spamassassin;host=[IP ADDRESS]
user_awl_sql_username [USER]
user_awl_sql_password [PASSWORD]
user_scores_dsn DBI:Pg:dbname=spamassassin;host=[IP ADDRESS]
user_scores_sql_username [USER]
user_scores_sql_password [PASSWORD]
bayes_sql_override_username spamd
allow_user_rules 1
header RCVD_IN_PSBL eval:check_rbl('psbl', 'psbl.surriel.com.')
describe RCVD_IN_PSBL Received via a relay in PSBL
tflags RCVD_IN_PSBL net
score RCVD_IN_PSBL 0 1.00 0 1.00
header X_CHINESE_RELAY eval:check_rbl('relay',
'cn.rbl.cluecentral.net.')
describe X_CHINESE_RELAY Received via a relay in China
score X_CHINESE_RELAY 1.5
header X_KOREAN_RELAY eval:check_rbl('relay', 'korea.services.net.')
describe X_KOREAN_RELAY Received via a relay in Korea
score X_KOREAN_RELAY 1.5
below is the extact from the logs
Mar 2 04:38:52 ngblhost3 spamd[12490]: child processing timeout at
/usr/bin/spamd line 1085, <GEN185> line 385.
Mar 2 04:38:52 ngblhost3 spamd[12490]: child processing timeout at
/usr/bin/spamd line 1085, <GEN185> line 385.
Mar 2 04:38:52 ngblhost3 spamd[944]: child processing timeout at
/usr/bin/spamd line 1085, <GEN404> line 160.
Mar 2 04:38:52 ngblhost3 spamd[944]: child processing timeout at
/usr/bin/spamd line 1085, <GEN404> line 160.
Mar 2 04:38:52 ngblhost3 spamd[944]: prepare_cached(SELECT token,
spam_count, ham_count, atime
Mar 2 04:38:52 ngblhost3 spamd[944]: FROM bayes_token
Mar 2 04:38:52 ngblhost3 spamd[944]: WHERE id = ?
Mar 2 04:38:52 ngblhost3 spamd[944]: AND token IN
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?))
statement handle DBI::st=HASH(0x98c08a4) still Active at
/usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/BayesStore/PgSQL.pm
line 445
after this its full of entries like the one below
Mar 2 04:39:37 ngblhost3 qmail-scanner[28726]:
Clear:RC:0(86.18.80.166):SA:0(?/?): 604.7591 29876 frye.ahmed@all.bg
[EMAIL_ADDRESS] Job_Offer._[Thu,_01_Mar_2007_14:58:07_-0800]
<11...@ngblhost3> disgustful.gif:20552 orig-ngblhost3
117278997280128726:29876 1172789977.28728-0.ngblhost3:1121
and after sometime logs show that it is working fine.
Mar 2 04:43:10 ngblhost3 qmail-scanner[28853]:
Clear:RC:0(24.8.5.208):SA:0(?/?): 600.1614 6668
kristydonated@seigakuin-univ.ac.jp [EMAIL_ADDRESS] For_Shalu
<01...@kristydonated>
orig-ngblhost3117279019080128853:6668
1172790190.28855-0.ngblhost3:1878 1172790190.28855-1.ngblhost3:3563
Mar 2 04:43:58 ngblhost3 spamd[12490]: spamd: identified spam
(24.7/8.0) for qscand:510 in 941.7 seconds, 29868 bytes.
Mar 2 04:43:58 ngblhost3 spamd[12490]: spamd: result: Y 24 -
BAYES_99,HELO_DYNAMIC_IPADDR2,HELO_DYNAMIC_SPLIT_IP,HTML_30_40,HTML_FONT_LOW_CONTRAST,HTML_IMAGE_ONLY_12,HTML_MESSAGE,HTML_SHORT_LINK_IMG_2,MIME_HTML_ONLY,RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,RCVD_NUMERIC_HELO,SARE_GIF_ATTACH,SARE_GIF_STOX,TVD_FW_GRAPHIC_NAME_LONG,URIBL_BLACK
scantime=941.7,size=29868,user=qscand,uid=510,required_score=8.0,rhost=ngblhost3,raddr=127.0.0.1,rport=39666,mid=(unknown),bayes=1,autolearn=spam
any suggestions how to fix this or the reason for this.
Sandep
Re: spamd child processing timeout
Posted by Sandeep Agarwal <sa...@gmail.com>.
On 3/16/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> Sandeep Agarwal wrote:
> > On 3/15/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> >> Sandeep Agarwal wrote:
> >> > On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> >> >> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
> >> >>
> >> >> > any suggestions how to fix this or the reason for this.
> >> >>
> >> >> It's probably being caused by bayes expiries. Disable auto expiry and
> >> >> do the expiries via a cron job.
> >> >>
> >> >> Daryl
> >> >
> >> > thanks Daryl, the problem seems fixed, will disabling this feature
> >> > will have any effect on spamassassin ? like db will grow very large
> >> > and slow down spamassassin itself. if yes then whats the best way to
> >> > cleanup the db
> >>
> >> As long as you do the expiries via a cron job the database size will be
> >> kept in check. If you never run expiries, and have bayes_auto_learn
> >> enabled (default) then, yeah, the database is going to grow.
> >>
> >
> > thanks for the reply, bayes_auto_learn is on, how can maintain the db
> > from cronjob ?
>
> sa-learn --force-expire -u username
>
thanks for helping me out
Sandeep
Re: spamd child processing timeout
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Sandeep Agarwal wrote:
> On 3/15/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
>> Sandeep Agarwal wrote:
>> > On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
>> >> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
>> >>
>> >> > any suggestions how to fix this or the reason for this.
>> >>
>> >> It's probably being caused by bayes expiries. Disable auto expiry and
>> >> do the expiries via a cron job.
>> >>
>> >> Daryl
>> >
>> > thanks Daryl, the problem seems fixed, will disabling this feature
>> > will have any effect on spamassassin ? like db will grow very large
>> > and slow down spamassassin itself. if yes then whats the best way to
>> > cleanup the db
>>
>> As long as you do the expiries via a cron job the database size will be
>> kept in check. If you never run expiries, and have bayes_auto_learn
>> enabled (default) then, yeah, the database is going to grow.
>>
>
> thanks for the reply, bayes_auto_learn is on, how can maintain the db
> from cronjob ?
sa-learn --force-expire -u username
Re: spamd child processing timeout
Posted by Sandeep Agarwal <sa...@gmail.com>.
On 3/15/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> Sandeep Agarwal wrote:
> > On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> >> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
> >>
> >> > any suggestions how to fix this or the reason for this.
> >>
> >> It's probably being caused by bayes expiries. Disable auto expiry and
> >> do the expiries via a cron job.
> >>
> >> Daryl
> >
> > thanks Daryl, the problem seems fixed, will disabling this feature
> > will have any effect on spamassassin ? like db will grow very large
> > and slow down spamassassin itself. if yes then whats the best way to
> > cleanup the db
>
> As long as you do the expiries via a cron job the database size will be
> kept in check. If you never run expiries, and have bayes_auto_learn
> enabled (default) then, yeah, the database is going to grow.
>
thanks for the reply, bayes_auto_learn is on, how can maintain the db
from cronjob ?
RE: spamd child processing timeout
Posted by Jean-Paul Natola <jn...@familycareintl.org>.
-----Original Message-----
From: Daryl C. W. O'Shea [mailto:spamassassin@dostech.ca]
Sent: Thursday, March 15, 2007 11:51 AM
To: Sandeep Agarwal
Cc: users@spamassassin.apache.org
Subject: Re: spamd child processing timeout
Sandeep Agarwal wrote:
> On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
>> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
>>
>> > any suggestions how to fix this or the reason for this.
>>
>> It's probably being caused by bayes expiries. Disable auto expiry and
>> do the expiries via a cron job.
>>
>> Daryl
>
> thanks Daryl, the problem seems fixed, will disabling this feature
> will have any effect on spamassassin ? like db will grow very large
> and slow down spamassassin itself. if yes then whats the best way to
> cleanup the db
As long as you do the expiries via a cron job the database size will be
kept in check. If you never run expiries, and have bayes_auto_learn
enabled (default) then, yeah, the database is going to grow.
Daryl
Re: spamd child processing timeout
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Sandeep Agarwal wrote:
> On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
>> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
>>
>> > any suggestions how to fix this or the reason for this.
>>
>> It's probably being caused by bayes expiries. Disable auto expiry and
>> do the expiries via a cron job.
>>
>> Daryl
>
> thanks Daryl, the problem seems fixed, will disabling this feature
> will have any effect on spamassassin ? like db will grow very large
> and slow down spamassassin itself. if yes then whats the best way to
> cleanup the db
As long as you do the expiries via a cron job the database size will be
kept in check. If you never run expiries, and have bayes_auto_learn
enabled (default) then, yeah, the database is going to grow.
Daryl
Re: spamd child processing timeout
Posted by Sandeep Agarwal <sa...@gmail.com>.
On 3/7/07, Daryl C. W. O'Shea <sp...@dostech.ca> wrote:
> On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
>
> > any suggestions how to fix this or the reason for this.
>
> It's probably being caused by bayes expiries. Disable auto expiry and
> do the expiries via a cron job.
>
> Daryl
thanks Daryl, the problem seems fixed, will disabling this feature
will have any effect on spamassassin ? like db will grow very large
and slow down spamassassin itself. if yes then whats the best way to
cleanup the db
Sandeep
Re: spamd child processing timeout
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
On 3/2/2007 2:50 AM, Sandeep Agarwal wrote:
> any suggestions how to fix this or the reason for this.
It's probably being caused by bayes expiries. Disable auto expiry and
do the expiries via a cron job.
Daryl