On Mar 11, 2010, at 9:35 AM, Maurício Ramos wrote:
List, we are working on implementing an antivirus solution (samba-
vscan + clamav)on our samba shares. We performed the steps mentioned
on some guides we found in Portuguese and things seems to be
installed ok. But when we make a test and try to access a share,
every file on it is not accessible (though we can mount the share)
and after looking at /var/log/messages we see the following:
...
Mar 11 10:56:51 rhel5 smbd_vscan-clamav[5238]: samba-vscan (vscan-
clamav 0.3.6b) registered (Samba 3.0), (c) by Rainer Link,
OpenAntiVirus.org
Mar 11 10:56:51 rhel5 smbd_vscan-clamav[5238]: samba-vscan (vscan-
clamav 0.3.6b) connected (Samba 3.0), (c) by Rainer Link,
OpenAntiVirus.org
Mar 11 10:56:51 rhel5 smbd_vscan-clamav[5238]: INFO: connect to
service tmp by user mauramos
Mar 11 10:57:10 rhel5 smbd_vscan-clamav[5238]: ERROR: can not
connect to clamd (socket: '/home/clamav/clamd.sock')!
Mar 11 10:57:10 rhel5 smbd_vscan-clamav[5238]: ERROR: can not
communicate to daemon - access denied
Mar 11 10:57:10 rhel5 smbd_vscan-clamav[5238]: ERROR: can not
connect to clamd (socket: '/home/clamav/clamd.sock')!
Mar 11 10:57:10 rhel5 smbd_vscan-clamav[5238]: ERROR: can not
communicate to daemon - access denied
...
What user is smbd_vscan-clamav running as? The problem looks like
smbd_vscan-clamav does not have access to the socket.
You can try opening the permissions on the directory and see if that
helps and tighten the permissions once you have worked it all out.
I run samba and clamav but have not implemented the vscan-clamav option.
I need to upgrade / rebuild the system so maybe I will add that as and
option.
Jim
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
