Hi,
I'm running an amavisd-new installation with clamav and spamassassin. When I
set it up, I followed the recipe from the Centos wiki except I used the user
name clam instead of clamav for the group.
Recently I ran a yum upgrade, which I think must've upgraded either clamav or
amavisd-new, not sure. The upshot is that now I see the following in my
LogWatch log:
*Unmatched Entries**
(!!)WARN: all primary virus scanners failed, considering backups: 3 Time(s)
(!)ClamAV-clamd: Can't connect to UNIX socket /var/run/clamav/clamd:
Connection refused, retrying (2): 3 Time(s)
(!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to
/var/run/clamav/clamd (Can't connect to UNIX socket /var/run/clamav/clamd:
Connection refused) at (eval 92) line 373.\n: 3 Time(s)
And when I try to start clamav by hand,
root@fortapache init.d]# service clamd start
Starting Clam AntiVirus Daemon: ERROR: Can't open /var/log/clamav/clamd.log in
append mode (check permissions!).
ERROR: Can't initialize the internal logger
[FAILED]
I looked at /var/log/
root@fortapache clamav]# ls -l
total 300
-rw-r--r-- 1 clamav clamav 3556 Jul 11 13:00 clamd.log
-rw-r--r-- 1 clam clam 31747 Jun 15 18:24 clamd.log.1
-rw-r--r-- 1 clamav clamav 204 Jul 11 13:01 freshclam.log
-rw-r--r-- 1 clam clam 3474 Jun 19 04:02 freshclam.log.1
I see that the logs are now owned by clamav. chmodding them to clam doesn't
seem to help. E.g,
[root@fortapache clamav]# service clamd start
Starting Clam AntiVirus Daemon: Bytecode: Security mode set to "TrustSigned".
LibClamAV Warning: **************************************************
LibClamAV Warning: *** The virus database is older than 7 days! ***
LibClamAV Warning: *** Please update it as soon as possible. ***
LibClamAV Warning: **************************************************
ERROR: LOCAL: Socket file /var/run/clamav/clamd could not be bound: Permission
denied
[FAILED]
My guess is that the username under which clamd or amavisd are running got
confused. I checked both conf files. I'm stumped.
Bob
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
