Hi, Ian,
[...]
We have seen the same problem when using db.NL.clamav.net. Looking at
the availability figures for Germany
(http://www.clamav.net/mirrors.html#de) it seems there has only been
one server with a temp. failure tonight (which matches roughly the
time the problem occurred).
What does freshclam daemon do:
a) do one DNS lookup (find multiple A reocrds), and after the first
host fails, take the second host and so on.
b) perform a DNS lookup after each failed connection
It does one DNS lookup (case a), according to the source code (see the
'wwwconnect()' function in "freshclam/manager.c": it does one call to
'gethostbyname()' followed by a 'for' loop, calling 'wait_connect()'
for each returned IP address until one succeeds or it reaches the end
of the list.
In case a) I can't understand why freshclam would fail seven times,
except when there has been a network problem for this host (there
wasn't). In case b) it is possible that the system each time gets the
same IP address (depends on the DNS client library and the way the
results are sorted).
For case a, it does seem strange that all seven IPs were unreachable.
FYI, the system on which ClamAV is running is a Solaris 10 system. I
hope there will be a fix for this in the next release.
You could always run it from a cron job, but yes, a fix would be nice.
Aha. Never thought about running it from cron, but yes, that would be an
option.
Thanks,
/rolf
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
