oliver at schinagl
Sep 7, 2010, 1:58 AM
Post #7 of 7
Well I booked little progress, I completely uninstalled ClamAV, cleared
the virus-database in /var/lib/clamav and installed clamav again. Config
file is exactly the same, freshclam can now notify clamd normally,
clamdtop works normally, but amavis still fails to connect to the
socket; connection is still refused, the socket, and the path to the
socket are work accessible however.
Thanks for any pointers in the right direction.
On 09/04/10 14:12, Oliver Schinagl wrote:
> I use Gentoo Base System release 1.12.13 as my distro with a hardened
> I can't really say, but I can't seem to find any errors really. I
> attached my debug output, but as mentioned, can't see anything wrong
> with it really.
> I'm not using selinux so not using any of these modes :S
> It is really confusing and baffling, as said, especially since freshclam
> can't even connect to clamav.
> On 09/03/10 10:11, Philippe Camps wrote:
>> What is your linux distribution ?
>> Have you errors when clamd is starting ?
>> Have you selinux in "enforced mode" ? You should try in "permissive mode"
>> Le 02/09/2010 18:40, Oliver Schinagl a écrit :
>>> Hello all,
>>> I've been stuffed with the old and known "(!!)ClamAV-clamd av-scanner
>>> FAILED: run_av error: Too many retries to talk to
>>> /var/run/clamav/clamd.sock (Can't connect to UNIX socket
>>> /var/run/clamav/clamd.sock: Permission denied) at (eval 99) line 326.\n"
>>> I have 2 mail servers running with near identical configs, so I did
>>> cross-check them. Also, I googled and verified my permissions and the
>>> like, but I can't seem to get amavis to talk to clamav.
>>> The socket is world read/write-able, so how this is an issue is
>>> beyond me:
>>> 7of9 var # ls -laF /var/run/clamav/clamd.sock
>>> srw-rw-rw- 1 clamav clamav 0 Sep 2 18:22 /var/run/clamav/clamd.sock=
>>> And supplementary groups are enabled:
>>> 7of9 var # grep Supp /etc/clamd.conf
>>> AllowSupplementaryGroups yes
>>> Amavis and clamav aren in each others groups:
>>> and when I 'cat' as user amavis, I do get access to the socket (I
>>> cat: /var/run/clamav/clamd.sock: No such device or address
>>> File: `/var/run/clamav/clamd.sock'
>>> Size: 0 Blocks: 0 IO Block: 4096 socket
>>> Device: 903h/2307d Inode: 7921 Links: 1
>>> Access: (0666/srw-rw-rw-) Uid: ( 116/ clamav) Gid: (10024/ clamav)
>>> Access: 2010-09-02 18:22:43.000000000 +0200
>>> Modify: 2010-09-02 18:22:43.000000000 +0200
>>> Change: 2010-09-02 18:22:43.000000000 +0200
>>> Which I think is what is supposed to happen?
>>> The thing that is strangest though, is that freshclam can't even connect
>>> to the socket:
>>> Received signal: wake up
>>> ClamAV update process started at Thu Sep 2 09:30:35 2010
>>> main.cvd is up to date (version: 52, sigs: 704727, f-level: 44, builder:
>>> Downloading daily-11776.cdiff [100%]
>>> daily.cld updated (version: 11776, sigs: 118691, f-level: 53, builder:
>>> bytecode.cld is up to date (version: 40, sigs: 9, f-level: 53, builder:
>>> Database updated (823427 signatures) from database.clamav.net (IP:
>>> WARNING: Clamd was NOT notified: Can't connect to clamd through
>>> I checked/tried all obvious answers but that's just not it I think.
>>> Any other pointers?
>>> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net