Since upgrading to 3.1.5, I get this when trying to use sa-learn:
# sa-learn --showdots --spam --mbx spam
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
archive-iterator: unable to open spam.spam: No such file or directory
Learned tokens from 0 message(s) (0 message(s) examined)
#
Any ideas?
Al.
On Fri, 8 Sep 2006, Bo Mellberg wrote:
Theo Van Dinter skrev:
On Thu, Sep 07, 2006 at 11:27:36AM +0200, Bo Mellberg wrote:
max:/#sa-learn -D --sync
which would upgrade the db from version 0 to version 2.
FWIW, the upgrade occurs anytime a DB write is attempted, --sync just
forces a write.
OK. Got it.
[25567] dbg: bayes: found bayes db version 0
[25567] dbg: bayes: detected bayes db format 0, upgrading
[25567] dbg: bayes: upgrading database format from v0 to v2
[25567] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[25567] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[25567] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[25567] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
The last row just keeps repeating itself until I ctrl-C out of it.
Nothing seems crazy so far -- the upgrade may take a long time if there
are a lot of tokens, so SA refreshes the lock periodically so it doesn't
loose it.
You were perfectly right! I waited some more and it actually finished:
[29404] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[29404] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[29404] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[29404] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[29404] dbg: bayes: upgraded database format from v2 to v3 in 89 seconds
[29404] dbg: locker: refresh_lock: refresh /root/.spamassassin/bayes.lock
[29404] dbg: bayes: expiry completed
[29404] dbg: bayes: untie-ing
[29404] dbg: bayes: untie-ing db_toks
[29404] dbg: bayes: untie-ing db_seen
[29404] dbg: bayes: files locked, now unlocking lock
[29404] dbg: locker: safe_unlock: unlink /root/.spamassassin/bayes.lock
What does "sa-learn --dump magic" say?
Well, before it didn't say anything, just complained about DB version 0, but
now it gives me:
max:~# sa-learn --dump magic
0.000 0 3 0 non-token data: bayes db version
0.000 0 0 0 non-token data: nspam
0.000 0 0 0 non-token data: nham
0.000 0 0 0 non-token data: ntokens
0.000 0 1157694555 0 non-token data: oldest atime
0.000 0 1157694555 0 non-token data: newest atime
0.000 0 1157694555 0 non-token data: last journal sync
atime
0.000 0 1157694555 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
So I guess I'm good. Thanks a bunch!
/Bo
