On Tue, 16 Nov 2010, Francesco Acchiappati wrote:
Il 16/11/2010 15:11, John Hardin ha scritto:
I'd suggest the most likely problem is sa-compile is failing for some
reason. Try running it interactively.
You could run this:
bash -x /etc/cron.daily/spamassassin 2>&1 | tee /tmp/log.txt
As you suggested here is the output
# bash -x /etc/cron.daily/spamassassin 2>&1 | tee /tmp/log.txt
+ set -e
+ CRON=0
+ test -f /etc/default/spamassassin
+ . /etc/default/spamassassin
++ ENABLED=1
++ OPTIONS='-q -x -u tomcat4'
++ PIDFILE=/var/run/spamd.pid
++ NICE='--nicelevel 15'
++ CRON=1
+ test -x /usr/bin/sa-update
+ test -x /etc/init.d/spamassassin
+ '[' 1 = 0 ']'
+ RANGE=3600
++ od -vAn -N2 -tu4
+ number=' 62039'
++ expr 62039 % 3600
+ number=839
+ sleep 839
+ umask 022
+ sa-update
+ exit 0
Heh. Okay, that looks even more like sa-compile is failing for some
reason. Unfortunately you're up-to-date so it's not getting to that part
of the script.
You'd have to shut down SA, delete the last update script, and run this
again, which would be fairly intrusive. Instead, you may want to stick
some "echo" statements into the script to log the progress, or put "set
-x" at the top so that it generates output similar to the above in the
message that cron mails to root.
You also might want to run sa-compile manually and see what happens.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Ignorance doesn't make stuff not exist. -- Bucky Katt
-----------------------------------------------------------------------
31 days until TRON Legacy
