MLS freshclam fails?

Looks to have been some sort of network issue with reaching your DNS around 4:59, but I'm guessing that cleared up by 7:00.

It's possible that the daily-16968.cdiff file had not yet been uploaded to the mirror sites you were using. I just successfully updated mine, so give it another try.

It's also possible that you are experiencing internet access issues right now.

Apple may or may not get around to updating the ClamAV scan engine any time soon. It's possible to update it manually if you feel a need to by following these instructions: Updating ClamAV on OS X Server >= 10.5.5.

Message was edited by: MadMacs0 who missed the point that you are using MLS.

In terms of the error "Can't query current.cvd.clamav.net"

have a look at /etc/freshclam.conf

# Uncomment the following line and replace XY with your country

# code. See http://www.iana.org/cctld/cctld-whois.htm for the full list.

DatabaseMirror db.us.clamav.net

In my case, I set it up with db.us.clamav.net
but of course edit that appropriately to match your country if not the US.
In your case, it think it would be db.nl.clamav.net - yes ?

davidh wrote:

In terms of the error "Can't query current.cvd.clamav.net"

have a look at /etc/freshclam.conf

# Uncomment the following line and replace XY with your country

# code. See http://www.iana.org/cctld/cctld-whois.htm for the full list.

That won't help with that issue at all as the query is done using by checking whatever DNS the OP is using.

It may help with the last issue, but I've found that it makes no difference at all in my case. Depends mostly on ones geographic location, which freshclam usually does a good job of determining for itself. It is only required to change this if you need to update more than once an hour.

A good reference for freshclam issues is FAQ - CVD.

Well, I offered it precisely because in the past, I'd seen problems updating and there was nothing wrong with DNS in my case. No shortage of various (DNS) lookups working correctly.
Specificying a country code as noted made the error go away.

Not the current version at the/that time, however (some 1-2 years ago).

davidh wrote:

Well, I offered it precisely because in the past, I'd seen problems updating

Sorry, I didn't mean to indicate that it could not help with mirror problems. You are the first US user who has indicated that it did, but I've run into several in other parts of the World, especially Europe where countries are very close together. I've been told by the mirror network admin that some block IP's from other countries, even though they have been instructed not to do so.

But the initial check for current.cvd.clamav.net takes place only to your DNS. Temporary problems with this occur because every time ClamAV publishes a database update it must send out a correction to the DNS system containing details of the most current versions of everything. You can see that by triple clicking, copying and pasting the following line in a Terminal app window after the "$ " prompt:

host -t txt current.cvd.clamav.net

It takes awhile for the DNS system to proliferate these changes throughout the world and it takes ClamAV a few minutes to get the change posted to all of it's ~140 mirror sites, so it is easy for the two systems to be out-of-sync for a short period until both the DNS and mirror networks are fully updated.