As a follow-up to my own post, since upgrading to SA 3.0.1, I am also seeing: ===== debug: open of AWL file failed: lock: 6994 cannot create lockfile /var/amavis/.spamassassin/auto-whitelist.mutex: Permission denied debug: bayes: no dbs present, cannot tie DB R/O: /var/amavis/.spamassassin/bayes_toks debug: auto-learning failed: lock: 6994 cannot create lockfile /var/amavis/.spamassassin/bayes.mutex: Permission denied =====
In local.cf I have "bayes_file_mode 777". ls -l /var/amavis/.spamassassin/ total 21348 -rw-rw-rw- 1 amavis amavis 10366976 Oct 23 11:41 auto-whitelist -rw-rw-rw- 1 amavis amavis 6 Oct 23 11:41 auto-whitelist.mutex -rw-rw-rw- 1 amavis amavis 1476 Oct 23 12:37 bayes.mutex -rw-rw-rw- 1 amavis amavis 10498048 Oct 23 12:37 bayes_seen -rw-rw-rw- 1 amavis amavis 5517312 Oct 23 12:37 bayes_toks However, /usr/bin/sa-learn --dump magic -D looks okay (relevant snippets): ===== debug: SpamAssassin version 3.0.1 [...] debug: bayes: 7301 tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_toks debug: bayes: 7301 tie-ing to DB file R/O /var/amavis/.spamassassin/bayes_seen debug: bayes: found bayes db version 3 debug: Score set 2 chosen. 0.000 0 3 0 non-token data: bayes db version 0.000 0 214770 0 non-token data: nspam 0.000 0 84960 0 non-token data: nham 0.000 0 156069 0 non-token data: ntokens 0.000 0 1098484588 0 non-token data: oldest atime 0.000 0 1098556914 0 non-token data: newest atime 0.000 0 1098559462 0 non-token data: last journal sync atime 0.000 0 1098560258 0 non-token data: last expiry atime 0.000 0 59178 0 non-token data: last expire atime delta 0.000 0 0 0 non-token data: last expire reduction count debug: bayes: 7301 untie-ing debug: bayes: 7301 untie-ing db_toks debug: bayes: 7301 untie-ing db_seen ===== So what's up with all of this? Looks like SA bayes and awl are both hosed with this latest release. FYI, I spawn SA via amavisd-new. Bill ----- Original Message ----- From: "Bill Landry" <[EMAIL PROTECTED]> To: <users@SpamAssassin.apache.org> Sent: Saturday, October 23, 2004 10:56 AM Subject: Bayes sa-learn change in SA 3.0.1? > I have "bayes_auto_expire 0" in my local.cf and instead run > "sa-learn --force-expire" via an hourly cron job. With SA 3.0.0 I was see > the following results in my hourly cron results e-mails: > ===== > synced Bayes databases from journal in 3 seconds: 3677 unique entries (3714 > total entries) > expired old Bayes database entries in 83 seconds > 129678 entries kept, 10414 deleted > token frequency: 1-occurence tokens: 55.30% > token frequency: less than 8 occurrences: 26.17% > ===== > > Since upgrading to SA 3.0.1 last night, I am now only seeing the following > in my hourly cron results e-mails: > ===== > synced Bayes databases from journal in 3 seconds: 3268 unique entries (3478 > total entries) > ===== > > I manually ran "sa-learn --force-expire -D" to see what was going on, and am > seeing the following lines in my debug output: > ===== > debug: bayes: Can't use estimation method for expiry, something fishy, > calculating optimal atime delta (first pass) > debug: bayes: couldn't find a good delta atime, need more token difference, > skipping expire. > ===== > > Is this new behavior to be expected now with SA 3.0.1? > > Bill >
