spamassassin-sysadmins mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Jones <da...@apache.org>
Subject Re: [Bug 7566] "SHA1 verification failed" for sa-update.razx.cloud since 1-2 weeks
Date Mon, 19 Mar 2018 20:56:34 GMT
On 03/19/2018 02:50 PM, Dave Warren wrote:
> 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.
> 

I enjoy this kind of scripting challenge so I may do this anyway just so 
we know if there are sa-update logs with errors from bad sha1 mismatches.

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

Done.

> 
> 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 run my cron jobs every 10 minutes with a static sleep offset.

>>> I see "MIRROR.CHECK" being updated at 03:18, 04:21, 05:23, 06:18, etc)
>>> confirming rsync was running.
>>>

Yes that is my hourly mirror check script that emails to this list.

>>>
>>> 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
>>>

These 3 files making up a ruleset should be created twice a day 
currently and be immutable.

>>> 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?
>>>

They should not be changing since we make the sha1 file only once at the 
same time the .tar.gz is created.

--
Dave Jones

Mime
View raw message