On Wed, 2012-06-27 at 13:12 -0700, jdow wrote:
> On 2012/06/27 12:43, S.Tindall wrote:
> > On Wed, 2012-06-27 at 12:31 -0700, jdow wrote:
> >> Latest clamav update main.cvd is an empty file. It apparently should not be
> >> empty. For two days now I've gotten this message:
> >>
> >> ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file
> >>
> >> {^_^}
> >
> > Run freshclam and then restart clamd.
> >
> > Steve

> rerunning freshclam gives:
> ClamAV update process started at Wed Jun 27 13:11:13 2012
> main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)
> daily.cld is up to date (version: 15092, sigs: 222617, f-level: 63, builder: 
> ccordes)
> bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo)
> WARNING: [LibClamAV] cli_cvdverify: Can't read CVD header
> ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file
> Corrupted database file renamed to /var/clamav/main.cld.broken
> Trying again in 5 secs...


> ClamAV update process started at Wed Jun 27 13:11:19 2012
> main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)
> daily.cld is up to date (version: 15092, sigs: 222617, f-level: 63, builder: 
> ccordes)
> bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo)
> 
> 
> It's broken, Jim! (Sorry Star Trek)
> 
> {^_^}

You "fixed" it with freshclam. As per the final section, main.cvd,
daily.cld and bytecode.cld are now up to date.

If /var/clamav/*broken bothers you, then delete it/them.

# rm /var/clamav/*broken

# ls /var/clamav/
bytecode.cld  daily.cld  main.cvd  mirrors.dat


At least on my EL6 systems, those satisfy clamd.

# service clamd restart
Stopping Clam AntiVirus Daemon:    [  OK  ]
Starting Clam AntiVirus Daemon:    [  OK  ]


Steve