Submitted by tauvix on Mon, 07/05/2010 - 18:12 Pro Licensee
I have a brand new install of Virtualmin on a clean (no optional package) installation of CentOS 5.5.
During the install configuration wizard, I selected to enable the clamav server. This failed. I then went to the Spam and Virus Scanning Page and attempted to enable it there. I get the following message:
Configuring and enabling the ClamAV scanning server .. Creating ClamAV configuration file /etc/clamd.d/virtualmin.conf .. .. done Fixing ClamAV bootup action /etc/rc.d/init.d/clamd-virtualmin .. .. already done
Linking ClamAV server to /usr/sbin/clamd.virtualmin .. .. done
Starting ClamAV server and enabling at boot .. .. failed to start : Starting clamd.virtualmin: ERROR: Please define server type (local and/or TCP). [FAILED]
.. all done
Status:
Closed (fixed)
Comments
Submitted by tauvix on Mon, 07/05/2010 - 18:26 Pro Licensee Comment #1
subscribing...
Submitted by JamieCameron on Mon, 07/05/2010 - 20:04 Comment #2
Sounds like Virtualmin isn't setting up clamd properly.
Could you attach the /etc/clamd.d/virtualmin.conf file to this bug report?
Submitted by tauvix on Mon, 07/05/2010 - 20:29 Pro Licensee Comment #3
Here you go.
Submitted by JamieCameron on Tue, 07/06/2010 - 00:40 Comment #4
Thanks .. looks like the config file format has changed in the new ClamAV version.
If you remove the # in the line :
#LocalSocket /var/run/clamd.virtualmin/clamd.sockdoes ClamAV then start OK?
Submitted by JamieCameron on Tue, 07/06/2010 - 02:01 Comment #5
I did a test install on a fresh CentOS 5.5 system and confirmed this bug, and the work-around. You may also need to create the /var/run/clamd.virtualmin directory with the commands :
mkdir /var/run/clamd.virtualminchmod 755 /var/run/clamd.virtualmin
chown nobody: /var/run/clamd.virtualmin
The 3.80 Virtualmin release will fix this problem by doing this automatically.
Submitted by tauvix on Tue, 07/06/2010 - 22:04 Pro Licensee Comment #6
Great. That resolved the issue thanks!