Some updates to the yum-sent clamav-milter.conf and (to a lesser extent) clamd.conf may be necessary.
After an automatic yum-update of the clamd family on RHEL, there’s a disparity in the way clamav-milter listens and clamd services the socket or port connection — clamav-milter doesn’t know what to go with (local socket on unix:/tmp/clamav.socket or tcp:127.0.0.1) – so you need to tell it. Otherwise, you get messages such as the below in you clamav-milter.log:
clamav-milter[5149]: No clamd server appears to be availableERROR: Failed to initiate streaming/fdpassing
So make sure the ClamdSocket in clamav-milter.conf points to the LocalSocket that clamd.conf says it’s broadcasting on. So if clamd.conf is
LocalSocket /tmp/clamd.socket
clamav-milter.conf should have
ClamdSocket unix:/tmp/clamd.socket
Else, if you’re on LocalSocket on 127.0.0.1 on the default port, just set ClamdSocket as below:
ClamdSocket tcp:127.0.0.1
Also, be sure to do an
sa-update
Simple, eh? But you knew that already
REFERENCES
http://blog.sven.co.za/2010/04/03/clamav-error-yum-upgrade-to-0-96-clamd-and-clamav-milter/
