• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

/etc/cron.daily/60sa-update tries to download from blog

Dan Mikkelsen

Basic Pleskian
Usually i get the error:
/etc/cron.daily/60sa-update:
[: 9: 0: unexpected operator
[: 14: 0: unexpected operator
/etc/cron.daily/mdadm:
mdadm: No mail address or alert command - not monitoring.
run-parts: /etc/cron.daily/mdadm exited with return code 1

But today it says:
/etc/cron.daily/60sa-update:
http: GET http://daryl.dostech.ca/sa-update/asf/1386514.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/1386514.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>
[: 9: 0: unexpected operator
[: 14: 0: unexpected operator
/etc/cron.daily/mdadm:
mdadm: No mail address or alert command - not monitoring.
run-parts: /etc/cron.daily/mdadm exited with return code 1

The webpage is a blog of some sort.

Maybe I'm just being paranoid, but is this a legit try to download an update or should i be worried :-/
 
I just got the same error.

http: GET http://daryl.dostech.ca/sa-update/asf/1386514.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/1386514.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>

If I go to: http://daryl.dostech.ca/sa-update/asf I see this message.

This site is for the Apache SpamAssassin Project updates using the sa-update command. You will now be redirected to the home page for the open-source Apache SpamAssassin Project.


Looks like the website that the automated sa-update command used to go to now redirects us to the regular spamassassin website. Not sure if the file it was expecting today was just missing, or if spamassassin is changing how things are supposed to work. anyone have any thoughts?
 
We're experiencing this problem too, on two different servers. For us it started 2 days ago. Does anyone know if there will be a micro-update for this?
 
Back
Top