Re: [clamav-users] fail updates

Hi, Still having a few issues here, even after ' rm -rfv mirrors.dat ' Reading CVD header (main.cvd): WARNING: main.cvd not found on remote server WARNING: Can't read main.cvd header from db.gb.clamav.net (IP: 193.1.193.64) WARNING: DNS record is older than 3 hours. WARNING: Invalid DNS reply.

Re: [clamav-users] fail updates

Sort of weird from personal experience, but OVH seems to update better than most. If anyone on OVH is here, feel free to explain. Just looking at freshclam logs on my local servers running on links with L3/Cogent vs OVH I seem to have less issues on the OVH mirrors. My personal explanation is

Re: [clamav-users] fail updates

I killed our "mirrors.dat" at 2017-11-06 19:35:35 (EST). It was last modified at 2017-11-06 18:06:29 (EST). We'll see what happens. Paul Kosinski On Mon, 6 Nov 2017 21:21:58 + "Joel Esler (jesler)" wrote: > It would be helpful, if, starting now, deleting mirrors.dat and

Re: [clamav-users] fail updates

On Mon, Nov 06, 2017 at 01:21 PM, Joel Esler (jesler) wrote: > It would be helpful, if, starting now, deleting mirrors.dat and *then* > telling us about failing mirrors…. Cause…. We’ve done many changes in the > past month, it would be good to start from a clean slate. You might want to

Re: [clamav-users] fail updates

It would be helpful, if, starting now, deleting mirrors.dat and *then* telling us about failing mirrors…. Cause…. We’ve done many changes in the past month, it would be good to start from a clean slate. -- Joel Esler | Talos: Manager | jes...@cisco.com On Nov 6,

Re: [clamav-users] fail updates

Am 06.11.2017 um 20:26 schrieb Benny Pedersen: Dennis Peterson skrev den 2017-11-06 19:43: Come to think of it, 130.59.10.36 shouldn't even still be in mirrors.dat and that is part of the systemic problems in the system. Nothing cleans up stale entries in mirrors.dat except rm -f mirrors.dat.

Re: [clamav-users] fail updates

Dennis Peterson skrev den 2017-11-06 19:43: Come to think of it, 130.59.10.36 shouldn't even still be in mirrors.dat and that is part of the systemic problems in the system. Nothing cleans up stale entries in mirrors.dat except rm -f mirrors.dat. yep, its not working well, i see freshclam

Re: [clamav-users] fail updates

Come to think of it, 130.59.10.36 shouldn't even still be in mirrors.dat and that is part of the systemic problems in the system. Nothing cleans up stale entries in mirrors.dat except rm -f mirrors.dat. dp On 11/6/17 9:02 AM, Benny Pedersen wrote: freshclam --list-mirrors Mirror #1 IP:

Re: [clamav-users] fail updates

Here's our latest actual download (subsequent queries showed nothing new). Note that 204.130.133.50 worked for us (from 66.31.152.192). Paul -- Monday 06 November 2017 at 09:06:03 EST -- Current working dir is

Re: [clamav-users] fail updates

Your report includes mirrors that should be ignored based on last access. I built a list of current mirrors from freshclam logs that go back only to August. grep -h Ignoring freshclam* |grep -v Reading |awk '{print $9}' |sort |uniq -c |sort -rn The result is an easy to understand (if not jaw

[clamav-users] fail updates

freshclam --list-mirrors Mirror #1 IP: 130.59.10.36 Successes: 391 Failures: 97 Last access: Mon Dec 19 00:46:43 2016 Ignore: No - Mirror #2 IP: 193.1.193.64 Successes: 2122 Failures: 208 Last access: Mon Nov 6 16:44:43 2017 Ignore: Yes