On 09/28/2012 08:02 AM, John Hinton wrote:
On 9/28/2012 8:41 AM, Nikolaos Milas wrote:
On 28/9/2012 12:08 μμ, Nikolaos Milas wrote:
# tail -f /var/log/sa-update.log
./sa-update: line 12: 10: command not found
It seems that this output is left from an older run (and I don't know
how it came up).
In all recent runs, it seems there is no output at all.
When I run simply "/usr/bin/sa-update -D", everything seems to run
smoothly.
So, I would guess something is wrong in
/usr/share/spamassassin/sa-update.cron which does not allow proper
updates.
Nick
I had an issue where the server contacted was not responding last
week. I was getting failed cronjob emails. It went away somewhere in
the last several days. Sorry to not have specific times, dates and
server name. Maybe you are seeing the residual from this?
I just had this yesterday:
http: GEThttp://daryl.dostech.ca/sa-update/asf/1391368.tar.gz request failed: 404 Not Found: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head>
<title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /sa-update/asf/1391368.tar.gz was not found on this
server.</p> <hr> <address>Apache/2.2.6 (Fedora) Server at daryl.dostech.ca Port 80</address> </body></html>
But I think this is a different issue.
Could you just set up your own cron job to run sa-update? I'm not sure
of the typical configuration on CentOS but on FreeBSD I set up a script
to run weekly (your path information will differ; test with the debug
first).:
#!/bin/sh
PATH=/usr/local/libexec/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
# Debug:
#/usr/local/bin/sa-update -D
/usr/local/bin/sa-update
