I found an abort message in spamassassin (bayes related). Does this look bad? Has my bayes db grown too large to expire? Should I clear it and start over? Any thoughts would be most helpful. Thanks!<br><br>[root@mx spamassassin]# spamassassin -D --lint
<br><snip><br>[8615] dbg: bayes: DB journal sync: last sync: 1182387243<br>[8615] dbg: bayes: corpus size: nspam = 41590, nham = 136390<br>[8615] dbg: bayes: score = 0.613357629956347<br>[8615] dbg: bayes: DB expiry: tokens in DB: 316397, Expiry max size: 150000, Oldest atime: 1176182136, Newest atime: 1182386879, Last expire: 1176225633, Current time: 1182389157
<br>[8615] dbg: bayes: opportunistic call found expiry due<br>[8615] dbg: bayes: bayes journal sync starting<br>[8615] dbg: locker: safe_lock: created /etc/MailScanner/bayes/bayes.mutex<br>[8615] dbg: locker: safe_lock: trying to get lock on /etc/MailScanner/bayes/bayes with 10 timeout
<br>[8615] dbg: locker: safe_lock: link to /etc/MailScanner/bayes/bayes.mutex: link ok<br>[8615] dbg: bayes: tie-ing to DB file R/W /etc/MailScanner/bayes/bayes_toks<br>[8615] dbg: bayes: tie-ing to DB file R/W /etc/MailScanner/bayes/bayes_seen
<br>[8615] dbg: bayes: found bayes db version 3<br>[8615] dbg: locker: refresh_lock: refresh /etc/MailScanner/bayes/bayes.mutex<br>[8615] dbg: bayes: synced databases from journal in 0 seconds: 370 unique entries (400 total entries)
<br>[8615] dbg: bayes: bayes journal sync completed<br>[8615] dbg: bayes: expiry starting<br>[8615] dbg: locker: refresh_lock: refresh /etc/MailScanner/bayes/bayes.mutex<br>[8615] dbg: locker: refresh_lock: refresh /etc/MailScanner/bayes/bayes.mutex
<br>[8615] dbg: bayes: DB expiry: tokens in DB: 316397, Expiry max size: 150000, Oldest atime: 1176182136, Newest atime: 1182387535, Last expire: 1176225633, Current time: 1182389157<br>[8615] dbg: bayes: expiry check keep size,
0.75 * max: 112500<br>[8615] dbg: bayes: token count: 316397, final goal reduction size: 203897<br>[8615] dbg: bayes: first pass? current: 1182389157, Last: 1176225633, atime: 43200, count: 161535, newdelta: 34224, ratio:
1.26224657195035, period: 43200<br>[8615] dbg: bayes: can't use estimation method for expiry, unexpected result, calculating optimal atime delta (first pass)<br>[8615] dbg: bayes: expiry max exponent: 9<br>[8615] dbg: bayes: atime token reduction
<br>[8615] dbg: bayes: ======== ===============<br>[8615] dbg: bayes: 43200 73442<br>[8615] dbg: bayes: 86400 70494<br>[8615] dbg: bayes: 172800 64774<br>[8615] dbg: bayes: 345600 61009<br>[8615] dbg: bayes: 691200 56206<br>
[8615] dbg: bayes: 1382400 48678<br>[8615] dbg: bayes: 2764800 39890<br>[8615] dbg: bayes: 5529600 26596<br>[8615] dbg: bayes: 11059200 0<br>[8615] dbg: bayes: 22118400 0<br>[8615] dbg: bayes: first pass decided on 43200 for atime delta
<br>[8615] dbg: bayes: token expiration would expire too many tokens, aborting<br>[8615] dbg: bayes: untie-ing<br>[8615] dbg: bayes: untie-ing db_toks<br>[8615] dbg: bayes: untie-ing db_seen<br>[8615] dbg: bayes: files locked, now unlocking lock
<br>[8615] dbg: locker: safe_unlock: unlocked /etc/MailScanner/bayes/bayes.mutex<br>[8615] dbg: bayes: expired old bayes database entries in 31 seconds: 316397 entries kept, 0 deleted<br>[8615] dbg: bayes: expiry completed
<br><br>[root@mx spamassassin]# sa-learn --force-expire<br>bayes: synced databases from journal in 0 seconds: 2 unique entries (2 total entries)<br>expired old bayes database entries in 31 seconds<br>316397 entries kept, 0 deleted
<br>token frequency: 1-occurrence tokens: 0.00%<br>token frequency: less than 8 occurrences: 0.00%<br>