Description of problem: For the past week I have been receiving Cron error e-mails reporting that the sa-update.cron script has failed to download the file. The email looks like this: http: GET http://yerp.org/rules/stage/330918877.tar.gz request failed: 500 read timeout: 500 read timeout channel: could not find working mirror, channel failed I am able to download the file manually with wget. I have been getting this error every day for at least the past week. The e-mail has a timestamp of 4:33 AM. Version-Release number of selected component (if applicable): spamassassin-3.3.0-5.fc12.x86_64 How reproducible: Every night cron runs itself. Actual results: No update downloaded. Expected results: Latest spam update downloaded.
I wonder if yerp.org is getting swamped by folks setting this up as a daily cron with no delay? Perhaps we should add more delay to our cron job. Michael: If you run it at say 8am does it work out ok?
(In reply to comment #1) > > Michael: If you run it at say 8am does it work out ok? Of course, it didn't happen this morning after happening the last week. I will try delaying it a few hours. Thanks.
(In reply to comment #1) > > Michael: If you run it at say 8am does it work out ok? I went the whole week without any cron emails, but I received one today at 8:50am this morning saying the same message about failing to download the update file. http: GET http://yerp.org/rules/stage/330922791.tar.gz request failed: 500 read timeout: 500 read timeout channel: could not find working mirror, channel failed
I should probably completely silence the cron job. These errors are transient, expected and non-fatal.
On second thought I'm having it print an additional message instead. +else + echo "*********************************************************" + echo "* NOTE: The above failure is NOT a bug in spamassassin. *" + echo "* It is an expected and transient error. *" + echo "* https://bugzilla.redhat.com/show_bug.cgi?id=570494 *" + echo "*********************************************************" fi
Updated info message. echo "***************************************************************" echo "NOTE: The above failure is probably NOT a bug in spamassassin." echo "It is likely an expected and transient error where the update echo "source server is down." echo " https://bugzilla.redhat.com/show_bug.cgi?id=570494" echo "Alternatively your configuration may be incorrect in " echo " /etc/mail/spamassassin/channel.d/" echo "***************************************************************"
On second thought that didn't work as expected. Reverted it back to 3.3.0-6 behavior. This is still NOT a spamassassin bug.
(In reply to comment #7) > On second thought that didn't work as expected. Reverted it back to 3.3.0-6 > behavior. I didn't mind the addition of the echo'd comments. The bz link may not be necessary. > This is still NOT a spamassassin bug. Is it? Should the update piece of spamassassin keep trying with another mirror if it fails? From the log output it looks like only one mirror is tried (or is there only one mirror?). I'm using a standard spamassassin install so there should be nothing I changed to affect the configuration of updates.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping