Any particular reason that you are using a local mirror? I mean, if not
strictly necessary, just point it at our mirrors and call it a day.
I've talked to a couple people off list in the last few days that were
experiencing errors or delays, and 100% of them were using local proxies or
mirrors
I just took a peek at the HAVP source code. It looks like it has a
"ClamdScanner" and a "ClamLibScanner". The ClamLibScanner code is only built
if you configure with --enable-clamav, else I _think_ it falls back to the
ClamdScanner variant.
To get HAVP's ClamLibScanner class to build with libc
lukn,
Sorry about all the trouble. I wish I knew more about what was happening. I
hope it's not a legitimate bug slipping by. Let us know if you end up finding
anything else.
Regards,
Micah
On Nov 20, 2018, at 2:40 AM, lukn mailto:lukn...@gmail.com>>
wrote:
Hi Micah and Henrik
I'm slowl
I think you misunderstand. The 'LocalIPAddress' is the *outgoing* IP
address: i.e., the address assigned to the NIC. (This used to be
important when we had two Internet connections.)
The 'LocalIPAddress' has nothing to do with the IP address that
freshclam tries to get the cvds etc. *from*. (Other
We are using a local mirror to reduce Internet traffic and (mainly) to
reduce load on the ClamAV servers.
It is *only* the "master" (Internet-connected) ClamAV that sees these
delays, where the DNS TXT record advertises updates before whatever
Cloudflare server we (are unlucky enough to) actually
It's possible. But, unless there is a vocal minority that no one is chiming in
about, you are the only person/group that I have heard complain about the
issue...
Millions of people are getting updates from Cloudflare a day, so something is
working correctly, and there's been no configuration c
