Discussion:
[clamav-users] updates
Michael Da Cova
2018-09-07 09:11:16 UTC
Permalink
Hi

I still get "WARNING: Mirror 104.16.187.138 is not synchronized" often
on freshclam updates

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.187.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.187.138 is not synchronized

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.185.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.185.138 is not synchronized.

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.186.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.186.138 is not synchronized.

Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
Giving up on database.clamav.net...

I have been deleting the mirror.dat file which seems to help for a while

--
Michael Da Cova

_______________________________________________
clamav-users mailing list
clamav-***@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
Micah Snyder (micasnyd)
2018-09-07 15:32:51 UTC
Permalink
Hi Michael,

Can you tell me what geographic region/country you're coming from? We've seen reports of this from a number of users though I've never personally observed this. I am starting to wonder if the issue is only occurring in certain region(s).

Regardless, I am going to try to mitigate the error in the upcoming 0.100.2 patch release and 0.101 feature release.

-Micah

Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.


On Sep 7, 2018, at 5:11 AM, Michael Da Cova <***@netpilot.com<mailto:***@netpilot.com>> wrote:

Hi

I still get "WARNING: Mirror 104.16.187.138 is not synchronized" often on freshclam updates

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.187.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.187.138 is not synchronized

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.185.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.185.138 is not synchronized.

Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.186.138)
Downloading daily.cvd [100%]
WARNING: Mirror 104.16.186.138 is not synchronized.

Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
Giving up on database.clamav.net<http://database.clamav.net>...

I have been deleting the mirror.dat file which seems to help for a while

--
Michael Da Cova

_______________________________________________
clamav-users mailing list
clamav-***@lists.clamav.net<mailto:clamav-***@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
Michael Da Cova
2018-09-08 08:31:44 UTC
Permalink
Hi

sorry just noticed the question below, I never got the original email
from Micah

EU, Ireland (IE)


~michael

> We are located near Boston, and the data comes via Comcast cable, but
> our DNS queries use our old, slow static-IP DSL. I keep it this way
> because there were stories about some major ISPs munging DSL replies
> (like replacing NXDOMAIN with an IP addresse of a Web site belonging to
> the ISP). Our DSL, on the other hand, doesn't ever do this, and even
> passes port 25, so we can send mail directly (rather than relaying
> through a possibly snoopy ISP.)
>
> 2018-08-18 05:03:02 No delay
> 2018-08-18 13:18:02 00:15:01 delay
> 2018-08-18 21:33:02 00:15:01 delay
> 2018-08-19 05:03:01 No delay
> 2018-08-19 14:03:01 00:44:59 delay
> 2018-08-19 21:18:02 00:15:00 delay
> 2018-08-20 05:33:02 00:30:01 delay
> 2018-08-20 13:33:02 00:30:00 delay
> 2018-08-20 21:03:02 No delay
> 2018-08-21 05:18:01 No delay
> 2018-08-21 13:03:01 No delay
> 2018-08-22 18:18:02 00:15:00 delay
> 2018-08-23 02:33:01 00:29:59 delay
> 2018-08-23 09:48:02 00:45:00 delay
> 2018-08-23 17:03:02 No delay
> 2018-08-24 02:18:02 01:15:00 delay
> 2018-08-24 09:33:02 00:30:00 delay
> 2018-08-24 18:48:02 00:30:01 delay
> 2018-08-25 01:18:02 No delay
> 2018-08-25 09:18:02 00:15:00 delay
> 2018-08-25 17:33:02 00:30:00 delay
> 2018-08-26 02:33:01 01:29:59 delay
> 2018-08-26 09:48:02 00:45:01 delay
> 2018-08-26 18:03:02 01:00:00 delay
> 2018-08-27 01:03:01 No delay
> 2018-08-27 09:18:02 00:15:00 delay
> 2018-08-27 17:33:01 00:29:59 delay
> 2018-08-28 01:48:02 00:45:00 delay
> 2018-08-28 09:18:02 No delay
> 2018-08-28 17:33:01 No delay
> 2018-08-29 01:18:01 00:14:59 delay
> 2018-08-29 09:33:02 00:30:01 delay
> 2018-08-29 17:48:01 00:45:00 delay
> 2018-08-30 01:03:01 No delay
> 2018-08-30 09:18:02 00:15:00 delay
> 2018-08-30 17:18:01 00:14:59 delay
> 2018-08-31 01:18:01 00:14:59 delay
> 2018-08-31 09:48:02 00:45:01 delay
> 2018-08-31 22:18:01 00:45:00 delay
> 2018-09-01 05:18:01 00:14:59 delay
> 2018-09-01 13:33:02 00:30:00 delay
> 2018-09-01 21:48:01 00:44:59 delay
> 2018-09-02 07:03:02 01:00:00 delay
> 2018-09-02 13:48:01 00:44:59 delay
> 2018-09-02 21:03:01 No delay
> 2018-09-03 05:03:02 No delay
> 2018-09-03 13:03:02 No delay
> 2018-09-03 21:03:01 No delay
> 2018-09-04 05:03:01 No delay
> 2018-09-04 13:03:02 No delay
> 2018-09-04 21:03:01 No delay
> 2018-09-05 05:03:02 No delay
> 2018-09-05 14:18:01 01:14:59 delay
> 2018-09-05 21:18:02 00:15:00 delay
> 2018-09-06 05:18:02 00:15:00 delay
> 2018-09-06 13:33:02 00:30:01 delay
> 2018-09-06 21:03:03 No delay
> 2018-09-07 05:18:02 00:15:00 delay
>
> ----------
>
> On Fri, 7 Sep 2018 15:32:51 +0000
> "Micah Snyder (micasnyd)" <***@cisco.com> wrote:
>
>> Hi Michael,
>>
>> Can you tell me what geographic region/country you're coming from?
>> We've seen reports of this from a number of users though I've never
>> personally observed this. I am starting to wonder if the issue is
>> only occurring in certain region(s).
>>
>> Regardless, I am going to try to mitigate the error in the upcoming
>> 0.100.2 patch release and 0.101 feature release.
>>
>> -Micah
>>
>> Micah Snyder
>> ClamAV Development
>> Talos
>> Cisco Systems, Inc.
>>
>>
>> On Sep 7, 2018, at 5:11 AM, Michael Da Cova
>> <***@netpilot.com<mailto:***@netpilot.com>> wrote:
>>
>> Hi
>>
>> I still get "WARNING: Mirror 104.16.187.138 is not synchronized"
>> often on freshclam updates
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP:
>> 104.16.187.138) Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.187.138 is not synchronized
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP:
>> 104.16.185.138) Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.185.138 is not synchronized.
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP:
>> 104.16.186.138) Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.186.138 is not synchronized.
>>
>> Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
>> Giving up on database.clamav.net<http://database.clamav.net>...
>>
>> I have been deleting the mirror.dat file which seems to help for a
>> while
>>
>> --
>> Michael Da Cova
> _______________________________________________
> clamav-users mailing list
> clamav-***@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

--
Michael Da Cova

Technical Support Manager

Main Tel: +44 (0)117 3357335 / Mob: +44 (0)790887629
Email: ***@netpilot.com - Web: www.netpilot.com

NetPilot Global Ltd. 9 Portland Square, Bristol, BS2 8ST

Registered in England & Wales, Company No. 11034665 - VAT Number. 280 6776 73
Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible for delivery of the message to such person),
you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to the official business of NetPilot Global Ltd shall be understood as neither given nor endorsed by it.

NetPilot Global Ltd is committed to GDPR compliance.
We are also committed to helping our customers comply with the GDPR by providing stringent privacy and security protections that are built into our service and contracts.
Any personal information that NetPilot Global Ltd may collect (including, but not limited to, your name, company and email address) will be collected, used and held in accordance with the provisions of GDPR and your rights under that Act.



_______________________________________________
clamav-users mailing list
clamav-***@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
Joel Esler (jesler)
2018-09-12 15:41:23 UTC
Permalink
Paul,

Can you give me some more information on how you do this? How often is the check ran, etc.

I am working with cloudflare on the issue now.

On Sep 7, 2018, at 2:25 PM, Paul Kosinski <clamav-***@iment.com<mailto:clamav-***@iment.com>> wrote:

Here is our recent CVD delay report showing how long the actual
daily.cvd (and sometimes bytcode.cvd) file(s) lag behind the DNS TXT
record.

We are located near Boston, and the data comes via Comcast cable, but
our DNS queries use our old, slow static-IP DSL. I keep it this way
because there were stories about some major ISPs munging DSL replies
(like replacing NXDOMAIN with an IP addresse of a Web site belonging to
the ISP). Our DSL, on the other hand, doesn't ever do this, and even
passes port 25, so we can send mail directly (rather than relaying
through a possibly snoopy ISP.)

2018-08-18 05:03:02 No delay
2018-08-18 13:18:02 00:15:01 delay
2018-08-18 21:33:02 00:15:01 delay
2018-08-19 05:03:01 No delay
2018-08-19 14:03:01 00:44:59 delay
2018-08-19 21:18:02 00:15:00 delay
2018-08-20 05:33:02 00:30:01 delay
2018-08-20 13:33:02 00:30:00 delay
2018-08-20 21:03:02 No delay
2018-08-21 05:18:01 No delay
2018-08-21 13:03:01 No delay
2018-08-22 18:18:02 00:15:00 delay
2018-08-23 02:33:01 00:29:59 delay
2018-08-23 09:48:02 00:45:00 delay
2018-08-23 17:03:02 No delay
2018-08-24 02:18:02 01:15:00 delay
2018-08-24 09:33:02 00:30:00 delay
2018-08-24 18:48:02 00:30:01 delay
2018-08-25 01:18:02 No delay
2018-08-25 09:18:02 00:15:00 delay
2018-08-25 17:33:02 00:30:00 delay
2018-08-26 02:33:01 01:29:59 delay
2018-08-26 09:48:02 00:45:01 delay
2018-08-26 18:03:02 01:00:00 delay
2018-08-27 01:03:01 No delay
2018-08-27 09:18:02 00:15:00 delay
2018-08-27 17:33:01 00:29:59 delay
2018-08-28 01:48:02 00:45:00 delay
2018-08-28 09:18:02 No delay
2018-08-28 17:33:01 No delay
2018-08-29 01:18:01 00:14:59 delay
2018-08-29 09:33:02 00:30:01 delay
2018-08-29 17:48:01 00:45:00 delay
2018-08-30 01:03:01 No delay
2018-08-30 09:18:02 00:15:00 delay
2018-08-30 17:18:01 00:14:59 delay
2018-08-31 01:18:01 00:14:59 delay
2018-08-31 09:48:02 00:45:01 delay
2018-08-31 22:18:01 00:45:00 delay
2018-09-01 05:18:01 00:14:59 delay
2018-09-01 13:33:02 00:30:00 delay
2018-09-01 21:48:01 00:44:59 delay
2018-09-02 07:03:02 01:00:00 delay
2018-09-02 13:48:01 00:44:59 delay
2018-09-02 21:03:01 No delay
2018-09-03 05:03:02 No delay
2018-09-03 13:03:02 No delay
2018-09-03 21:03:01 No delay
2018-09-04 05:03:01 No delay
2018-09-04 13:03:02 No delay
2018-09-04 21:03:01 No delay
2018-09-05 05:03:02 No delay
2018-09-05 14:18:01 01:14:59 delay
2018-09-05 21:18:02 00:15:00 delay
2018-09-06 05:18:02 00:15:00 delay
2018-09-06 13:33:02 00:30:01 delay
2018-09-06 21:03:03 No delay
2018-09-07 05:18:02 00:15:00 delay

----------

On Fri, 7 Sep 2018 15:32:51 +0000
"Micah Snyder (micasnyd)" <***@cisco.com<mailto:***@cisco.com>> wrote:

Hi Michael,

Can you tell me what geographic region/country you're coming from?
We've seen reports of this from a number of users though I've never
personally observed this. I am starting to wonder if the issue is
only occurring in certain region(s).

Regardless, I am going to try to mitigate the error in the upcoming
0.100.2 patch release and 0.101 feature release.

-Micah

Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.


On Sep 7, 2018, at 5:11 AM, Michael Da Cova
<***@netpilot.com<mailto:***@netpilot.com><mailto:***@netpilot.com>> wrote:

Hi

I still get "WARNING: Mirror 104.16.187.138 is not synchronized"
often on freshclam updates

Trying to download http://database.clamav.net/daily.cvd (IP:
104.16.187.138) Downloading daily.cvd [100%]
WARNING: Mirror 104.16.187.138 is not synchronized

Trying to download http://database.clamav.net/daily.cvd (IP:
104.16.185.138) Downloading daily.cvd [100%]
WARNING: Mirror 104.16.185.138 is not synchronized.

Trying to download http://database.clamav.net/daily.cvd (IP:
104.16.186.138) Downloading daily.cvd [100%]
WARNING: Mirror 104.16.186.138 is not synchronized.

Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
Giving up on database.clamav.net<http://database.clamav.net/><http://database.clamav.net<http://database.clamav.net/>>...

I have been deleting the mirror.dat file which seems to help for a
while

--
Michael Da Cova


_______________________________________________
clamav-users mailing list
clamav-***@lists.clamav.net<mailto:clamav-***@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
Joel Esler (jesler)
2018-09-12 20:59:45 UTC
Permalink
What is the interval that you run this?

> On Sep 12, 2018, at 4:53 PM, Paul Kosinski <clamav-***@iment.com> wrote:
>
> Joel (and any other interested parties),
>
> Attached is the code we use to update ClamAV: 'getfreshclam' is run by
> cron under userid clamav (same as clamd) every so often (currently
> every 15 mins) to determine if there are any relevant cvd files to
> update (currently daily.cvd, bytecode.cvd and main.cvd).
>
> Only if something is *really* there -- as determined by *both* the DNS
> TXT record and quick 'curl' of the head of the cvd file -- is
> 'freshclam' invoked to do the actual work. This ensures that running
> the test pretty often doesn't put a big load on the servers.
>
> Notes to help understanding the code:
>
> 'testclam-external' does the DNS TXT and curl test.
>
> 'report-delays' logs the delays (or non- delays) found.
>
> We keep various recent versions of ClamAV in /opt/clamav.d, both for
> testing, and in case we have to backtrack. Thus, /opt/clamav is a
> symlink to the current version, as in:
>
> /opt/clamav -> /opt/clamav.d/clamav.0.100.1
>
>
> Enjoy!
> Paul Kosinski
>
>
> On Wed, 12 Sep 2018 15:41:23 +0000
> "Joel Esler (jesler)" <***@cisco.com> wrote:
>
>> Paul,
>>
>> Can you give me some more information on how you do this? How often
>> is the check ran, etc.
>>
>> I am working with cloudflare on the issue now.
>>
>> On Sep 7, 2018, at 2:25 PM, Paul Kosinski
>> <clamav-***@iment.com<mailto:clamav-***@iment.com>> wrote:
>>
>> Here is our recent CVD delay report showing how long the actual
>> daily.cvd (and sometimes bytcode.cvd) file(s) lag behind the DNS TXT
>> record.
>>
>> We are located near Boston, and the data comes via Comcast cable, but
>> our DNS queries use our old, slow static-IP DSL. I keep it this way
>> because there were stories about some major ISPs munging DSL replies
>> (like replacing NXDOMAIN with an IP addresse of a Web site belonging
>> to the ISP). Our DSL, on the other hand, doesn't ever do this, and
>> even passes port 25, so we can send mail directly (rather than
>> relaying through a possibly snoopy ISP.)
>>
>> 2018-08-18 05:03:02 No delay
>> 2018-08-18 13:18:02 00:15:01 delay
>> 2018-08-18 21:33:02 00:15:01 delay
>> 2018-08-19 05:03:01 No delay
>> 2018-08-19 14:03:01 00:44:59 delay
>> 2018-08-19 21:18:02 00:15:00 delay
>> 2018-08-20 05:33:02 00:30:01 delay
>> 2018-08-20 13:33:02 00:30:00 delay
>> 2018-08-20 21:03:02 No delay
>> 2018-08-21 05:18:01 No delay
>> 2018-08-21 13:03:01 No delay
>> 2018-08-22 18:18:02 00:15:00 delay
>> 2018-08-23 02:33:01 00:29:59 delay
>> 2018-08-23 09:48:02 00:45:00 delay
>> 2018-08-23 17:03:02 No delay
>> 2018-08-24 02:18:02 01:15:00 delay
>> 2018-08-24 09:33:02 00:30:00 delay
>> 2018-08-24 18:48:02 00:30:01 delay
>> 2018-08-25 01:18:02 No delay
>> 2018-08-25 09:18:02 00:15:00 delay
>> 2018-08-25 17:33:02 00:30:00 delay
>> 2018-08-26 02:33:01 01:29:59 delay
>> 2018-08-26 09:48:02 00:45:01 delay
>> 2018-08-26 18:03:02 01:00:00 delay
>> 2018-08-27 01:03:01 No delay
>> 2018-08-27 09:18:02 00:15:00 delay
>> 2018-08-27 17:33:01 00:29:59 delay
>> 2018-08-28 01:48:02 00:45:00 delay
>> 2018-08-28 09:18:02 No delay
>> 2018-08-28 17:33:01 No delay
>> 2018-08-29 01:18:01 00:14:59 delay
>> 2018-08-29 09:33:02 00:30:01 delay
>> 2018-08-29 17:48:01 00:45:00 delay
>> 2018-08-30 01:03:01 No delay
>> 2018-08-30 09:18:02 00:15:00 delay
>> 2018-08-30 17:18:01 00:14:59 delay
>> 2018-08-31 01:18:01 00:14:59 delay
>> 2018-08-31 09:48:02 00:45:01 delay
>> 2018-08-31 22:18:01 00:45:00 delay
>> 2018-09-01 05:18:01 00:14:59 delay
>> 2018-09-01 13:33:02 00:30:00 delay
>> 2018-09-01 21:48:01 00:44:59 delay
>> 2018-09-02 07:03:02 01:00:00 delay
>> 2018-09-02 13:48:01 00:44:59 delay
>> 2018-09-02 21:03:01 No delay
>> 2018-09-03 05:03:02 No delay
>> 2018-09-03 13:03:02 No delay
>> 2018-09-03 21:03:01 No delay
>> 2018-09-04 05:03:01 No delay
>> 2018-09-04 13:03:02 No delay
>> 2018-09-04 21:03:01 No delay
>> 2018-09-05 05:03:02 No delay
>> 2018-09-05 14:18:01 01:14:59 delay
>> 2018-09-05 21:18:02 00:15:00 delay
>> 2018-09-06 05:18:02 00:15:00 delay
>> 2018-09-06 13:33:02 00:30:01 delay
>> 2018-09-06 21:03:03 No delay
>> 2018-09-07 05:18:02 00:15:00 delay
> <reportdelays><testclam-external><getfreshclam>_______________________________________________
> clamav-users mailing list
> clamav-***@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-***@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
Joel Esler (jesler)
2018-09-13 14:00:36 UTC
Permalink
Ah, so when you have things like the 14/15 minute delay, the delay may not be that long?

> On Sep 13, 2018, at 2:16 AM, Paul Kosinski <clamav-***@iment.com> wrote:
>
> "What is the interval that you run this?"
>
> Every 15 minutes by cron, specifically:
>
> OCBG='/opt/clamav/bin/getfreshclam'
>
> 3 * * * * root test -x $OCBG && /usr/bin/sudo -u clamav $OCBG && /usr/bin/killall -HUP havp80c && /usr/bin/killall -HUP havp80d
> 18 * * * * root test -x $OCBG && /usr/bin/sudo -u clamav $OCBG && /usr/bin/killall -HUP havp80c && /usr/bin/killall -HUP havp80d
> 33 * * * * root test -x $OCBG && /usr/bin/sudo -u clamav $OCBG && /usr/bin/killall -HUP havp80c && /usr/bin/killall -HUP havp80d
> 48 * * * * root test -x $OCBG && /usr/bin/sudo -u clamav $OCBG && /usr/bin/killall -HUP havp80c && /usr/bin/killall -HUP havp80d
>
>
> (Original post mentioned the interval in passing in the text.)
>
>>> Attached is the code we use to update ClamAV: 'getfreshclam' is run
>>> by cron under userid clamav (same as clamd) every so often
>>> (currently every 15 mins) to determine if there are any relevant
>
> ----------
>
> On Wed, 12 Sep 2018 20:59:45 +0000
> "Joel Esler (jesler)" <***@cisco.com> wrote:
>
>> What is the interval that you run this?
>>
>>> On Sep 12, 2018, at 4:53 PM, Paul Kosinski <clamav-***@iment.com>
>>> wrote:
>>>
>>> Joel (and any other interested parties),
>>>
>>> Attached is the code we use to update ClamAV: 'getfreshclam' is run
>>> by cron under userid clamav (same as clamd) every so often
>>> (currently every 15 mins) to determine if there are any relevant
>>> cvd files to update (currently daily.cvd, bytecode.cvd and
>>> main.cvd).
>>>
>>> Only if something is *really* there -- as determined by *both* the
>>> DNS TXT record and quick 'curl' of the head of the cvd file -- is
>>> 'freshclam' invoked to do the actual work. This ensures that running
>>> the test pretty often doesn't put a big load on the servers.
>>>
>>> Notes to help understanding the code:
>>>
>>> 'testclam-external' does the DNS TXT and curl test.
>>>
>>> 'report-delays' logs the delays (or non- delays) found.
>>>
>>> We keep various recent versions of ClamAV in /opt/clamav.d, both for
>>> testing, and in case we have to backtrack. Thus, /opt/clamav is a
>>> symlink to the current version, as in:
>>>
>>> /opt/clamav -> /opt/clamav.d/clamav.0.100.1
>>>
>>>
>>> Enjoy!
>>> Paul Kosinski
> _______________________________________________
> clamav-users mailing list
> clamav-***@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-***@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
Michael Da Cova
2018-09-12 10:57:45 UTC
Permalink
Hi

is anyone else getting sync errors

Michael



On 07/09/18 10:11, Michael Da Cova wrote:
> Hi
>
> I still get "WARNING: Mirror 104.16.187.138 is not synchronized" often
> on freshclam updates
>
> Trying to download http://database.clamav.net/daily.cvd (IP:
> 104.16.187.138)
> Downloading daily.cvd [100%]
> WARNING: Mirror 104.16.187.138 is not synchronized
>
> Trying to download http://database.clamav.net/daily.cvd (IP:
> 104.16.185.138)
> Downloading daily.cvd [100%]
> WARNING: Mirror 104.16.185.138 is not synchronized.
>
> Trying to download http://database.clamav.net/daily.cvd (IP:
> 104.16.186.138)
> Downloading daily.cvd [100%]
> WARNING: Mirror 104.16.186.138 is not synchronized.
>
> Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
> Giving up on database.clamav.net...
>
> I have been deleting the mirror.dat file which seems to help for a while
>

--
Michael Da Cova

Technical Support Manager

Main Tel: +44 (0)117 3357335 / Mob: +44 (0)790887629
Email: ***@netpilot.com - Web: www.netpilot.com

NetPilot Global Ltd. 9 Portland Square, Bristol, BS2 8ST

Registered in England & Wales, Company No. 11034665 - VAT Number. 280 6776 73
Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible for delivery of the message to such person),
you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions,
conclusions and other information in this message that do not relate to the official business of NetPilot Global Ltd shall be understood as neither given nor endorsed by it.

NetPilot Global Ltd is committed to GDPR compliance.
We are also committed to helping our customers comply with the GDPR by providing stringent privacy and security protections that are built into our service and contracts.
Any personal information that NetPilot Global Ltd may collect (including, but not limited to, your name, company and email address) will be collected, used and held in accordance with the provisions of GDPR and your rights under that Act.



_______________________________________________
clamav-users mailing list
clamav-***@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
Joel Esler (jesler)
2018-09-12 11:32:59 UTC
Permalink
We are going to need more information than that

Sent from my iPhone

> On Sep 12, 2018, at 06:58, Michael Da Cova <***@netpilot.com> wrote:
>
> Hi
>
> is anyone else getting sync errors
>
> Michael
>
>
>
>> On 07/09/18 10:11, Michael Da Cova wrote:
>> Hi
>>
>> I still get "WARNING: Mirror 104.16.187.138 is not synchronized" often on freshclam updates
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.187.138)
>> Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.187.138 is not synchronized
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.185.138)
>> Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.185.138 is not synchronized.
>>
>> Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.186.138)
>> Downloading daily.cvd [100%]
>> WARNING: Mirror 104.16.186.138 is not synchronized.
>>
>> Querying daily.0.79.0.0.6810BA8A.ping.clamav.net
>> Giving up on database.clamav.net...
>>
>> I have been deleting the mirror.dat file which seems to help for a while
>>
>
> --
> Michael Da Cova
>
> Technical Support Manager
>
> Main Tel: +44 (0)117 3357335 / Mob: +44 (0)790887629
> Email: ***@netpilot.com - Web: www.netpilot.com
>
> NetPilot Global Ltd. 9 Portland Square, Bristol, BS2 8ST
>
> Registered in England & Wales, Company No. 11034665 - VAT Number. 280 6776 73
> Privileged/Confidential Information may be contained in this message.
> If you are not the addressee indicated in this message (or responsible for delivery of the message to such person),
> you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
> Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions,
> conclusions and other information in this message that do not relate to the official business of NetPilot Global Ltd shall be understood as neither given nor endorsed by it.
>
> NetPilot Global Ltd is committed to GDPR compliance.
> We are also committed to helping our customers comply with the GDPR by providing stringent privacy and security protections that are built into our service and contracts.
> Any personal information that NetPilot Global Ltd may collect (including, but not limited to, your name, company and email address) will be collected, used and held in accordance with the provisions of GDPR and your rights under that Act.
>
>
> _______________________________________________
> clamav-users mailing list
> clamav-***@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-***@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
Continue reading on narkive:
Loading...