Re: [Clamav-users] Starting clamd [FAILED]

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Moray Henderson (ICT)
Date:  
To: ClamAV users ML
Subject: Re: [Clamav-users] Starting clamd [FAILED]
>From: Török Edwin [mailto:]
>On 2008-07-16 12:58, Gavin Bartle wrote:
>> Hi, as far as i know clamd-0.93.3-1.el5.rf.i386.rpm is the latest
>> version , and i have that installed.
>
>Do you have SELinux enabled?
>If yes, you'll need to check that the paths configured in its policy is
>correct for clamav.


Yes, we had problems like this too. Default EL5 SELinux policy wants the clam files in /var/lib/clamav, but the last .el5.rf.i386.rpms I saw (not 0.93.3, though) still put the files in /var/clamav, which SELinux prevents clam from accessing. I modified our clam config files to move everything to /var/lib/clamav.

I'm not sure whether /tmp/clamd.socket is going to work either - check /var/log/messages and /var/log/audit/audit.log for avc messages that mention clamd.socket.

Not sure about dansguardian either: EL5 SELinux comes with a policy to get amavis and clamd working together, but I had to write my own policy module to get clamd to work with MIMEDefang.

Alternatively, you could remove clam from SELinux control using

setsebool -P clamd_disable_trans=1


Moray.
"To err is human. To purr, feline"
http://members.aol.com/edgwddirk

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml