spamassassin-sysadmins mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Warren ...@thedave.ca>
Subject Re: [Bug 7566] "SHA1 verification failed" for sa-update.razx.cloud since 1-2 weeks
Date Mon, 19 Mar 2018 19:50:15 GMT
I'm going to keep a close eye on it for the next few days manually, and 
then decide if adding automated validation is worthwhile or not.

Could you (whoever is responsible) add me back to the mirrors list?


On 2018-03-19 13:36, Kevin A. McGrail wrote:
> I would guess you caught it mid copy and it arose because of the caching.
> Just a guess but glad we know what's going on.
> 
> On Mon, Mar 19, 2018, 15:09 Dave Warren <dw@thedave.ca> wrote:
> 
>> Howdy. I'm on this list.
>>
>> Okay, so this is a bit odd, it looks like the file 1827131.tar.gz was
>> actually modified by rsync many hours after the initial write:
>>
>> Date: Sun, 18 Mar 2018 02:36:30 -0600 (MDT)
>> .d..t...... ./
>>   >f+++++++++ 1827131.tar.gz
>>   >f+++++++++ 1827131.tar.gz.asc
>>   >f+++++++++ 1827131.tar.gz.sha1
>>
>> My cron runs every 5 minutes (with up to 220 seconds variability). I see
>> "MIRROR.CHECK" being updated at 03:18, 04:21, 05:23, 06:18, etc)
>> confirming rsync was running.
>>
>>
>> 1827131.tar.gz is modified just over 18 hours later:
>>
>> Date: Sun, 18 Mar 2018 20:47:39 -0600 (MDT)
>>   >f.st...... 1827131.tar.gz
>>   >f..t...... 1827131.tar.gz.asc
>>   >f.st...... 1827131.tar.gz.sha1
>>
>> I was under the impression that the *.tar.gz* files were immutable, but
>> looking through my rsync logs, this is definitely not the case, I see
>> the files being created and later updated nearly daily (although not
>> every day, March 8th I see 1826189.tar.gz was created and never
>> modified), the only reference to it is here:
>>
>> 8 Mar 2018 19:46:40 -0700 (MST)
>> .d..t...... ./
>>   >f+++++++++ 1826189.tar.gz
>>   >f+++++++++ 1826189.tar.gz.asc
>>   >f+++++++++ 1826189.tar.gz.sha1
>>
>>
>> Due to my belief in the immutable nature of these files, the files were
>> being cached without verifying whether the on-disk source had changed.
>> For the moment, I will cache less aggressively which should resolve the
>> problem.
>>
>>
>> Can anyone confirm why the files are being modified? Is this
>> intentional/expected?
>>
>>
>>
>>
>> On 2018-03-19 07:52, Dave Jones wrote:
>>> I found an email address in the SA archives from 2013.  Hopefully this
>>> makes it to him.
>>>
>>> On 03/19/2018 08:33 AM, Dave Jones wrote:
>>>> Is Dave Warren on this list?  If no response, does anyone have an old
>>>> email with his contact info so I can ask him how his rsync's are setup?
>>>>
>>>> Dave
>>>>
>>>> On 03/19/2018 08:26 AM, bugzilla-daemon@bugzilla.spamassassin.org
>> wrote:
>>>>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7566
>>>>>
>>>>> Dave Jones <davej@apache.org> changed:
>>>>>
>>>>>              What    |Removed                     |Added
>>>>>
>> ----------------------------------------------------------------------------
>>>>>
>>>>>                    CC|                            |davej@apache.org
>>>>>
>>>>> --- Comment #2 from Dave Jones <davej@apache.org> ---
>>>>> I guess I can add logic to our hourly script to check sha1 values on
>>>>> the latest
>>>>> tar.gz to catch rsync'ing issues.
>>>>>
>>>>
>>>
>>
>>
> 


Mime
View raw message