Hello,
Recently I found in freshclam.log messages like this:
Can't query daily.25671.105.1.0.6810DA54.ping.clamav.net
that was occured once per day about 11:30 p.m.
Another attempts to update clamav are successfull (before mentioned
message and after) but next day this message is repeat.
I t
Hi there,
On Mon, 23 Dec 2019, Sohin Vyacheslav via clamav-users wrote:
Recently I found in freshclam.log messages like this:
Can't query daily.25671.105.1.0.6810DA54.ping.clamav.net
[...]
I thought that the reason is connection error with IPv6 mirrors
[...]
$ freshclam --list-mirrors
Mirror #1
On Mon, 23 Dec 2019, Sohin Vyacheslav via clamav-users wrote:
> Date: Mon, 23 Dec 2019 11:18:15 +0200
> From: Sohin Vyacheslav via clamav-users
> To: clamav-users@lists.clamav.net
> Cc: Sohin Vyacheslav
> Subject: [clamav-users] messages in freshclam.log
>
> Hello,
>
> Recently I found in fres
23.12.2019 15:37, G.W. Haywood via clamav-users пишет:
Are you sure that you have IPv6 connectivity to the mirrors?
$ ping db.nl.ipv6.clamav.net
PING db.nl.ipv6.clamav.net.cdn.cloudflare.net (104.16.219.84) 56(84)
bytes of data.
64 bytes from 104.16.219.84 (104.16.219.84): icmp_seq=1 ttl=
23.12.2019 15:43, Robert M. Stockmann via clamav-users пишет:
On Mon, 23 Dec 2019, Sohin Vyacheslav via clamav-users wrote:
[hubble:root]:(~)# freshclam --list-mirrors
WARNING: Deprecated option --list-mirrors. Individual mirrors are no longer
tracked, as official signature distribution is no
These don’t exist. All of these addresses simply point at database.clamav.net.
So, it makes no sense to point them to anything else.
Sent from my iPad
> On Dec 23, 2019, at 04:19, Sohin Vyacheslav via clamav-users
> wrote:
>
> DatabaseMirror db.nl.ipv6.clamav.net
> DatabaseMirror db.fr.ip
23.12.2019 16:51, Joel Esler (jesler) пишет:
These don’t exist. All of these addresses simply point at database.clamav.net.
So, it makes no sense to point them to anything else.
Ok, I agree. But what about mentioned message:
Can't query daily.25671.105.1.0.6810DA54.ping.clamav.net
--
Be
This was mentioned here before, and I can't remember what the status was.
For this example:
A dig trace leads to:
ping.clamav.net.86400 IN NS ns1a.clamav.net.
;; BAD (HORIZONTAL) REFERRAL
dig: too many lookups
#dig daily.25671.105.1.0.6810DA54.ping.clamav.net @ns1a.clamav.net
On Mon, 23 Dec 2019 08:04:13 +0100, Alessandro Vesely via clamav-users
stated:
>Perhaps you could try and match From:snopescom-.*@cmail20.com?
Actually, it is the "@cmail20.com" part changes also.
--
Jerry
___
clamav-users mailing list
clamav-user
I think the status is currently “ignore this”.
Sent from my iPad
> On Dec 23, 2019, at 10:52, Eric Tykwinski wrote:
>
> This was mentioned here before, and I can't remember what the status was.
>
> For this example:
> A dig trace leads to:
> ping.clamav.net.86400 IN NS n
This is correct. Please ignore the "Can't query daily. ... .ping.clamav.net".
This message has been removed as of ClamAV 0.102.
-Micah
On 12/23/19, 12:12 PM, "clamav-users on behalf of Joel Esler (jesler) via
clamav-users" wrote:
I think the status is currently “ignore this”.
11 matches
Mail list logo
