Hi,
I'm updating SA & exploring/cleaning Bayes DBs on a slighty 'dusty' box.
after update to latest SA 32x-branch, --lint is OK.
but, currently, i get:
sa-learn --force-expire -D
...
[19416] dbg: bayes: found bayes db version 3
[19416] dbg: bayes: opportunistic call attempt skipped, found fresh
running expire magic token
[19416] dbg: config: score set 3 chosen.
[19416] dbg: learn: initializing learner
[19416] dbg: bayes: bayes journal sync starting
[19416] dbg: bayes: bayes journal sync completed
[19416] dbg: bayes: expiry starting
[19416] dbg: locker: safe_lock: created
/etc/sa/local/.spamassassin/bayes.mutex
[19416] dbg: locker: safe_lock: trying to get lock on
/etc/sa/local/.spamassassin/bayes with 300 timeout
[19416] dbg: locker: safe_lock: link to
/etc/sa/local/.spamassassin/bayes.mutex: link ok
[19416] dbg: bayes: tie-ing to DB file R/W
/etc/sa/local/.spamassassin/bayes_toks
[19416] dbg: bayes: tie-ing to DB file R/W
/etc/sa/local/.spamassassin/bayes_seen
[19416] dbg: bayes: found bayes db version 3
[19416] dbg: locker: refresh_lock: refresh
/etc/sa/local/.spamassassin/bayes.mutex
[19416] dbg: bayes: expiry check keep size, 0.75 * max: 112500
[19416] dbg: bayes: token count: 218650, final goal reduction size:
106150
[19416] dbg: bayes: first pass? current: 1190215099, Last:
1110223381, atime: 1261902, count: 28215, newdelta: 335417, ratio:
3.76218323586745, period: 43200
[19416] dbg: bayes: can't use estimation method for expiry,
unexpected result, calculating optimal atime delta (first pass)
[19416] dbg: bayes: expiry max exponent: 9
where it just 'sits' for awhile -- no errors in logs -- and,
eventually, 'releases' and completes without error.
this only seems to happen an unquantified "some of the time" ...
sometimes (as moments ago) repeating the process results in no such
hand/delay.
fyi,
grep -i bayes local.cf
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1
bayes_min_ham_num 200
bayes_min_spam_num 200
bayes_learn_during_report 1
bayes_use_hapaxes 1
bayes_journal_max_size 102400 # in bytes
bayes_expiry_max_db_size 150000 # of tokens
bayes_auto_expire 1
bayes_learn_to_journal 1
bayes_path /etc/sa/local/.spamassassin/bayes
bayes_auto_learn_threshold_nonspam 1.0
bayes_auto_learn_threshold_spam 6.0
and,
cd /etc/sa/.spamassassin
ls -al
total 36024
drwxrwxr-x 10 sa sa 340 2007-09-19 08:22 .
drwxrwxr-x 39 sa sa 1326 2007-09-19 06:59 ..
-rw-rw---- 1 sa sa 90112 2007-09-19 08:23 auto-whitelist
-rw-rw---- 1 sa sa 10244096 2007-06-28 07:09 auto-whitelist-old
-rw-rw---- 1 sa sa 6 2007-09-19 08:23 auto-whitelist.mutex
-rw-rw---- 1 sa sa 30 2007-09-19 08:21 bayes.mutex
-rw------- 1 root sa 816 2007-09-19 08:22 bayes_journal
-rw-rw---- 1 sa sa 20570112 2007-09-19 07:30 bayes_seen
-rw-rw---- 1 sa sa 5488640 2007-09-19 08:21 bayes_toks
i had NOT noticed this before on this box ... not clear if it's the
build or my local.cf's bayes-related settings. or, perms, maybe?
i've found some old thread references to
"[19416] dbg: bayes: can't use estimation method for expiry, unexpected
result, calculating optimal atime delta (first pass)"
but not yet a resolution ... (still loooking!)
hints?
thanks.
