In article <4fec9cef.7030...@ucsd.edu>,
 Trevor Cooper <tcoo...@ucsd.edu> wrote:

> Recently we've been getting failures from freshclam of the following type 
> reported in Logwatch...
> 
> /etc/cron.daily/freshclam:
> 
> ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file
> 
> Since we install/reinstall with a 'scorch-the-earth' script I did so on my 
> machine and found
> 'similar' errors during freshclam after reinstall. Here is an excerpt from 
> the install/reinstall
> script output...
> 
> ...
> #     Installing clamav clamav-db clamd clamtk and dependencies...
> Installed:
>   clamav.x86_64 0:0.97.5-2.el5.rf        clamav-db.x86_64 0:0.97.5-2.el5.rf   
>        clamd.x86_64 0:0.97.5-2.el5.rf       
>   clamtk.noarch 0:4.25-1.el5.rf         

You are using the packages produced by Dag Wieers, so he's the person to 
contact.

There is a packaging "error" in the latest version, if you do

# rpm -qlv clamav-db

you will see that there are zero-length .cld files installed, this is 
what freshclam is whinging about. Freshclam will rename it and try 
again, but as a side-effect you have to restart the daemon because the 
zero-length files kill it as soon as the RPM install causes the restart!

Dave


-- 
Dave Hill - dave at hillcroft dot org dot uk

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to