On Fri, 25 Feb 2005 10:24:46 -0500 in [EMAIL PROTECTED] Scott Plumee <[EMAIL PROTECTED]> wrote:
Daniel A. Deitch wrote:
I have ClamAV 0.82 installed on a Verio VPSv2 FreeBSD server ... works fine ... scans, cleans, deletes ... the works.
My problem is with freshclam ... the problem has been occurring since 0.80, 0.81, 0.82 and 0.82_1
I have the following flag in my /etc/rc.conf file:
clamav_freshclam_flags="--config-file=/usr/local/etc/freshclam.conf --checks=12 --datadir=/usr/local/share/clamav --daemon-notify=/usr/local/etc/clamav.conf --log=/var/log/clamav/freshclam.log"
I can't say for sure, but I've got the same setup and I've always noticed that if I hadn't upgraded to the latest release yet, I would get the same error messages in the log files after a certain period of time. I assumed that the update servers were blacklisting IPs that had out of date versions after a certain point, as they did when they required you switch to the new DNS configuration options in the freshclam.conf file around version .81 or so. Upgrading to the latest ported version always got it working for me. Not much help, but that was what worked for me.
Looks to me like the OP has either an odd DNS problem or a permissions problem somewhere. I think the upgrade advice has only worked by coincidence.
You were correct. I have not set permissions on the /var/db/clamav directory to be writeable by the user clamav was running as. Enabled verbose logging, saw the problem, made the change, and now I'm happy as a clam.
I should probably get kicked off the list for that pun. Thanks again for the help.
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
