spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gregorie <mar...@gregorie.org>
Subject Re: SHA1 verification failure during sa_update
Date Fri, 18 Jan 2013 13:11:10 GMT
On Fri, 2013-01-18 at 07:02 -0500, Kevin A. McGrail wrote:
> On 1/18/2013 6:24 AM, Martin Gregorie wrote:
> > On Fri, 2013-01-18 at 05:28 -0500, Kevin A. McGrail wrote:
> >> What channels do you update and what version of SpamAssassin?
> >>
> > SA 3.3.2
> > sa-update version svn917659
> >    running on Perl version 5.14.3
> >
> > I'm only using the default rule set.
> > I'm running sa-update without any command line arguments or options.
> 
> I run one of the mirrors and I don't show a sha1 mismatch on the mirror
> 
> cat 1435057.tar.gz.sha1
> 8eaa92bfceb5160debe78afac819e2a5a31c29c0 
> /home/updatesd/tmp/stage/3.4.0/update.tgz
> sha1sum 1435057.tar.gz
> 8eaa92bfceb5160debe78afac819e2a5a31c29c0  1435057.tar.gz
> 
> If you run it again manually what occurs?  Can you run it with -D and 
> trap the output, please?
> 
I edited my cron script (sa_update) to add the -D option to sa-update
and then ran it as "./sa_update 2>&1 | tee sa-diag.txt". File attached.
No update available.

And, of course, this time there was no SHA1 failure: it was obviously a
transient error of some type, and one that I hadn't previously seen.


Martin



Mime
View raw message