On Mon, Jun 22, 2015 at 9:45 PM, Michael B Allen <iop...@gmail.com> wrote:
> and after running sa-learn again (as root) on ham, my db is now broken:
>
> [root@www .spamassassin]# sa-learn --dump magic
> bayes: bayes db version 0 is not able to be used, aborting! at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/BayesStore/DBM.pm line
> 208.
> bayes: bayes db version 0 is not able to be used, aborting! at
> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/BayesStore/DBM.pm line
> 208.
> ERROR: Bayes dump returned an error, please re-run with -D for more 
> information

Well now the DB is no longer broken and I didn't do anything. I guess
spamassassin ran and detected the broken DB and rebuilt it?

[root@www .spamassassin]# ls -la
total 9288
drwx------ 2 spamd spamd     4096 Jun 22 21:46 .
drwx------ 3 spamd spamd     4096 Jun  7 00:41 ..
-rw------- 1 spamd spamd     2280 Jun 22 21:46 bayes_journal
-rw------- 1 spamd spamd  1306624 Jun 22 21:38 bayes_seen
-rw------- 1 spamd spamd 10485760 Jun 22 21:38 bayes_toks
-rw-r--r-- 1 spamd spamd     1869 Jun  7 00:41 user_prefs
[root@www .spamassassin]# sa-learn --dump magic
0.000          0          3          0  non-token data: bayes db version
0.000          0        378          0  non-token data: nspam
0.000          0      10821          0  non-token data: nham
0.000          0     413216          0  non-token data: ntokens
0.000          0 1150469108          0  non-token data: oldest atime
0.000          0 1435023513          0  non-token data: newest atime
0.000          0 1435023514          0  non-token data: last journal sync atime
0.000          0 1435023525          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

Weird.

But now I am seeing:

X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=unavailable
    version=3.4.0

I have restarted spamd with systemctrl {stop,start} spamassassin.
Hopefully it was just a transient issue.

Mike

Reply via email to