I'd run "sh -x /etc/cron.daily/spamassassin"
to see what command in that file failed. I assume it is the sa-compile
command.
I got some more results.
Here are the steps I made:
1. Remove everything from /var/lib/spamassassin
2. Reinstall spamassassin package
3. Recreate /var/lib/spamassassin/compiled directory with
debian-spamd:debian-spamd ownership
4. Run sudo sh -x /etc/cron.daily/spamassassin
Here is the output I collected:
+ CRON=0
+ test -f /etc/default/spamassassin
+ . /etc/default/spamassassin
+ SPAMD_HOME=/run/spamd/
+ OPTIONS=--create-prefs --max-children 5 --helper-home-dir /run/spamd/
--listen /run/spamd/spamd.sock --username debian-spamd -s spamd
--allow-tell --timeout-child=30
+ PIDFILE=/run/spamd/spamd.pid
+ NICE=--nicelevel 15
+ CRON=1
+ test -x /usr/bin/sa-update
+ test -x /etc/init.d/spamassassin
+ command -v gpg
+ [ 1 = 0 ]
+ [ ! -t 0 ]
+ umask 022
+ env -i LANG=en_GB.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
http_proxy= start-stop-daemon --chuid debian-spamd:debian-spamd --start
--exec /usr/bin/sa-update -- --gpghomedir
/var/lib/spamassassin/sa-update-keys
+ env -i LANG=en_GB.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
start-stop-daemon --chuid debian-spamd:debian-spamd --start --exec
/usr/bin/spamassassin -- --lint
+ do_compile
+ [ -x /usr/bin/re2c -a -x /usr/bin/sa-compile ]
+ env -i LANG=en_GB.UTF-8
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
start-stop-daemon --chuid debian-spamd:debian-spamd --start --exec
/usr/bin/sa-compile -- --quiet
chmod: cannot access 'body_0.bs': No such file or directory
make: *** [Makefile:465: body_0.bs] Error 1
command 'make PREFIX=/tmp/.spamassassin11033rJy6vLtmp/ignored
INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.032/3.004006
>>/tmp/.spamassassin11033rJy6vLtmp/log' failed: exit 2
+ runuser -u debian-spamd -- chmod -R go-w,go+rX
/var/lib/spamassassin/compiled
+ reload
+ which invoke-rc.d
+ invoke-rc.d --quiet spamassassin status
+ invoke-rc.d spamassassin reload
+ [ -d /etc/spamassassin/sa-update-hooks.d ]
+ run-parts --lsbsysinit /etc/spamassassin/sa-update-hooks.d
The error in the middle is the one reported daily through the run of the
cron job.
Might there be something wrong with my environment? Else, what could be
wrong/needs checking?
Bernard
