Got nothing in var log changed to log to /var/log/clamd.robpatton.log restarted still nothing in logs, guess thats the wrong conf file
The config file that is used by clamav is normally somewhere in /etc/clam* It might be that the file has a different name on your system, the "official" name is clamd.conf as you can see in the manpage, but some distributions like to rename files.
Clam.d is the only folder in etc [root@webhost etc]# cd clamd.d/ p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 18.0px Menlo; color: #000000; background-color: #ffffff} span.s1 {font-variant-ligatures: no-common-ligatures} [root@webhost clamd.d]# ls -l total 28 -rw-r--r-- 1 root root 546 Nov 23 2015 amavisd.conf -rw-r--r-- 1 root root 22239 May 20 2016 scan.conf [root@webhost clamd.d]# scan.conf now has LogFile /var/log/clamd.scan uncommented and restarted. See the error in maillog, but do not see a /var/log/clam.scan file yet
amavisd.conf: # Use system logger. LogSyslog yes # Specify the type of syslog messages - please refer to 'man syslog' # for facility names. LogFacility LOG_MAIL # This option allows you to save a process identifier of the listening # daemon (main thread). PidFile /var/run/clamd.amavisd/clamd.pid # Remove stale socket after unclean shutdown. # Default: disabled FixStaleSocket yes # Run as a selected user (clamd must be started by root). User amavis # Path to a local socket file the daemon will listen on. LocalSocket /var/run/clamd.amavisd/clamd.sock
The error that I'm seeing: connect to /var/run/clamav/clamd.sock failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.sock: No such file or directory strikes me as odd since its looking at /var/run/clamav/clamd.sock while the amavis config uses /var/run/clamd.amavisd/clamd.sock Is this the problem?
In var/run/clamd.amavisd [root@webhost run]# cd clamd.amavisd/ [root@webhost clamd.amavisd]# ls clamd.pid clamd.sock in var/run/clam.scan this is nothing. There is no such /var/run/clamav/clamd.sock
That appears to be the same problem I have, and the symlink seems to fix the error, until I reboot. But at least I know how to prop it up for the time being. Thanks, glad to understand what happened. Have realized Centos may not be as great as I had thought.
