Can you turn on debugging and perhaps add it to retry again? I am
trying to figure out if it is one server with an issue.
On 1/10/2018 9:25 AM, Dale Blount wrote:
I get them randomly starting a few months back. My cronjob is set for
4:40am Eastern. Normally it won't fail two days in a row.
My cron script looks like this:
/usr/bin/vendor_perl/sa-update --gpgkey 6C6191E3 --channel
updates.spamassassin.org
RET=$?
if [ "$RET" -eq 0 ]; then
/usr/bin/vendor_perl/sa-compile && systemctl restart spamassassin
fi
On 01/10/2018 09:09 AM, Kevin A. McGrail wrote:
Anyone having issues with Sha1 failures on their machines on sa-updates?
Anyone familiar with sa-update.cron so we can try and get more data
on this bug below?
-------- Forwarded Message --------
Subject: [Bug 7331] channel: SHA1 verification failed, channel failed
Date: Tue, 09 Jan 2018 15:05:37 +0000
From: bugzilla-dae...@issues.apache.org
To: kmcgr...@apache.org
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7331
--- Comment #5 from Jonathan Kamens<j...@kamens.us> ---
(In reply to Kevin A. McGrail from comment #4)
> Please add more logs and if you can, try manually downloading the files.
I'm getting the error from sa-update.cron, so (a) I'm not around when it
happens in the middle of the night to retry it immediately, and (b) I have no
idea where, if anywhere, the logs from sa-update.cron are captured.
If you can advise me how to configure or modify the cron job so that it
captures logs, I will be glad to follow your advice to collect additional
information.
> My big question is does a subsequent run fix the issue? Is there a specific
> mirror that might be having the issue?
When I get the error overnight and then rerun the update during the day when I
notice it, it usually works the second time.
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
