Re: [clamav-users] Freshclam failure - Still ongoing???

[Joel Esler (jesler)]

Al —

Thanks for responding.  I’m going to write an email in a separate thread, so 
that people see it.


--
Joel Esler | Talos: Manager | jes...@cisco.com






On Aug 27, 2017, at 4:36 AM, Al Varnell 
mailto:alvarn...@mac.com>> wrote:

If I recall correctly, I believe Joel said before that they have an internal 
means of monitoring mirrors but had not gotten around to turning it into a 
public facing web page yet.

-Al-
On Aug 27, 2017, at 1:07 AM, Andreas Schulze 
mailto:andreas.schu...@datev.de>> wrote:

Am 25.08.2017 um 22:44 schrieb Joel Esler (jesler):
We are working on ways to not only fix the on going mirror issues, but prevent 
them in the future, as well as bring back the Mirror page on 
ClamAV.net at some point soon.
Joel,

expect a mirror monitoring would make visible that many mirrors are no longer 
up to date.
I could imagine, some db.XY.clamav.net don't have 
current mirrors at all.

Andreas
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

It will fall through to db.local.clamav.net.

dp

On 8/27/17 1:07 AM, Andreas Schulze wrote:

Am 25.08.2017 um 22:44 schrieb Joel Esler (jesler):
We are working on ways to not only fix the on going mirror issues, but 
prevent them in the future, as well as bring back the Mirror page on 
ClamAV.net at some point soon.

Joel,

expect a mirror monitoring would make visible that many mirrors are no longer 
up to date.

I could imagine, some db.XY.clamav.net don't have current mirrors at all.

Andreas
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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



___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Al Varnell]

If I recall correctly, I believe Joel said before that they have an internal 
means of monitoring mirrors but had not gotten around to turning it into a 
public facing web page yet.

-Al-
On Aug 27, 2017, at 1:07 AM, Andreas Schulze  wrote:

> Am 25.08.2017 um 22:44 schrieb Joel Esler (jesler):
>> We are working on ways to not only fix the on going mirror issues, but 
>> prevent them in the future, as well as bring back the Mirror page on 
>> ClamAV.net at some point soon.
> Joel,
> 
> expect a mirror monitoring would make visible that many mirrors are no longer 
> up to date.
> I could imagine, some db.XY.clamav.net don't have current mirrors at all.
> 
> Andreas
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Andreas Schulze]

Am 25.08.2017 um 22:44 schrieb Joel Esler (jesler):

We are working on ways to not only fix the on going mirror issues, but prevent them 
in the future, as well as bring back the Mirror page on 
ClamAV.net at some point soon.

Joel,

expect a mirror monitoring would make visible that many mirrors are no 
longer up to date.

I could imagine, some db.XY.clamav.net don't have current mirrors at all.

Andreas
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Bill Maidment]

Yes, and it still failed.
I'm now switching to UK as others seem to have more success with that (for now).
 
 
-Original message-
> From:Al Varnell 
> Sent: Saturday 26th August 2017 20:49
> To: ClamAV users ML 
> Subject: Re: [clamav-users] Freshclam failure - Still ongoing???
> 
> Did you trash your daily.cld? Joel told us earlier today that those having 
> this issue would need to get rid of it along with mirrors.dat for freshclam 
> to function normally again.
> 
> -Al-
> 
> On Aug 25, 2017, at 11:09 PM, Bill Maidment  wrote:
> 
> > This is getting really serious.
> > I found a mirror that was working on DE, but now that is failing too.
> > 
> > ERROR: getpatch: Can't download daily-23715.cdiff from 195.30.97.3
> > ERROR: Can't download daily.cvd from 195.30.97.3
> > 
> > Is this a virus
> > 
> > 
> > -Original message-
> >> From:Dennis Peterson 
> >> Sent: Saturday 26th August 2017 1:02
> >> To: clamav-users@lists.clamav.net
> >> Subject: Re: [clamav-users] Freshclam failure - Still ongoing???
> >> 
> >> This is abysmal.
> >> 
> >> # freshclam --list-mirrors |grep Success |sort -n -k2
> >> Successes: 0
> >> Successes: 0
> >> Successes: 0
> >> Successes: 0
> >> Successes: 0
> >> Successes: 0
> >> Successes: 0
> >> Successes: 4
> >> Successes: 7
> >> Successes: 8
> >> Successes: 11
> >> Successes: 11
> >> Successes: 19
> >> Successes: 46
> >> Successes: 79
> >> Successes: 81
> >> Successes: 85
> >> Successes: 90
> >> Successes: 176
> >> Successes: 178
> >> Successes: 188
> >> Successes: 215
> >> 
> >> # freshclam --list-mirrors |grep Fail |sort -n -k2
> >> Failures: 0
> >> Failures: 0
> >> Failures: 2
> >> Failures: 4
> >> Failures: 12
> >> Failures: 19
> >> Failures: 21
> >> Failures: 23
> >> Failures: 55
> >> Failures: 90
> >> Failures: 102
> >> Failures: 109
> >> Failures: 110
> >> Failures: 148
> >> Failures: 148
> >> Failures: 160
> >> Failures: 163
> >> Failures: 183
> >> Failures: 274
> >> Failures: 274
> >> Failures: 275
> >> Failures: 275
> >> 
> >> # freshclam --list-mirrors |grep -B2 Fail
> >> IP: 208.72.56.53
> >> Successes: 0
> >> Failures: 275
> >> --
> >> IP: 200.236.31.1
> >> Successes: 81
> >> Failures: 160
> >> --
> >> IP: 64.6.100.177
> >> Successes: 0
> >> Failures: 274
> >> --
> >> ...
> >> 
> >> dp
> >> 
> >> On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
> >>> On it
> >>> 
> >>> Sent from my iPhone
> >>> 
> >> ___
> >> clamav-users mailing list
> >> clamav-users@lists.clamav.net
> >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> >> 
> >> Help us build a comprehensive ClamAV guide:
> >> https://github.com/vrtadmin/clamav-faq
> >> 
> >> http://www.clamav.net/contact.html#ml
> >> 
> >> 
> > ___
> > clamav-users mailing list
> > clamav-users@lists.clamav.net
> > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> > 
> > 
> > Help us build a comprehensive ClamAV guide:
> > https://github.com/vrtadmin/clamav-faq
> > 
> > http://www.clamav.net/contact.html#ml
> 
> -Al-
> -- 
> Al Varnell
> Mountain View, CA
> 
> 
> 
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
> 
> 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

On 8/26/17 10:49 AM, Dennis Peterson wrote:
I grabbed a tld file to use to locate (best effort) all ClamAV mirrors using a 
couple patterns I've discovered. Surely there is a better way but I'm old and 
time is precious.


db.TLD.clamav.net
db.TLD.rr.clamav.net 


Snippage happened.


I should add that just because a site is pingable is no guarantee that it will 
respond to freshclam requests, or have the current version of the signature 
files. It takes time to distribute these files to the mirrors.


dp

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

I grabbed a tld file to use to locate (best effort) all ClamAV mirrors using a 
couple patterns I've discovered. Surely there is a better way but I'm old and 
time is precious.


db.TLD.clamav.net
db.TLD.rr.clamav.net

I used the host command to find every mirror available to this method. That 
returned over 500 hosts but with many IP duplicates. After dedup'ing the list I 
got 144 uniq servers. I pinged that list and got 33 pingable servers world wide. 
I ran that list through geoiplookup and got this list of healthy pingable 
servers sorted by world region.


Many of the unreachable IP's are the result of firewall decisions and don't 
necessarily reflect a failed system.


My intention now is to create a list of fairly local systems and create a DNS RR 
table for my own use. I will track performance using the mirrors.dat file 
(freshclam --list-mirrors). I suggest before anyone removed this file that you 
gather a report using freshclam so that you can monitor your own site 
interactions as the new mirrors.dat file collects data. A little forensics goes 
a long way.


The following list are the only mirrors world wide that I could find and which 
also responded to a ping. It isn't much of a list.


212.71.0.66
GeoIP Country Edition: BE, Belgium
--
46.29.125.16
GeoIP Country Edition: FR, France
--
212.180.1.29
GeoIP Country Edition: FR, France
--
130.133.110.67
GeoIP Country Edition: DE, Germany
--
144.76.28.11
GeoIP Country Edition: DE, Germany
--
212.227.138.145
GeoIP Country Edition: DE, Germany
--
213.133.110.235
GeoIP Country Edition: DE, Germany
--
194.8.197.22
GeoIP Country Edition: DE, Germany
--
195.30.97.3
GeoIP Country Edition: DE, Germany
--
62.27.56.14
GeoIP Country Edition: DE, Germany
--
62.245.181.53
GeoIP Country Edition: DE, Germany
--
5.9.253.237
GeoIP Country Edition: DE, Germany
--
218.189.210.14
GeoIP Country Edition: HK, Hong Kong
--
180.92.182.5
GeoIP Country Edition: HK, Hong Kong
--
90.147.160.69
GeoIP Country Edition: IT, Italy
--
85.254.217.235
GeoIP Country Edition: LV, Latvia
--
196.192.32.38
GeoIP Country Edition: MG, Madagascar
--
128.199.133.36
GeoIP Country Edition: SG, Singapore
--
92.240.244.203
GeoIP Country Edition: SK, Slovakia
--
158.197.16.70
GeoIP Country Edition: SK, Slovakia
--
84.255.209.87
GeoIP Country Edition: SI, Slovenia
--
155.232.191.239
GeoIP Country Edition: ZA, South Africa
--
196.4.160.79
GeoIP Country Edition: ZA, South Africa
--
82.159.137.16
GeoIP Country Edition: ES, Spain
--
82.195.224.39
GeoIP Country Edition: CH, Switzerland
--
130.59.113.36
GeoIP Country Edition: CH, Switzerland
--
178.79.177.182
GeoIP Country Edition: GB, United Kingdom
--
81.91.100.173
GeoIP Country Edition: GB, United Kingdom
--
129.67.1.218
GeoIP Country Edition: GB, United Kingdom
--
204.130.133.50
GeoIP Country Edition: US, United States
--
104.131.196.175
GeoIP Country Edition: US, United States
--
69.12.162.28
GeoIP Country Edition: US, United States
--
69.163.100.14
GeoIP Country Edition: US, United States
--

dp

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Al Varnell]

Did you trash your daily.cld? Joel told us earlier today that those having this 
issue would need to get rid of it along with mirrors.dat for freshclam to 
function normally again.

-Al-

On Aug 25, 2017, at 11:09 PM, Bill Maidment  wrote:

> This is getting really serious.
> I found a mirror that was working on DE, but now that is failing too.
> 
> ERROR: getpatch: Can't download daily-23715.cdiff from 195.30.97.3
> ERROR: Can't download daily.cvd from 195.30.97.3
> 
> Is this a virus
> 
> 
> -Original message-
>> From:Dennis Peterson 
>> Sent: Saturday 26th August 2017 1:02
>> To: clamav-users@lists.clamav.net
>> Subject: Re: [clamav-users] Freshclam failure - Still ongoing???
>> 
>> This is abysmal.
>> 
>> # freshclam --list-mirrors |grep Success |sort -n -k2
>> Successes: 0
>> Successes: 0
>> Successes: 0
>> Successes: 0
>> Successes: 0
>> Successes: 0
>> Successes: 0
>> Successes: 4
>> Successes: 7
>> Successes: 8
>> Successes: 11
>> Successes: 11
>> Successes: 19
>> Successes: 46
>> Successes: 79
>> Successes: 81
>> Successes: 85
>> Successes: 90
>> Successes: 176
>> Successes: 178
>> Successes: 188
>> Successes: 215
>> 
>> # freshclam --list-mirrors |grep Fail |sort -n -k2
>> Failures: 0
>> Failures: 0
>> Failures: 2
>> Failures: 4
>> Failures: 12
>> Failures: 19
>> Failures: 21
>> Failures: 23
>> Failures: 55
>> Failures: 90
>> Failures: 102
>> Failures: 109
>> Failures: 110
>> Failures: 148
>> Failures: 148
>> Failures: 160
>> Failures: 163
>> Failures: 183
>> Failures: 274
>> Failures: 274
>> Failures: 275
>> Failures: 275
>> 
>> # freshclam --list-mirrors |grep -B2 Fail
>> IP: 208.72.56.53
>> Successes: 0
>> Failures: 275
>> --
>> IP: 200.236.31.1
>> Successes: 81
>> Failures: 160
>> --
>> IP: 64.6.100.177
>> Successes: 0
>> Failures: 274
>> --
>> ...
>> 
>> dp
>> 
>> On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
>>> On it
>>> 
>>> Sent from my iPhone
>>> 
>> ___
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>> 
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> 
>> http://www.clamav.net/contact.html#ml
>> 
>> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

-Al-
-- 
Al Varnell
Mountain View, CA




___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Bill Maidment]

This is getting really serious.
I found a mirror that was working on DE, but now that is failing too.

ERROR: getpatch: Can't download daily-23715.cdiff from 195.30.97.3
ERROR: Can't download daily.cvd from 195.30.97.3

Is this a virus

 
-Original message-
> From:Dennis Peterson 
> Sent: Saturday 26th August 2017 1:02
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] Freshclam failure - Still ongoing???
> 
> This is abysmal.
> 
> # freshclam --list-mirrors |grep Success |sort -n -k2
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 4
> Successes: 7
> Successes: 8
> Successes: 11
> Successes: 11
> Successes: 19
> Successes: 46
> Successes: 79
> Successes: 81
> Successes: 85
> Successes: 90
> Successes: 176
> Successes: 178
> Successes: 188
> Successes: 215
> 
> # freshclam --list-mirrors |grep Fail |sort -n -k2
> Failures: 0
> Failures: 0
> Failures: 2
> Failures: 4
> Failures: 12
> Failures: 19
> Failures: 21
> Failures: 23
> Failures: 55
> Failures: 90
> Failures: 102
> Failures: 109
> Failures: 110
> Failures: 148
> Failures: 148
> Failures: 160
> Failures: 163
> Failures: 183
> Failures: 274
> Failures: 274
> Failures: 275
> Failures: 275
> 
> # freshclam --list-mirrors |grep -B2 Fail
> IP: 208.72.56.53
> Successes: 0
> Failures: 275
> --
> IP: 200.236.31.1
> Successes: 81
> Failures: 160
> --
> IP: 64.6.100.177
> Successes: 0
> Failures: 274
> --
> ...
> 
> dp
> 
> On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
> > On it
> >
> > Sent from my iPhone
> >
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
> 
> 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Paul Dean]

Can do, as it looks like AU only has 1 mirror anyway. I'll check the $$ side of 
things to provide it.

Get back to you on this Joel.

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 08:50:05 -0700
Dennis Peterson  wrote:

>Are you not able to create your own mirror?
>
>dp
>
>On 8/25/17 8:48 AM, Paul Dean wrote:
>> Hi,
>>
>> Thanks for the info, but doing this across several groups of servers is not 
>> really suitable. But that said, if there is no viable fix in the next day or 
>> so, then this might be the only solution.
>>
>> Does anyone have a list of confirmed working mirrors?
>>
>> Thanks Joel for getting onto this, let me know if I can help somehow.
>>
>> --
>>
>>
>> Thanks
>>
>> Paul Dean.
>>
>> "Life is not WHAT you make it, it's WHO you have in it..."
>>
>>
>> On Fri, 25 Aug 2017 07:43:08 -0700
>> Dennis Peterson  wrote:
>>  
>>> You don't need ClamAV ppl to help - you have complete control over this 
>>> process. Try this:
>>>
>>> Find a healthy mirror
>>> Put that healthy mirror's IP address in your freshclam.conf file as the 
>>> first definition of DatabaseMirror
>>> Run freshclam manually.
>>>
>>> grep ^DatabaseMirror freshclam.conf
>>>
>>> You should see a host name such as db.de.clamav.net. Use the host or 
>>> nslookup command to expand that to reveal all the round-robin IP addresses. 
>>> It looks like this (as of this moment):
>>>
>>> host db.de.clamav.net
>>>
>>> db.de.clamav.net has address 195.30.97.3
>>> db.de.clamav.net has address 212.227.138.145
>>> db.de.clamav.net has address 213.174.32.130
>>> db.de.clamav.net has address 5.9.253.237
>>> db.de.clamav.net has address 62.27.56.14
>>> db.de.clamav.net has address 62.201.161.84
>>> db.de.clamav.net has address 62.245.181.53
>>> db.de.clamav.net has address 84.39.110.99
>>> db.de.clamav.net has address 88.198.17.100
>>> db.de.clamav.net has address 130.133.110.67
>>> db.de.clamav.net has address 144.76.28.11
>>> db.de.clamav.net has address 178.63.73.246
>>> db.de.clamav.net has address 193.27.49.165
>>>
>>> Ping each of these hosts to see which ones respond. Use geoiplookup or 
>>> similar tool to find which healthy sites are located near you. No point 
>>> trying to poll a site around the world from you. If you don't have a geoip 
>>> tool then notice the response time of each mirror's successful ping. The 
>>> lower the time the better suited it could be for you.
>>>
>>> Choose an IP that looks promising. Put that in your freshclam.conf file and 
>>> run freshclam. For example:
>>>
>>> DatabaseMirror 195.30.97.3
>>>
>>> Remember this is a temporary fix - don't depend on this configuration to 
>>> work in the long run. Undo it when the ClamAV ppl fix the mirrors problem.
>>>
>>> As an aside try some diagnostics - run freshclam manually:
>>> freshclam --list-mirrors
>>>
>>> This will give you a list of mirrors and their health. On the report I see 
>>> some of the mirrors have never responded, others respond about 50% of the 
>>> time. If you see a mirror that is 100% successful you can use that in your 
>>> freshclam.conf file. It would be helpful if the ClamAV ppl would remove the 
>>> bad actors from the DNS records.
>>>
>>> If none of this makes sense then do nothing and wait for the ClamAV ppl. 
>>> Better safe than sorry.
>>>
>>> dp
>>>
>>>
>>>
>>>
>>> On 8/25/17 2:14 AM, Paul Dean wrote:  
 Oh shoot ClamAV ppl, help please...

 --


 Thanks

 Paul Dean.

 "Life is not WHAT you make it, it's WHO you have in it..."


 On Fri, 25 Aug 2017 10:47:23 +0200
 maxal  wrote:  
    hi,  
>
> yes, this is ongoing as there are numerous broken mirrors in different
> country zones out there, eg german zone db.de.clamav.net:
>
> db.de.clamav.net has address 62.201.161.84 -> OK
> db.de.clamav.net has address 195.30.97.3 -> OK
> db.de.clamav.net has address 130.133.110.67 -> OK
> db.de.clamav.net has address 212.227.138.145 -> OK
> db.de.clamav.net has
> address 62.27.56.14 -> OK
> db.de.clamav.net has address 62.245.181.53 ->
> OK
> db.de.clamav.net has address 193.27.49.165 -> OK
> db.de.clamav.net has address 88.198.17.100 -> FAIL
> db.de.clamav.net has address 84.39.110.99 -> FAIL
> db.de.clamav.net has address 144.76.28.11 -> FAIL
> db.de.clamav.net has address 213.174.32.130 -> FAIL
> db.de.clamav.net has address 5.9.253.237 -> FAIL
> db.de.clamav.net has address 178.63.73.246 -> FAIL
>
> regards
> max
>
>
> On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:  
>> Hi,
>>
>> I've checked the lists and nuked the mirror.dat file as suggested,
>> but still getting failure on dling daily-23699.cdiff via freshclam.
>> Also tried via wget, and got a 404 error. So currently I'm stuck on
>> 23698.
>>
>> Also nuked all .cld files and still failed.
>>
>> I've got a few servers/machine

Re: [clamav-users] Freshclam failure - Still ongoing???

[Paul Dean]

Yes, I've seen this as well, and done said delete(even on  my lappy this 
morning to test), but still failing, sadly.

Just odd that all AU servers are "bad". Anyways, I guess this might be a time 
thing, as people see the mirrors that they manage are out of sync, they'll fix 
them.

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 20:44:58 +
"Joel Esler (jesler)"  wrote:

>We are working on ways to not only fix the on going mirror issues, but prevent 
>them in the future, as well as bring back the Mirror page on 
>ClamAV.net at some point soon.
>
>That being said — We are seeing nothing wrong between our mirrors (that work), 
>and our Sync servers.  However, the reports that we are seeing here, through 
>social media, and the direct reports via the website are telling us that you 
>need to delete mirrors.dat and the daily.cld file that are on your systems and 
>re-run Freshclam.
>
>
>--
>Joel Esler | Talos: Manager | jes...@cisco.com
>
>
>
>
>
>
>On Aug 25, 2017, at 2:04 PM, Joel Esler (jesler) 
>mailto:jes...@cisco.com>> wrote:
>
>I am discussing this with our team, about how to make this process not suck.
>
>
>--
>Joel Esler | Talos: Manager | 
>jes...@cisco.com
>
>
>
>
>
>
>On Aug 25, 2017, at 11:01 AM, Dennis Peterson 
>mailto:denni...@inetnw.com>> 
>wrote:
>
>This is abysmal.
>
># freshclam --list-mirrors |grep Success |sort -n -k2
>Successes: 0
>Successes: 0
>Successes: 0
>Successes: 0
>Successes: 0
>Successes: 0
>Successes: 0
>Successes: 4
>Successes: 7
>Successes: 8
>Successes: 11
>Successes: 11
>Successes: 19
>Successes: 46
>Successes: 79
>Successes: 81
>Successes: 85
>Successes: 90
>Successes: 176
>Successes: 178
>Successes: 188
>Successes: 215
>
># freshclam --list-mirrors |grep Fail |sort -n -k2
>Failures: 0
>Failures: 0
>Failures: 2
>Failures: 4
>Failures: 12
>Failures: 19
>Failures: 21
>Failures: 23
>Failures: 55
>Failures: 90
>Failures: 102
>Failures: 109
>Failures: 110
>Failures: 148
>Failures: 148
>Failures: 160
>Failures: 163
>Failures: 183
>Failures: 274
>Failures: 274
>Failures: 275
>Failures: 275
>
># freshclam --list-mirrors |grep -B2 Fail
>IP: 208.72.56.53
>Successes: 0
>Failures: 275
>--
>IP: 200.236.31.1
>Successes: 81
>Failures: 160
>--
>IP: 64.6.100.177
>Successes: 0
>Failures: 274
>--
>...
>
>dp
>
>On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
>On it
>
>Sent from my iPhone
>
>
>___
>clamav-users mailing list
>clamav-users@lists.clamav.net
>http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
>Help us build a comprehensive ClamAV guide:
>https://github.com/vrtadmin/clamav-faq
>
>http://www.clamav.net/contact.html#ml
>
>___
>clamav-users mailing list
>clamav-users@lists.clamav.net
>http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
>Help us build a comprehensive ClamAV guide:
>https://github.com/vrtadmin/clamav-faq
>
>http://www.clamav.net/contact.html#ml
>
>___
>clamav-users mailing list
>clamav-users@lists.clamav.net
>http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
>Help us build a comprehensive ClamAV guide:
>https://github.com/vrtadmin/clamav-faq
>
>http://www.clamav.net/contact.html#ml

-- 

Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


pgp4HYcU2Y1BH.pgp
Description: OpenPGP digital signature
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Paul Kosinski]

We were getting a lot of failed attempts to download from various
mirrors, but I don't think it ever completely blocked updates.
In any case, early Friday morning I deleted mirrors.dat to see if it
would help. Since then I have seen several "bad" mirrors, but have
still been able to download (we're most recently at 23713).

One perhaps significant difference from common usage is that freshclam
on our gateway is run as cron job every 1.5 hours, rather than running
continuously and doing its own timing. Thus it gets "reset" every time
it attempts to update the database. (We always download the cvd files
to our gateway machine and then serve them from there to the other
machines on the LAN.)

Some of today's error msgs from freshclam include:

  WARNING: getfile: daily.cvd not found on db.us.clamav.net (IP: 155.98.64.87)
  Can't connect to port 80 of host db.us.clamav.net (IP: 64.6.100.177)
  Can't connect to port 80 of host db.us.clamav.net (IP: 208.72.56.53)
  Can't connect to port 80 of host db.us.clamav.net (IP: 64.22.33.90)
  Can't connect to port 80 of host db.us.clamav.net (IP: 168.143.19.95)

The latest successful download was:

  --  Friday 25 August 2017 at 18:06:02 EDT
  Current working dir is /opt/clamav.d/clamav.0.99.2/share/clamav
  Max retries == 4
  ClamAV update process started at Fri Aug 25 18:06:02 2017
  Using IPv6 aware code
  Querying current.cvd.clamav.net
  TTL: 615
  Software version from DNS: 0.99.2
  main.cvd version from DNS: 58
  main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
sigmgr)
  daily.cvd version from DNS: 23713
  Retrieving http://db.us.clamav.net/daily.cvd
  Trying to download http://db.us.clamav.net/daily.cvd (IP: 150.214.142.197)
  Downloading daily.cvd [100%]
  Loading signatures from daily.cvd
  Properly loaded 1742567 signatures from new daily.cvd
  daily.cvd updated (version: 23713, sigs: 1742567, f-level: 63, builder: neo)
  Querying daily.23713.82.1.0.96D68EC5.ping.clamav.net
  bytecode.cvd version from DNS: 309
  bytecode.cvd is up to date (version: 309, sigs: 69, f-level: 63, builder: 
bbaker)
  Database updated (6308885 signatures) from db.us.clamav.net (IP: 
150.214.142.197)
  OnUpdateExecute: EXIT_1
  --  Friday 25 August 2017 at 18:06:34 EDT


=


On Fri, 25 Aug 2017 20:44:58 +
"Joel Esler (jesler)"  wrote:

> We are working on ways to not only fix the on going mirror issues,
> but prevent them in the future, as well as bring back the Mirror page
> on ClamAV.net at some point soon.
> 
> That being said — We are seeing nothing wrong between our mirrors
> (that work), and our Sync servers.  However, the reports that we are
> seeing here, through social media, and the direct reports via the
> website are telling us that you need to delete mirrors.dat and the
> daily.cld file that are on your systems and re-run Freshclam.
> 
> 
> --
> Joel Esler | Talos: Manager |
> jes...@cisco.com
> 
> 
> 
> 
> 
> 
> On Aug 25, 2017, at 2:04 PM, Joel Esler (jesler)
> mailto:jes...@cisco.com>> wrote:
> 
> I am discussing this with our team, about how to make this process
> not suck.
> 
> 
> --
> Joel Esler | Talos: Manager |
> jes...@cisco.com
> 
> 
> 
> 
> 
> 
> On Aug 25, 2017, at 11:01 AM, Dennis Peterson
> mailto:denni...@inetnw.com>>
> wrote:
> 
> This is abysmal.
> 
> # freshclam --list-mirrors |grep Success |sort -n -k2
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 4
> Successes: 7
> Successes: 8
> Successes: 11
> Successes: 11
> Successes: 19
> Successes: 46
> Successes: 79
> Successes: 81
> Successes: 85
> Successes: 90
> Successes: 176
> Successes: 178
> Successes: 188
> Successes: 215
> 
> # freshclam --list-mirrors |grep Fail |sort -n -k2
> Failures: 0
> Failures: 0
> Failures: 2
> Failures: 4
> Failures: 12
> Failures: 19
> Failures: 21
> Failures: 23
> Failures: 55
> Failures: 90
> Failures: 102
> Failures: 109
> Failures: 110
> Failures: 148
> Failures: 148
> Failures: 160
> Failures: 163
> Failures: 183
> Failures: 274
> Failures: 274
> Failures: 275
> Failures: 275
> 
> # freshclam --list-mirrors |grep -B2 Fail
> IP: 208.72.56.53
> Successes: 0
> Failures: 275
> --
> IP: 200.236.31.1
> Successes: 81
> Failures: 160
> --
> IP: 64.6.100.177
> Successes: 0
> Failures: 274
> --
> ...
> 
> dp
> 
> On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
> On it
> 
> Sent from my iPhone
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Gene Heskett]

On Friday 25 August 2017 16:44:58 Joel Esler (jesler) wrote:

> We are working on ways to not only fix the on going mirror issues, but
> prevent them in the future, as well as bring back the Mirror page on
> ClamAV.net at some point soon.
>
> That being said — We are seeing nothing wrong between our mirrors
> (that work), and our Sync servers.  However, the reports that we are
> seeing here, through social media, and the direct reports via the
> website are telling us that you need to delete mirrors.dat and the
> daily.cld file that are on your systems and re-run Freshclam.
>
>
Thanks Joel.

> --
> Joel Esler | Talos: Manager |
> jes...@cisco.com
>
>
>
>
>
>
> On Aug 25, 2017, at 2:04 PM, Joel Esler (jesler)
> mailto:jes...@cisco.com>> wrote:
>
> I am discussing this with our team, about how to make this process not
> suck.
>
>
> --
> Joel Esler | Talos: Manager |
> jes...@cisco.com
>
>
>
>
>
>
> On Aug 25, 2017, at 11:01 AM, Dennis Peterson
> mailto:denni...@inetnw.com>w.com>> wrote:
>
> This is abysmal.
>
> # freshclam --list-mirrors |grep Success |sort -n -k2
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 0
> Successes: 4
> Successes: 7
> Successes: 8
> Successes: 11
> Successes: 11
> Successes: 19
> Successes: 46
> Successes: 79
> Successes: 81
> Successes: 85
> Successes: 90
> Successes: 176
> Successes: 178
> Successes: 188
> Successes: 215
>
> # freshclam --list-mirrors |grep Fail |sort -n -k2
> Failures: 0
> Failures: 0
> Failures: 2
> Failures: 4
> Failures: 12
> Failures: 19
> Failures: 21
> Failures: 23
> Failures: 55
> Failures: 90
> Failures: 102
> Failures: 109
> Failures: 110
> Failures: 148
> Failures: 148
> Failures: 160
> Failures: 163
> Failures: 183
> Failures: 274
> Failures: 274
> Failures: 275
> Failures: 275
>
> # freshclam --list-mirrors |grep -B2 Fail
> IP: 208.72.56.53
> Successes: 0
> Failures: 275
> --
> IP: 200.236.31.1
> Successes: 81
> Failures: 160
> --
> IP: 64.6.100.177
> Successes: 0
> Failures: 274
> --
> ...
>
> dp
>
> On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
> On it
>
> Sent from my iPhone
>
>
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.netilto:clamav-users@lists.clamav.net>
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Joel Esler (jesler)]

We are working on ways to not only fix the on going mirror issues, but prevent 
them in the future, as well as bring back the Mirror page on 
ClamAV.net at some point soon.

That being said — We are seeing nothing wrong between our mirrors (that work), 
and our Sync servers.  However, the reports that we are seeing here, through 
social media, and the direct reports via the website are telling us that you 
need to delete mirrors.dat and the daily.cld file that are on your systems and 
re-run Freshclam.


--
Joel Esler | Talos: Manager | jes...@cisco.com






On Aug 25, 2017, at 2:04 PM, Joel Esler (jesler) 
mailto:jes...@cisco.com>> wrote:

I am discussing this with our team, about how to make this process not suck.


--
Joel Esler | Talos: Manager | 
jes...@cisco.com






On Aug 25, 2017, at 11:01 AM, Dennis Peterson 
mailto:denni...@inetnw.com>> 
wrote:

This is abysmal.

# freshclam --list-mirrors |grep Success |sort -n -k2
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 4
Successes: 7
Successes: 8
Successes: 11
Successes: 11
Successes: 19
Successes: 46
Successes: 79
Successes: 81
Successes: 85
Successes: 90
Successes: 176
Successes: 178
Successes: 188
Successes: 215

# freshclam --list-mirrors |grep Fail |sort -n -k2
Failures: 0
Failures: 0
Failures: 2
Failures: 4
Failures: 12
Failures: 19
Failures: 21
Failures: 23
Failures: 55
Failures: 90
Failures: 102
Failures: 109
Failures: 110
Failures: 148
Failures: 148
Failures: 160
Failures: 163
Failures: 183
Failures: 274
Failures: 274
Failures: 275
Failures: 275

# freshclam --list-mirrors |grep -B2 Fail
IP: 208.72.56.53
Successes: 0
Failures: 275
--
IP: 200.236.31.1
Successes: 81
Failures: 160
--
IP: 64.6.100.177
Successes: 0
Failures: 274
--
...

dp

On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
On it

Sent from my iPhone


___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Joel Esler (jesler)]

I am discussing this with our team, about how to make this process not suck.


--
Joel Esler | Talos: Manager | jes...@cisco.com






On Aug 25, 2017, at 11:01 AM, Dennis Peterson 
mailto:denni...@inetnw.com>> wrote:

This is abysmal.

# freshclam --list-mirrors |grep Success |sort -n -k2
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 4
Successes: 7
Successes: 8
Successes: 11
Successes: 11
Successes: 19
Successes: 46
Successes: 79
Successes: 81
Successes: 85
Successes: 90
Successes: 176
Successes: 178
Successes: 188
Successes: 215

# freshclam --list-mirrors |grep Fail |sort -n -k2
Failures: 0
Failures: 0
Failures: 2
Failures: 4
Failures: 12
Failures: 19
Failures: 21
Failures: 23
Failures: 55
Failures: 90
Failures: 102
Failures: 109
Failures: 110
Failures: 148
Failures: 148
Failures: 160
Failures: 163
Failures: 183
Failures: 274
Failures: 274
Failures: 275
Failures: 275

# freshclam --list-mirrors |grep -B2 Fail
IP: 208.72.56.53
Successes: 0
Failures: 275
--
IP: 200.236.31.1
Successes: 81
Failures: 160
--
IP: 64.6.100.177
Successes: 0
Failures: 274
--
...

dp

On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:
On it

Sent from my iPhone


___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

Are you not able to create your own mirror?

dp

On 8/25/17 8:48 AM, Paul Dean wrote:

Hi,

Thanks for the info, but doing this across several groups of servers is not 
really suitable. But that said, if there is no viable fix in the next day or 
so, then this might be the only solution.

Does anyone have a list of confirmed working mirrors?

Thanks Joel for getting onto this, let me know if I can help somehow.

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 07:43:08 -0700
Dennis Peterson  wrote:


You don't need ClamAV ppl to help - you have complete control over this 
process. Try this:

Find a healthy mirror
Put that healthy mirror's IP address in your freshclam.conf file as the first 
definition of DatabaseMirror
Run freshclam manually.

grep ^DatabaseMirror freshclam.conf

You should see a host name such as db.de.clamav.net. Use the host or nslookup 
command to expand that to reveal all the round-robin IP addresses. It looks 
like this (as of this moment):

host db.de.clamav.net

db.de.clamav.net has address 195.30.97.3
db.de.clamav.net has address 212.227.138.145
db.de.clamav.net has address 213.174.32.130
db.de.clamav.net has address 5.9.253.237
db.de.clamav.net has address 62.27.56.14
db.de.clamav.net has address 62.201.161.84
db.de.clamav.net has address 62.245.181.53
db.de.clamav.net has address 84.39.110.99
db.de.clamav.net has address 88.198.17.100
db.de.clamav.net has address 130.133.110.67
db.de.clamav.net has address 144.76.28.11
db.de.clamav.net has address 178.63.73.246
db.de.clamav.net has address 193.27.49.165

Ping each of these hosts to see which ones respond. Use geoiplookup or similar 
tool to find which healthy sites are located near you. No point trying to poll 
a site around the world from you. If you don't have a geoip tool then notice 
the response time of each mirror's successful ping. The lower the time the 
better suited it could be for you.

Choose an IP that looks promising. Put that in your freshclam.conf file and run 
freshclam. For example:

DatabaseMirror 195.30.97.3

Remember this is a temporary fix - don't depend on this configuration to work 
in the long run. Undo it when the ClamAV ppl fix the mirrors problem.

As an aside try some diagnostics - run freshclam manually:
freshclam --list-mirrors

This will give you a list of mirrors and their health. On the report I see some 
of the mirrors have never responded, others respond about 50% of the time. If 
you see a mirror that is 100% successful you can use that in your 
freshclam.conf file. It would be helpful if the ClamAV ppl would remove the bad 
actors from the DNS records.

If none of this makes sense then do nothing and wait for the ClamAV ppl. Better 
safe than sorry.

dp




On 8/25/17 2:14 AM, Paul Dean wrote:

Oh shoot ClamAV ppl, help please...

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 10:47:23 +0200
maxal  wrote:
  

hi,

yes, this is ongoing as there are numerous broken mirrors in different
country zones out there, eg german zone db.de.clamav.net:

db.de.clamav.net has address 62.201.161.84 -> OK
db.de.clamav.net has address 195.30.97.3 -> OK
db.de.clamav.net has address 130.133.110.67 -> OK
db.de.clamav.net has address 212.227.138.145 -> OK
db.de.clamav.net has
address 62.27.56.14 -> OK
db.de.clamav.net has address 62.245.181.53 ->
OK
db.de.clamav.net has address 193.27.49.165 -> OK
db.de.clamav.net has address 88.198.17.100 -> FAIL
db.de.clamav.net has address 84.39.110.99 -> FAIL
db.de.clamav.net has address 144.76.28.11 -> FAIL
db.de.clamav.net has address 213.174.32.130 -> FAIL
db.de.clamav.net has address 5.9.253.237 -> FAIL
db.de.clamav.net has address 178.63.73.246 -> FAIL

regards
max


On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:

Hi,

I've checked the lists and nuked the mirror.dat file as suggested,
but still getting failure on dling daily-23699.cdiff via freshclam.
Also tried via wget, and got a 404 error. So currently I'm stuck on
23698.

Also nuked all .cld files and still failed.

I've got a few servers/machines that use ClamAV, so hoping a overall
fix instead of each machine would be preferable.

All machines are based in AU and failures happen with
db.local.clamav.net and database.clamav.net.

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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



___
clamav-users mailing list
clamav-users@lis

Re: [clamav-users] Freshclam failure - Still ongoing???

[Paul Dean]

Hi,

Thanks for the info, but doing this across several groups of servers is not 
really suitable. But that said, if there is no viable fix in the next day or 
so, then this might be the only solution.

Does anyone have a list of confirmed working mirrors?

Thanks Joel for getting onto this, let me know if I can help somehow.

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 07:43:08 -0700
Dennis Peterson  wrote:

>You don't need ClamAV ppl to help - you have complete control over this 
>process. Try this:
>
>Find a healthy mirror
>Put that healthy mirror's IP address in your freshclam.conf file as the first 
>definition of DatabaseMirror
>Run freshclam manually.
>
>grep ^DatabaseMirror freshclam.conf
>
>You should see a host name such as db.de.clamav.net. Use the host or nslookup 
>command to expand that to reveal all the round-robin IP addresses. It looks 
>like this (as of this moment):
>
>host db.de.clamav.net
>
>db.de.clamav.net has address 195.30.97.3
>db.de.clamav.net has address 212.227.138.145
>db.de.clamav.net has address 213.174.32.130
>db.de.clamav.net has address 5.9.253.237
>db.de.clamav.net has address 62.27.56.14
>db.de.clamav.net has address 62.201.161.84
>db.de.clamav.net has address 62.245.181.53
>db.de.clamav.net has address 84.39.110.99
>db.de.clamav.net has address 88.198.17.100
>db.de.clamav.net has address 130.133.110.67
>db.de.clamav.net has address 144.76.28.11
>db.de.clamav.net has address 178.63.73.246
>db.de.clamav.net has address 193.27.49.165
>
>Ping each of these hosts to see which ones respond. Use geoiplookup or similar 
>tool to find which healthy sites are located near you. No point trying to poll 
>a site around the world from you. If you don't have a geoip tool then notice 
>the response time of each mirror's successful ping. The lower the time the 
>better suited it could be for you.
>
>Choose an IP that looks promising. Put that in your freshclam.conf file and 
>run freshclam. For example:
>
>DatabaseMirror 195.30.97.3
>
>Remember this is a temporary fix - don't depend on this configuration to work 
>in the long run. Undo it when the ClamAV ppl fix the mirrors problem.
>
>As an aside try some diagnostics - run freshclam manually:
>freshclam --list-mirrors
>
>This will give you a list of mirrors and their health. On the report I see 
>some of the mirrors have never responded, others respond about 50% of the 
>time. If you see a mirror that is 100% successful you can use that in your 
>freshclam.conf file. It would be helpful if the ClamAV ppl would remove the 
>bad actors from the DNS records.
>
>If none of this makes sense then do nothing and wait for the ClamAV ppl. 
>Better safe than sorry.
>
>dp
>
>
>
>
>On 8/25/17 2:14 AM, Paul Dean wrote:
>> Oh shoot ClamAV ppl, help please...
>>
>> --
>>
>>
>> Thanks
>>
>> Paul Dean.
>>
>> "Life is not WHAT you make it, it's WHO you have in it..."
>>
>>
>> On Fri, 25 Aug 2017 10:47:23 +0200
>> maxal  wrote:
>>  
>>> hi,
>>>
>>> yes, this is ongoing as there are numerous broken mirrors in different
>>> country zones out there, eg german zone db.de.clamav.net:
>>>
>>> db.de.clamav.net has address 62.201.161.84 -> OK
>>> db.de.clamav.net has address 195.30.97.3 -> OK
>>> db.de.clamav.net has address 130.133.110.67 -> OK
>>> db.de.clamav.net has address 212.227.138.145 -> OK
>>> db.de.clamav.net has
>>> address 62.27.56.14 -> OK
>>> db.de.clamav.net has address 62.245.181.53 ->
>>> OK
>>> db.de.clamav.net has address 193.27.49.165 -> OK
>>> db.de.clamav.net has address 88.198.17.100 -> FAIL
>>> db.de.clamav.net has address 84.39.110.99 -> FAIL
>>> db.de.clamav.net has address 144.76.28.11 -> FAIL
>>> db.de.clamav.net has address 213.174.32.130 -> FAIL
>>> db.de.clamav.net has address 5.9.253.237 -> FAIL
>>> db.de.clamav.net has address 178.63.73.246 -> FAIL
>>>
>>> regards
>>> max
>>>
>>>
>>> On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:  
 Hi,

 I've checked the lists and nuked the mirror.dat file as suggested,
 but still getting failure on dling daily-23699.cdiff via freshclam.
 Also tried via wget, and got a 404 error. So currently I'm stuck on
 23698.

 Also nuked all .cld files and still failed.

 I've got a few servers/machines that use ClamAV, so hoping a overall
 fix instead of each machine would be preferable.

 All machines are based in AU and failures happen with
 db.local.clamav.net and database.clamav.net.

 ___
 clamav-users mailing list
 clamav-users@lists.clamav.net
 http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

 http://www.clamav.net/contact.html#ml  
>>> ___
>>> clamav-users mailing list
>>> clamav-users@lists.clamav.net
>>> http://lists.clamav.net/cgi-bin/mailm

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

This is abysmal.

# freshclam --list-mirrors |grep Success |sort -n -k2
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 0
Successes: 4
Successes: 7
Successes: 8
Successes: 11
Successes: 11
Successes: 19
Successes: 46
Successes: 79
Successes: 81
Successes: 85
Successes: 90
Successes: 176
Successes: 178
Successes: 188
Successes: 215

# freshclam --list-mirrors |grep Fail |sort -n -k2
Failures: 0
Failures: 0
Failures: 2
Failures: 4
Failures: 12
Failures: 19
Failures: 21
Failures: 23
Failures: 55
Failures: 90
Failures: 102
Failures: 109
Failures: 110
Failures: 148
Failures: 148
Failures: 160
Failures: 163
Failures: 183
Failures: 274
Failures: 274
Failures: 275
Failures: 275

# freshclam --list-mirrors |grep -B2 Fail
IP: 208.72.56.53
Successes: 0
Failures: 275
--
IP: 200.236.31.1
Successes: 81
Failures: 160
--
IP: 64.6.100.177
Successes: 0
Failures: 274
--
...

dp

On 8/25/17 4:00 AM, Joel Esler (jesler) wrote:

On it

Sent from my iPhone



___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Dennis Peterson]

You don't need ClamAV ppl to help - you have complete control over this process. 
Try this:


Find a healthy mirror
Put that healthy mirror's IP address in your freshclam.conf file as the first 
definition of DatabaseMirror

Run freshclam manually.

grep ^DatabaseMirror freshclam.conf

You should see a host name such as db.de.clamav.net. Use the host or nslookup 
command to expand that to reveal all the round-robin IP addresses. It looks like 
this (as of this moment):


host db.de.clamav.net

db.de.clamav.net has address 195.30.97.3
db.de.clamav.net has address 212.227.138.145
db.de.clamav.net has address 213.174.32.130
db.de.clamav.net has address 5.9.253.237
db.de.clamav.net has address 62.27.56.14
db.de.clamav.net has address 62.201.161.84
db.de.clamav.net has address 62.245.181.53
db.de.clamav.net has address 84.39.110.99
db.de.clamav.net has address 88.198.17.100
db.de.clamav.net has address 130.133.110.67
db.de.clamav.net has address 144.76.28.11
db.de.clamav.net has address 178.63.73.246
db.de.clamav.net has address 193.27.49.165

Ping each of these hosts to see which ones respond. Use geoiplookup or similar 
tool to find which healthy sites are located near you. No point trying to poll a 
site around the world from you. If you don't have a geoip tool then notice the 
response time of each mirror's successful ping. The lower the time the better 
suited it could be for you.


Choose an IP that looks promising. Put that in your freshclam.conf file and run 
freshclam. For example:


DatabaseMirror 195.30.97.3

Remember this is a temporary fix - don't depend on this configuration to work in 
the long run. Undo it when the ClamAV ppl fix the mirrors problem.


As an aside try some diagnostics - run freshclam manually:
freshclam --list-mirrors

This will give you a list of mirrors and their health. On the report I see some 
of the mirrors have never responded, others respond about 50% of the time. If 
you see a mirror that is 100% successful you can use that in your freshclam.conf 
file. It would be helpful if the ClamAV ppl would remove the bad actors from the 
DNS records.


If none of this makes sense then do nothing and wait for the ClamAV ppl. Better 
safe than sorry.


dp




On 8/25/17 2:14 AM, Paul Dean wrote:

Oh shoot ClamAV ppl, help please...

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 10:47:23 +0200
maxal  wrote:


hi,

yes, this is ongoing as there are numerous broken mirrors in different
country zones out there, eg german zone db.de.clamav.net:

db.de.clamav.net has address 62.201.161.84 -> OK
db.de.clamav.net has address 195.30.97.3 -> OK
db.de.clamav.net has address 130.133.110.67 -> OK
db.de.clamav.net has address 212.227.138.145 -> OK
db.de.clamav.net has
address 62.27.56.14 -> OK
db.de.clamav.net has address 62.245.181.53 ->
OK
db.de.clamav.net has address 193.27.49.165 -> OK
db.de.clamav.net has address 88.198.17.100 -> FAIL
db.de.clamav.net has address 84.39.110.99 -> FAIL
db.de.clamav.net has address 144.76.28.11 -> FAIL
db.de.clamav.net has address 213.174.32.130 -> FAIL
db.de.clamav.net has address 5.9.253.237 -> FAIL
db.de.clamav.net has address 178.63.73.246 -> FAIL

regards
max


On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:

Hi,

I've checked the lists and nuked the mirror.dat file as suggested,
but still getting failure on dling daily-23699.cdiff via freshclam.
Also tried via wget, and got a 404 error. So currently I'm stuck on
23698.

Also nuked all .cld files and still failed.

I've got a few servers/machines that use ClamAV, so hoping a overall
fix instead of each machine would be preferable.

All machines are based in AU and failures happen with
db.local.clamav.net and database.clamav.net.

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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




___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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



___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Joel Esler (jesler)]

On it

Sent from my iPhone

> On Aug 25, 2017, at 5:14 AM, Paul Dean  wrote:
> 
> Oh shoot ClamAV ppl, help please...
> 
> --
> 
> 
> Thanks
> 
> Paul Dean.
> 
> "Life is not WHAT you make it, it's WHO you have in it..."
> 
> 
> On Fri, 25 Aug 2017 10:47:23 +0200
> maxal  wrote:
> 
>> hi,
>> 
>> yes, this is ongoing as there are numerous broken mirrors in different
>> country zones out there, eg german zone db.de.clamav.net:
>> 
>> db.de.clamav.net has address 62.201.161.84 -> OK
>> db.de.clamav.net has address 195.30.97.3 -> OK
>> db.de.clamav.net has address 130.133.110.67 -> OK
>> db.de.clamav.net has address 212.227.138.145 -> OK
>> db.de.clamav.net has
>> address 62.27.56.14 -> OK
>> db.de.clamav.net has address 62.245.181.53 ->
>> OK
>> db.de.clamav.net has address 193.27.49.165 -> OK 
>> db.de.clamav.net has address 88.198.17.100 -> FAIL 
>> db.de.clamav.net has address 84.39.110.99 -> FAIL
>> db.de.clamav.net has address 144.76.28.11 -> FAIL
>> db.de.clamav.net has address 213.174.32.130 -> FAIL
>> db.de.clamav.net has address 5.9.253.237 -> FAIL
>> db.de.clamav.net has address 178.63.73.246 -> FAIL
>> 
>> regards
>> max
>> 
>> 
>>> On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:
>>> Hi,
>>> 
>>> I've checked the lists and nuked the mirror.dat file as suggested,
>>> but still getting failure on dling daily-23699.cdiff via freshclam.
>>> Also tried via wget, and got a 404 error. So currently I'm stuck on
>>> 23698.
>>> 
>>> Also nuked all .cld files and still failed.
>>> 
>>> I've got a few servers/machines that use ClamAV, so hoping a overall
>>> fix instead of each machine would be preferable.
>>> 
>>> All machines are based in AU and failures happen with
>>> db.local.clamav.net and database.clamav.net.
>>> 
>>> ___
>>> clamav-users mailing list
>>> clamav-users@lists.clamav.net
>>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>>> 
>>> 
>>> Help us build a comprehensive ClamAV guide:
>>> https://github.com/vrtadmin/clamav-faq
>>> 
>>> http://www.clamav.net/contact.html#ml  
>> ___
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>> 
>> 
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> 
>> http://www.clamav.net/contact.html#ml
> 
> 
> -- 
> 
> Thanks
> 
> Paul Dean.
> 
> "Life is not WHAT you make it, it's WHO you have in it..."
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Paul Dean]

Oh shoot ClamAV ppl, help please...

--


Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


On Fri, 25 Aug 2017 10:47:23 +0200
maxal  wrote:

>hi,
>
>yes, this is ongoing as there are numerous broken mirrors in different
>country zones out there, eg german zone db.de.clamav.net:
>
>db.de.clamav.net has address 62.201.161.84 -> OK
>db.de.clamav.net has address 195.30.97.3 -> OK
>db.de.clamav.net has address 130.133.110.67 -> OK
>db.de.clamav.net has address 212.227.138.145 -> OK
>db.de.clamav.net has
>address 62.27.56.14 -> OK
>db.de.clamav.net has address 62.245.181.53 ->
>OK
>db.de.clamav.net has address 193.27.49.165 -> OK 
>db.de.clamav.net has address 88.198.17.100 -> FAIL 
>db.de.clamav.net has address 84.39.110.99 -> FAIL
>db.de.clamav.net has address 144.76.28.11 -> FAIL
>db.de.clamav.net has address 213.174.32.130 -> FAIL
>db.de.clamav.net has address 5.9.253.237 -> FAIL
>db.de.clamav.net has address 178.63.73.246 -> FAIL
>
>regards
>max
>
>
>On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:
>> Hi,
>> 
>> I've checked the lists and nuked the mirror.dat file as suggested,
>> but still getting failure on dling daily-23699.cdiff via freshclam.
>> Also tried via wget, and got a 404 error. So currently I'm stuck on
>> 23698.
>> 
>> Also nuked all .cld files and still failed.
>> 
>> I've got a few servers/machines that use ClamAV, so hoping a overall
>> fix instead of each machine would be preferable.
>> 
>> All machines are based in AU and failures happen with
>> db.local.clamav.net and database.clamav.net.
>> 
>> ___
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>> 
>> 
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> 
>> http://www.clamav.net/contact.html#ml  
>___
>clamav-users mailing list
>clamav-users@lists.clamav.net
>http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
>Help us build a comprehensive ClamAV guide:
>https://github.com/vrtadmin/clamav-faq
>
>http://www.clamav.net/contact.html#ml


-- 

Thanks

Paul Dean.

"Life is not WHAT you make it, it's WHO you have in it..."


pgpLjboEKWE4R.pgp
Description: OpenPGP digital signature
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[maxal]

hi,

yes, this is ongoing as there are numerous broken mirrors in different
country zones out there, eg german zone db.de.clamav.net:

db.de.clamav.net has address 62.201.161.84 -> OK
db.de.clamav.net has address 195.30.97.3 -> OK
db.de.clamav.net has address 130.133.110.67 -> OK
db.de.clamav.net has address 212.227.138.145 -> OK
db.de.clamav.net has
address 62.27.56.14 -> OK
db.de.clamav.net has address 62.245.181.53 ->
OK
db.de.clamav.net has address 193.27.49.165 -> OK 
db.de.clamav.net has address 88.198.17.100 -> FAIL 
db.de.clamav.net has address 84.39.110.99 -> FAIL
db.de.clamav.net has address 144.76.28.11 -> FAIL
db.de.clamav.net has address 213.174.32.130 -> FAIL
db.de.clamav.net has address 5.9.253.237 -> FAIL
db.de.clamav.net has address 178.63.73.246 -> FAIL

regards
max


On Fri, 2017-08-25 at 16:24 +0800, Paul Dean wrote:
> Hi,
> 
> I've checked the lists and nuked the mirror.dat file as suggested,
> but still getting failure on dling daily-23699.cdiff via freshclam.
> Also tried via wget, and got a 404 error. So currently I'm stuck on
> 23698.
> 
> Also nuked all .cld files and still failed.
> 
> I've got a few servers/machines that use ClamAV, so hoping a overall
> fix instead of each machine would be preferable.
> 
> All machines are based in AU and failures happen with
> db.local.clamav.net and database.clamav.net.
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[Simon Mousey Smith]

Hi

I think the is a fault with that particular provider of the mirror

whois 193.1.193.64 os showing as HEANET-MIRROR

My 'dig database.clamav.net ' in the UK Liverpool 
here WAS showing as that IP address,

however the round-robin doesn’t seem to use that server anymore strangely 
enough? and NOW using others instead

Maybe contact heanet and ask them if the is an issue with there mirror server

Or change ya freshclam.conf to use another dns like db.uk.clamav.net 


Regards

Simon

> On 25 Aug 2017, at 09:37, briancullen  wrote:
> 
> The problem has me (also in Australia) still stuck on 23695:
> 
> main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
> sigmgr)
> WARNING: getpatch: Can't download daily-23695.cdiff from database.clamav.net
> WARNING: getpatch: Can't download daily-23695.cdiff from database.clamav.net
> ERROR: getpatch: Can't download daily-23695.cdiff from database.clamav.net
> WARNING: Incremental update failed, trying to download daily.cvd
> WARNING: getfile: daily.cvd not found on remote server (IP: 193.1.193.64)
> ERROR: Can't download daily.cvd from database.clamav.net
> Giving up on database.clamav.net...
> 
>> On 25 Aug 2017, at 6:24 pm, Paul Dean  wrote:
>> 
>> Hi,
>> 
>> I've checked the lists and nuked the mirror.dat file as suggested, but still 
>> getting failure on dling daily-23699.cdiff via freshclam.
>> Also tried via wget, and got a 404 error. So currently I'm stuck on 23698.
>> 
>> Also nuked all .cld files and still failed.
>> 
>> I've got a few servers/machines that use ClamAV, so hoping a overall fix 
>> instead of each machine would be preferable.
>> 
>> All machines are based in AU and failures happen with db.local.clamav.net 
>> and database.clamav.net.
>> 
>> -- 
>> 
>> Thanks
>> 
>> Paul Dean.
>> 
>> "Life is not WHAT you make it, it's WHO you have in it..."
>> ___
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>> 
>> 
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> 
>> http://www.clamav.net/contact.html#ml
> 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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

Re: [clamav-users] Freshclam failure - Still ongoing???

[briancullen]

The problem has me (also in Australia) still stuck on 23695:

main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
sigmgr)
WARNING: getpatch: Can't download daily-23695.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-23695.cdiff from database.clamav.net
ERROR: getpatch: Can't download daily-23695.cdiff from database.clamav.net
WARNING: Incremental update failed, trying to download daily.cvd
WARNING: getfile: daily.cvd not found on remote server (IP: 193.1.193.64)
ERROR: Can't download daily.cvd from database.clamav.net
Giving up on database.clamav.net...

> On 25 Aug 2017, at 6:24 pm, Paul Dean  wrote:
> 
> Hi,
> 
> I've checked the lists and nuked the mirror.dat file as suggested, but still 
> getting failure on dling daily-23699.cdiff via freshclam.
> Also tried via wget, and got a 404 error. So currently I'm stuck on 23698.
> 
> Also nuked all .cld files and still failed.
> 
> I've got a few servers/machines that use ClamAV, so hoping a overall fix 
> instead of each machine would be preferable.
> 
> All machines are based in AU and failures happen with db.local.clamav.net and 
> database.clamav.net.
> 
> -- 
> 
> Thanks
> 
> Paul Dean.
> 
> "Life is not WHAT you make it, it's WHO you have in it..."
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


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

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