My friend had this problem with his zimbra installation. After upgrade Clamav to version 0.93 Zimbra service for antivirus could not be started.
Information about the Zimbra Installation
ZIMBRA Release 5.0.5_GA_2201.RHEL5_20080417012110 CentOS5 FOSS edition. Run on Centos 5.
cp: cannot stat `/opt/zimbra/clamav/db/daily.cvd.init': No such file or directory
cp: cannot stat `/opt/zimbra/clamav/db/main.cvd.init': No such file or directory
ClamAV update process started at Mon May 5 05:09:26 2008
main.cvd is up to date (version: 46, sigs: 231834, f-level: 26, builder: sven)
daily.cld is up to date (version: 7025, sigs: 45717, f-level: 26, builder: ccordes)
clamd failed to start
The first two lines Zimbra startup script try to find two files daily.cvd.init and main.cvd.init inside /opt/zimbra/clamav/db but this files is not part of Clamav installation files. It's part of Zimbra, that may act as skeleton files.
What we did, is to run freshclam, to download the latest daily.cvd and main.cvd and copy them into daily.cvd.init and main.cvd.init.
For the error clamd failed to start. We need to view the error in the clamd log /opt/zimbra/log/clamd.log
ERROR: Parse error at line 241: Unknown option ArchiveMaxFileSize.
ERROR: Can't open/parse the config file /opt/zimbra/conf/clamd.conf
This setup is installed with Zimbra that came with Clamav version 0.90. This option ArchiveMaxFileSize under /opt/zimbra/conf/clamd.conf is not reconize under Clamav 0.93.
My friend stuck with this problem because he did not realize that, the Zimbra startup script will still refer to /opt/zimbra/conf/zimbra.conf.in
Any modification that he did to the file /opt/zimbra/conf/clamd.conf was changed by the Zimbra startup script. He should modify /opt/zimbra/conf/zimbra.conf.in and remark the ArchiveMaxFileSize ie #ArchiveMaxFileSize.
and we resolved the Zimbra Antivirus problem.