Clamd Amavisd unix socket question

Question

Level 1

8 points

Clamd Amavisd unix socket question

I have setup user and group 'clamav'

The socket for clamd and amavisd is /var/clamav/clamd.sock and is setup in both clamd.conf and amavisd.conf. Permissions have been set. What I see in my log file though, is:
ClamAV-ClamD: Can't connect to UNIX socket /var/clamav/clamd.sock file does not exist.

It tries a few times and gives up.

Looking at the log file, I also noticed a line at amavisd startup:

Net::Server: Binding to unix socket file /var/amavis/amavisd.sock.

hmmm. So I changed all the above config files to the amavisd.sock.

This seemed to remove the issue of clamd being able to connect to the socket, but now it just seems to take a very long time to come back from checking the email.

Any thoughts?

Thanks
Joe

g4 powerbook, Mac OS X (10.3.9)

Posted on Oct 21, 2006 1:00 PM

Reply

Answer 1

Mezza

Level 1

85 points

Oct 25, 2006 2:09 PM in response to joeboldt

Hi Joe,

I'm no expert on clamd on Mac os x, though I have it happily working on FreeBSD. I got it to work tonight, but I had to explicitly pass clamd the -c flag, eg:

sudo -u clamav clamd -c /etc/clamav.conf

HTH.

iBook Dual USB Mac OS X (10.4.8)

Reply

Answer 2

Mezza

Level 1

85 points

Oct 26, 2006 3:37 AM in response to Mezza

Hi joe,

A couple more updates. BTW, did you need to create a clamav user:group? It should have already existed on OS X 10.4.6 onwards at least (maybe even earlier but I can't remember).

In my /etc/clamav.conf, I have my socket set to "/var/run/clamav/clamd".

In my /etc/amavisd.conf, in the clamd section, I made sure the path to the clamd socket is as above. Excuse me if I'm misinterpreting your post, but I presume you've left '$unix_socketname' in this file to '$MYHOME/amavisd.sock'.

Then I added a launchd script to /Library/LaunchDaemons/org.clamav.clamd.plist, in which I pass clamd the '-c /etc/clamav.conf' argument.

To get launchd to actually detect clamd, I've also enabled the 'Foreground' option in /etc/clamav.conf.

Reply

Answer 3

joeboldt Author

Level 1

8 points

Oct 26, 2006 9:48 AM in response to Mezza

I (sort of) solved my issue. I redid the permissions the same way I set them up when I started. Not sure what I had done differently. Anyway, I still get a "socket in use" error, but only once at startup, after that everything works fine.

Thanks,

Reply