We had a server go crazy last night and reset its date into August of
2277. In any case, we've resolved that, but now I can't get bayes to
expire.
After the clocks was correctly set, I deleted all tokens that had a
lastupdate in the future, and also removed similar bayes_seen rows. I
then reset the the token count in bayes_vars to the correct value.
When I try to run sa-learn --force-expire, nothing gets expired and the
token list keeps growing. Will this get better on its own or do I need
to intervene?
[14256] dbg: bayes: using username: root
[14256] dbg: bayes: database connection established
[14256] dbg: bayes: found bayes db version 3
[14256] dbg: bayes: Using userid: 1
[14256] dbg: config: score set 3 chosen.
[14256] dbg: learn: initializing learner
[14256] dbg: bayes: bayes journal sync starting
[14256] dbg: bayes: bayes journal sync completed
[14256] dbg: bayes: expiry starting
[14256] dbg: bayes: expiry check keep size, 0.75 * max: 112500
[14256] dbg: bayes: token count: 443162, final goal reduction size: 330662
[14256] dbg: bayes: first pass? current: 1201117198, Last: 1201117194,
atime: 43200, count: 1231, newdelta: 160, ratio: 268.612510154346,
period: 43200
[14256] dbg: bayes: can't use estimation method for expiry, unexpected
result, calculating optimal atime delta (first pass)
[14256] dbg: bayes: expiry max exponent: 9
[14256] dbg: bayes: atime token reduction
[14256] dbg: bayes: ======== ===============
[14256] dbg: bayes: 43200 528
[14256] dbg: bayes: 86400 0
[14256] dbg: bayes: 172800 0
[14256] dbg: bayes: 345600 0
[14256] dbg: bayes: 691200 0
[14256] dbg: bayes: 1382400 0
[14256] dbg: bayes: 2764800 0
[14256] dbg: bayes: 5529600 0
[14256] dbg: bayes: 11059200 0
[14256] dbg: bayes: 22118400 0
[14256] dbg: bayes: couldn't find a good delta atime, need more token
difference, skipping expire
[14256] dbg: bayes: expiry completed
