You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Mika A <mi...@kyamk.fi> on 2004/07/03 19:50:21 UTC
Unable to expire
Joop,
I'm having problems expiring my bayes database. After reading the
sa-learn manual I think it's because the 'newest atime' is way off
for some reason:
0.000 0 2 0 non-token data: bayes db version
0.000 0 29578 0 non-token data: nspam
0.000 0 2682 0 non-token data: nham
0.000 0 907660 0 non-token data: ntokens
0.000 0 1010609624 0 non-token data: oldest atime
0.000 0 1213413657 0 non-token data: newest atime
0.000 0 1088875434 0 non-token data: last journal sync atime
0.000 0 1088872001 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
oldest atime: Wed Jan 9 22:53:44 2002
newest atime: Sat Jun 14 06:20:57 2008
And that probably causes the expiry process to fail:
man sa-learn:
"Starting at 12hrs, calculate whether or not the token would be
expired (based on the difference between the token's atime
and the db's newest token atime)"
debug: bayes: expiry check keep size, 75% of max: 187500
debug: bayes: token count: 907772, final goal reduction size: 720272
debug: bayes: First pass? Current: 1088876391, Last: 1088872001, atime: 0, count: 0, newdelta: 0, ratio: 0
debug: bayes: Can't use estimation method for expiry, something fishy, calculating optimal atime delta (first pass)
debug: bayes: atime token reduction
debug: bayes: ======== ===============
debug: bayes: 43200 907663
debug: bayes: 86400 907663
debug: bayes: 172800 907663
debug: bayes: 345600 907663
debug: bayes: 691200 907663
debug: bayes: 1382400 907663
debug: bayes: 2764800 907663
debug: bayes: 5529600 907663
debug: bayes: 11059200 907663
debug: bayes: 22118400 907663
debug: bayes: couldn't find a good delta atime, need more token difference, skipping expire.
Now is there any way of "fixing" the newest atime into something
more close to reality? Or am I "out-of-luck" and I have to clean the
database and start fresh?
Thanks!
--
Mika Aleksandroff, Kymenlaakson AMK
_________________________________________________________
Best intentions are fraught with disappointments - Gil Grissom
Re: Unable to expire
Posted by "Jack L. Stone" <ja...@sage-american.com>.
At 08:50 PM 7.3.2004 +0300, Mika A wrote:
>Joop,
>
>I'm having problems expiring my bayes database. After reading the
>sa-learn manual I think it's because the 'newest atime' is way off
>for some reason:
>
>Now is there any way of "fixing" the newest atime into something
>more close to reality? Or am I "out-of-luck" and I have to clean the
>database and start fresh?
>
>Thanks!
>--
>Mika Aleksandroff, Kymenlaakson AMK
Seems that a clean-out/start-over is the best way as I have the same troube
even though I've tried to have cron keep it cleaned on a regular basis.
Also, as another post just said, it's probably a good idea anyway as the DB
will become less effective over time....
HTH.
Best regards,
Jack L. Stone,
Administrator
Sage American
http://www.sage-american.com
jacks@sage-american.com