Test Andrea wrote:
Dear List,
This is my configuration:
CentOS 4.8
# clamdscan -V
ClamAV 0.95.3/10861/Thu Apr 29 04:16:19 2010
# sigtool --info=/home/amavisd/clamav/main.cld
File: /home/amavisd/clamav/main.cld
Build time: 15 Feb 2010 09:54 -0500
Version: 52
Signatures: 704727
Functionality level: 44
Builder: sven
# sigtool --info=/home/amavisd/clamav/daily.cld
File: /home/amavisd/clamav/daily.cld
Build time: 28 Apr 2010 22:16 -0400
Version: 10861
Signatures: 54573
Functionality level: 51
Builder: guitar
From few days ago i had these errors into the freshclam.log:
http://nopaste.info/6ce68caae7.html
Freshclamd running with the -d (Daemon) option at the boot of the Server.
I have this problem only for the incremental update of daily.cld.
Yesterday i tried to stop freshclam, remove daily.cld and after the
restart the 1st update of the daily.cld worked without errors.
I have the same problem on another server with Clamav 0.95.2 on Centos
5.4.
I'm seeing a similar problem, and I believe it's another issue caused by
ClamAV's aggressive policy of disabling older software versions. If I
run freshclam with debug options I see errors like this:
Ignoring mirror 217.135.32.99 (has connected too many times with an
outdated version)
Ignoring mirror 81.91.100.173 (has connected too many times with an
outdated version)
Ignoring mirror 163.1.3.8 (has connected too many times with an outdated
version)
...and so on for the other mirrors I'm using.
I have two scanning boxes running ClamAV built from source, which I've
updated to 0.96, and two boxes running Debian Lenny, with ClamAV
installed from the packages in the volatile repository. The Debian boxes
are running Debian's most recent package, 0.95.3; I only see this
problem on those boxes.
The 'outdated version' error appears to be the handling they added to
stop older versions (which couldn't do incremental updates) from
hammering the mirrors. I guess they're now applying it to all versions
except for the most recent, even if they do incremental updates.
If you're running an OS that hasn't packaged 0.96 yet, I think you now
need to build ClamAV from source if you want timely signature updates.
The odd thing is the ClamAV website still recommends using the Debian
Volatile packages.
regards,
Adam
--
--------------------------------
Adam Stephens
Network Specialist - Email & DNS
adam.steph...@bristol.ac.uk
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
