Re: bayes auto expire question
On 08/29/2012 01:32 PM, RW wrote: On Wed, 29 Aug 2012 11:08:09 +0200 Leonardo Verzetti wrote: I have an other question: During the expire operation does the SA use the bayes db to check the email or the SA works without use bayes? I think it does continue using bayes. IIWY I'd ignore any errors that occurred under autoexpiry, unless they repeat under forced expiry. They may just be a symptom of an autoexpiry not terminating cleanly under a timeout. I disabled the auto expire restarted the spamassassin and manually run the force expire but i have the same warning. Do you think the lock it's when the SA try to write on db or when it try to read the db for the bayes check? Thanks Leonardo Aug 30 14:09:46.322 [7548] dbg: bayes: tie-ing to DB file R/O /var/spamassassin/bayes_db/bayes_toks Aug 30 14:09:46.322 [7548] dbg: bayes: tie-ing to DB file R/O /var/spamassassin/bayes_db/bayes_seen Aug 30 14:09:46.323 [7548] dbg: bayes: found bayes db version 3 Aug 30 14:09:46.323 [7548] dbg: bayes: DB journal sync: last sync: 1346328286 Aug 30 14:09:46.323 [7548] dbg: bayes: opportunistic call found journal sync due Aug 30 14:09:46.323 [7548] dbg: plugin: Mail::SpamAssassin::Plugin::Bayes=HASH(0x8fbc020) implements 'learner_sync', priority 0 Aug 30 14:09:46.323 [7548] dbg: bayes: bayes journal sync starting Aug 30 14:09:46.324 [7548] dbg: locker: mode is 438 Aug 30 14:09:46.324 [7548] dbg: locker: safe_lock: created /var/spamassassin/bayes_db/bayes.mutex Aug 30 14:09:46.324 [7548] dbg: locker: safe_lock: trying to get lock on /var/spamassassin/bayes_db/bayes with 10 timeout Aug 30 14:09:56.331 [7548] dbg: locker: safe_lock: timed out after 10 seconds Aug 30 14:09:56.332 [7548] warn: bayes: cannot open bayes databases /var/spamassassin/bayes_db/bayes_* R/W: lock failed: Aug 30 14:09:56.332 [7548] dbg: bayes: bayes journal sync completed Aug 30 14:09:56.332 [7548] dbg: config: score set 3 chosen. Aug 30 14:09:56.333 [7548] dbg: config: time limit 300.0 s SA logs: warn: bayes: cannot open bayes databases /var/spamassassin/bayes_db/bayes_* R/W: lock failed: Interrupted system call info: prefork: child states: IBBIBIB -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
Re: bayes auto expire question
I have an other question: During the expire operation does the SA use the bayes db to check the email or the SA works without use bayes? SA logs: warn: bayes: cannot open bayes databases /var/spamassassin/bayes_db/bayes_* R/W: lock failed: Interrupted system call info: prefork: child states: IBBIBIB Thanks Leonardo On 08/28/2012 05:19 PM, RW wrote: On Tue, 28 Aug 2012 16:48:29 +0200 Leonardo Verzetti wrote: Sometime the expire operation don't work properly, it seems that the compression failed (the byes_db size don't decrease) while the lock persists and the spam child in busy (B) status increase. What is the reason for this issue? Are there any information on SA log about this? There are known problems with autoexpiry due its being carried out as a side effect of scanning a mail, and hence under the same timeouts. Switching to expiry from cron is the right thing to do. You may want to check for any cruft in the bayes directory. I would like perform a cronjob in order to expire the byes_db. Have i to stop the MTA service before? Shouldn't be needed. -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
bayes auto expire question
Hi all I have some quetions on bayes auto expire. During the expire operation (compress and lock) does the SA engine use the bayes_toks to check the email? SA logs: warn: bayes: cannot open bayes databases /var/spamassassin/bayes_db/bayes_* R/W: lock failed: Interrupted system call info: prefork: child states: IBBIBIB Sometime the expire operation don't work properly, it seems that the compression failed (the byes_db size don't decrease) while the lock persists and the spam child in busy (B) status increase. What is the reason for this issue? Are there any information on SA log about this? I would like perform a cronjob in order to expire the byes_db. Have i to stop the MTA service before? My server: Slackware 10.2.0 Linux 2.6.34 #1 SMP Tue May 25 12:08:19 CEST 2010 i686 unknown unknown GNU/Linux SpamAssassin version 3.3.2 Perl version 5.8.7 Qmail 1.03 Spamassassin configurathion: bayes_learn_to_journal1 bayes_journal_max_size102400 bayes_expiry_max_db_size25 bayes_auto_expire1 Ask me if you need more information Thanks Leonardo -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
Problem afther sa-update
Hi all I have a problem on spamassassin afther sa-update The server download the update, it reload the service and the child process wasn't correctly killed and the father process go on zombie state. Message on spamd log: Thu Jun 14 08:57:46 2012 [20774] info: spamd: server hit by SIGHUP, restarting Thu Jun 14 08:57:46 2012 [20774] info: spamd: child [9228] killed successfully: interrupted, signal 2 (0002) Thu Jun 14 08:58:49 2012 [20774] warn: Use of uninitialized value $selerr in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line 332. Thu Jun 14 08:58:49 2012 [20774] warn: prefork: select returned error on server filehandle: My server: Debian 6.0.4 SpamAssassin version 3.3.2 running on Perl version 5.10.1 Can you help me? Thanks Leonardo -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
Problem afther sa-update
Hi all I have a problem on spamassassin afther sa-update The server download the update, it reload the service and the child process wasn't correctly killed and the father process go on zombie state. Message on spamd log: Thu Jun 14 08:57:46 2012 [20774] info: spamd: server hit by SIGHUP, restarting Thu Jun 14 08:57:46 2012 [20774] info: spamd: child [9228] killed successfully: interrupted, signal 2 (0002) Thu Jun 14 08:58:49 2012 [20774] warn: Use of uninitialized value $selerr in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line 332. Thu Jun 14 08:58:49 2012 [20774] warn: prefork: select returned error on server filehandle: My server: Debian 6.0.4 SpamAssassin version 3.3.2 running on Perl version 5.10.1 Can you help me? Thanks Leonardo -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
