Bug#426117: exim4: unable to connect /var/run/clamav/clamd.ctl, but /var/run/clamav/clamd.ctl exists

[Marc Haber]

On Sat, May 26, 2007 at 02:10:07PM +0200, Axel Ludszuweit wrote:
> I have the below described behaviour on my Debian testing 
> installation.
> I use the exim4 mail packet with the clamd virus scanner,
> spam assassin and fetchmail.
> After booting I get the following messages in
> file /var/log/exim4/paniclog:
> 
> 2007-05-26 13:34:29 1HruXU-0001pP-Il malware acl condition: clamd:
> unable to connect to UNIX socket /var/run/clamav/clamd.ct
> l (No such file or directory)

What happens when you connect to the daemon from a shell? Are the
privileges on the directory OK?

drwxr-xr-x 13 root   root   4,0K 2002-07-23 12:35 /var//
drwxr-xr-x 13 root   root   4,0K 2007-05-26 07:44 /var/run//
drwxr-xr-x  2 clamav clamav 4,0K 2007-05-02 12:44 /var/run/clamav//
srwxrwxrwx  1 clamav clamav    0 2007-05-02 12:44 /var/run/clamav/clamd.ctl=


> This behaviour began, without any modifying of configuration after a
> update
> made by synaptic.

Which packages got updated during that update?

> I have modified the clamd start script, so that after starting the
> script
> waits until the socket exists. But the same behaviour as before.
> I hope, the error is not the user.

Can you strace clamd and/or exim and see whether this gives any
conclusive information?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190