On Thu, 24 Mar 2005 at 12:18:24 -0500, Scott Plumee wrote:
Steffen Winther Soerensen wrote:
Sounds very much like your network connection and resolve lib isn't in place at this time, try to delay running freshclam until network connection is in place.
Not sure if this is the best way to do it, but I added a 30 second delay to the /usr/local/etc/rc.d/clamav-freshclam.sh script. However, still did not solve it - same error on a reboot. It's a virtual server, and the entire reboot process only takes about 15 seconds before I can get back in via SSH, so that doesn't seem to be it.
Is there a better way to do this I should try?
Maybe insert 'ping -c 5 database.clamav.net > path/somefile' in the script just before invoking freshclam and see what you get as the output.
Note that I don't know whether all database mirrors answer to ping requests, so you can receive no reply anyway. That's why you can replace 'database.clamav.net' with some hostname which you know is pingable. Use a hostname, not an IP address, so that you can notice a DNS-related problem during startup in case it's the reason.
Changed the relevent part of rc.conf to read: ping -c 5 database.clamav.net > /path/to/the/file/clamtest.log clamav_freshclam_enable="YES"
After a reboot, the file reads: PING db.other.clamav.net (80.95.80.7): 56 data bytes 64 bytes from 80.95.80.7: icmp_seq=0 ttl=50 time=115.091 ms
I tried several more reboots and sometime the hostname ping works, sometimes it drops a few packets, sometime no response at all. The IP ping of google.com works each time, so it looks like it might well be an issue with the resolving of the hostname.
I'm going to try it with a cron job and see what happens. Thanks for the help so far.
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
