Originally Posted by www
I had the same problem. Commenting out
in /etc/clamd.conf allowed clamd to restart.
Then I noticed that there was a new version of clamd available through yum. Installing that seems to have fixed the problem and clamd now restarts even with the lines above uncommented.
I don't want to be a wet blanket, but you haven't fixed the problem, you've ignored it. What you did was to turn off the socket by which 99% of local programs will submit data to be scanned for viruses by clamav. To be perfectly honest, while it is possible to configure clamav to accept submissions via tcp that's not too popular right now.
Clamav was complaining that either /var/run/clamd
/clamd.sock (the bolded directory) didn't exist or it had no rights to read/create/modify etc. in that directory.
#chown root:<same group name that clamd runs as
You also might want to un-comment those two lines in clamd.conf.