I finally got around to installing 2.60 today in my system, running it with
amavisd-new (which I also bumped up to the latest, 20030616.
I'm very happy that the bayes opportunistic expiration is now configurable
with the bayes_auto_expire option.
However, there seems to be some other contention issue. What I'm seeing is
the SA calls timing out in the BayesStore.pm and UnixLocker.pm modules:
Oct 15 12:12:52 spaminator amavis[692]: (00692-09) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/BayesStore.pm line
434\n\trequire 8 called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/BayesStore.pm line
434\n\tMail::SpamAssassin::BayesStore::untie_db('Mail::SpamAssassin::BayesSt
ore=HASH(0x9227e38)', 'Mail::SpamAssassin::BayesStore=HASH(0x9227e38)',
'Mail::SpamAssassin::BayesStore=HASH(0x9227e38)',
'Mail::SpamAssassin::BayesStore=HASH(0x9227e38)') called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/BayesStore.pm line
1075\n\tMail::SpamAssassin::BayesStore::sync_journal('Mail::SpamAssassin::Ba
yesStore=HASH(0x9227e38)', undef) called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/Bayes.pm line
856\n\tMail::SpamAssassin::Bayes::sync('Mail::SpamAssassin::Bayes=HASH(0x951
8598)', 1, 0) called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/Bayes.pm line
1104\n\tMail::SpamAssassin::Bayes::opportunistic_calls('Mail::SpamAssassin::
Bayes=HASH(0x9518598)') cal...
Oct 15 12:25:16 spaminator amavis[1871]: (01871-01) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/UnixLocker.pm line
58\n\tMail::SpamAssassin::UnixLocker::safe_lock('Mail::SpamAssassin::UnixLoc
ker=HASH(0x929b5e4)', '/var/amavis/bayes', 10) called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/BayesStore.pm line
224\n\tMail::SpamAssassin::BayesStore::tie_db_writable('Mail::SpamAssassin::
BayesStore=HASH(0x929b704)') called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/Bayes.pm line
628\n\trequire 8 called at
/usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/Bayes.pm line
621\n\tMail::SpamAssassin::Bayes::learn('Mail::SpamAssassin::Bayes=HASH(0x95
8baa0)', 0, 'Mail::SpamAssassin::NoMailAudit=HASH(0xa0f60c0)', undef) called
at /usr/lib/perl5/site_perl/5.6.0/Mail/SpamAssassin/PerMsgLearner.pm line
110\n\tMail::SpamAssassin::PerMsgLearner::learn_ham('Mail::SpamAssassin::Per
MsgLearner=HASH(0xa1e5ca0)', undef) cal...
Anyone else seen this? Is there any other expiration contention issue we
should be aware of with 2.60? I see there is a bayes_journal_max_size
option. I tried setting this to 0 about an hour ago and I've not seen any
more "SA TIMED OUT" entries in the log.
One other possible issue is that I kept my old bayes DB - I did an expire
first, then upgraded to 2.60, and then restarted amavisd. Perhaps some cruft
in there?
johnS
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
