> On Dec 10, 2020, at 9:07 AM, Andrew C Aitchison <and...@aitchison.me.uk> 
> wrote:
> 
> On Thu, 10 Dec 2020, Joel Esler (jesler) via clamav-users wrote:
> 
>>> <snip>
>>> 
>> 
>> By “unable to resolve” Micah means: “There’s nothing more we can do
>> to solve the problem”.
>> 
>> When we generate a new cvd/cld, etc, we push it to our local
>> mirrors.  We then force Cloudflare to fetch the files through
>> purging the cache for the files updated, and then requesting them
>> through cloudflare (which causes the CF PoP (Point of Presence) to
>> fetch the file from our mirror). Then we update the TXT record in
>> DNS.
> 
> Would you be able to request them from multiple cloudflare PoPs
> before updating the DNS record ?
> Not necessarily waiting for the update, but making the request.

Possibly.  But only in places around the world where we have a datacenter we 
can do it from, for obvious reasons.

> 
>> So, there are occasions where one PoP from Cloudflare is behind and
>> hasn’t yet fetched the file from the other PoP or from our mirror
>> directly.  This might be the case that you’re the first one that’s
>> asked for it from your PoP location in the world, or its just not
>> caught up yet.  Waiting a bit ensures that the PoP will fetch the
>> file, and when you try again, it’s there (as you can see).
>> 
>> I think the way to fix this is, freshclam, if it receives an “I’m
>> behind” error from the PoP, to do a sleep for awhile and then try
>> again.  If the second attempt still fails then give the error to the
>> user.
> 
> Would it be sensible for freshclam to update the file when a newer
> version is available, even if it is not the newest ?

Not sure what you mean here?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to