Hi, I am using SA 2.60, updated vom 2.55 some weeks ago. I was also using various rc-versions of 2.60.
In local.cf I have no values assigned to the use of the Bayes-db so I am running on default values. When I try to clean up the Bayes db I get this: router:/disk/log # sa-learn -D --force-expire debug: Score set 0 chosen. debug: running in taint mode? yes debug: Running in taint mode, removing unsafe env vars, and resetting PATH debug: PATH included '/sbin', keeping. debug: PATH included '/usr/sbin', keeping. debug: PATH included '/bin', keeping. debug: PATH included '/usr/bin', keeping. debug: PATH included '/usr/local/bin', keeping. debug: PATH included '.', which is not absolute, dropping. debug: Final PATH set to: /sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin debug: using "/usr/local/perl/share/spamassassin" for default rules dir debug: using "/etc/apache/mail/spamassassin/" for site rules dir debug: using "//.spamassassin/user_prefs" for user prefs file debug: bayes: 7059 tie-ing to DB file R/O //.spamassassin/bayes_toks debug: bayes: 7059 tie-ing to DB file R/O //.spamassassin/bayes_seen debug: bayes: found bayes db version 2 debug: Score set 2 chosen. debug: Initialising learner debug: Initialising learner debug: Syncing Bayes journal and expiring old tokens... debug: lock: 7059 created //.spamassassin/bayes.lock.router.7059 debug: lock: 7059 trying to get lock on //.spamassassin/bayes with 0 retries debug: lock: 7059 link to //.spamassassin/bayes.lock: link ok debug: bayes: 7059 tie-ing to DB file R/W //.spamassassin/bayes_toks debug: bayes: 7059 tie-ing to DB file R/W //.spamassassin/bayes_seen debug: bayes: found bayes db version 2 debug: bayes: expiry check keep size, 75% of max: 112500 debug: bayes: token count: 167078, final goal reduction size: 54578 debug: bayes: First pass? Current: 1065966293, Last: 1065965451, atime: 0, count: 0, newdelta: 0, ratio: 0 debug: bayes: something fishy, calculating atime (first pass) debug: bayes: couldn't find a good delta atime, need more token difference, skipping expire. debug: Syncing complete. debug: bayes: 7059 untie-ing debug: bayes: 7059 untie-ing db_toks debug: bayes: 7059 untie-ing db_seen debug: bayes: files locked, now unlocking lock debug: unlock: 7059 unlink //.spamassassin/bayes.lock Looks like the time stamps show no big difference and therefore the expiry process can not figure out which tokens to expire. router:/disk/log # sa-learn --dump 0.000 0 2 0 non-token data: bayes db version 0.000 0 5188 0 non-token data: nspam 0.000 0 1930 0 non-token data: nham 0.000 0 167078 0 non-token data: ntokens 0.000 0 1062456372 0 non-token data: oldest atime 0.000 0 1065965625 0 non-token data: newest atime 0.000 0 1065965715 0 non-token data: last journal sync atime 0.000 0 1065966678 0 non-token data: last expiry atime 0.000 0 0 0 non-token data: last expire atime delta 0.000 0 0 0 non-token data: last expire reduction count This problem is not so important if the expire run would not be running during mail processing. I am getting a timeout and mails (often spam) get through unscanned (Exim 4.12 with Exiscan, not exiscan-acl). Or shall I wait some 16 days longer? SA 2.60 is running since at least 19 days here. Greetings, Bernd ------------------------------------------------------- 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
