Amavisd ClamDscan

"Wayne Spivak" <[email protected]>
Newsgroups gmane.mail.virus.amavis.user
Organization SBANetWeb
Message-ID <[email protected]>
I went to install ClamDscan (emphasis mine).

I commected out all ClamAV or  Clamscan lines.

I uncommented this:

### http://www.clamav.net/ - using remote clamd scanner as a backup
   ['ClamAV-clamdscan', 'clamdscan',
 # "--stdout --no-summary --config-file=/etc/clamd-client.conf {}",
  "--stdout --no-summary --config-file=/etc/clamd.d/clamd.conf {}",  <--
changed file name
   [0], qr/:.*\sFOUND$/m, qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],


This is the errors I'm getting.:


Apr 25 13:40:14 mcq amavis[32237]: (32237-01) Checking: MVAo_dkuB45a
[209.85.128.42] <[email protected]> -> <[email protected]>
Apr 25 13:40:14 mcq amavis[32237]: (32237-01) (!)WARN: all primary virus
scanners failed, considering backups
Apr 25 13:40:14 mcq amavis[32237]: (32237-01) (!)run_av (ClamAV-clamdscan)
FAILED - unexpected exit 2, output="ERROR: Could not connect to clamd on
LocalSocket /run/clamd.amavisd/clamd.sock: No such file or directory"
Apr 25 13:40:14 mcq amavis[32237]: (32237-01) (!)ClamAV-clamdscan av-scanner
FAILED: /usr/bin/clamdscan unexpected exit 2, output="ERROR: Could not
connect to clamd on LocalSocket /run/clamd.amavisd/clamd.sock: No such file
or directory" at /usr/share/perl5/vendor_perl/Amavis/AV.pm line 955.
Apr 25 13:40:14 mcq amavis[32237]: (32237-01) (!!)AV: ALL VIRUS SCANNERS
FAILED

Scan.conf has:

PidFile /var/run/clamd.scan/clamd.pid
LocalSocket /var/run/clamd.scan/clamd.sock
LocalSocketGroup virusgroup
User clamscan

Currently clamd@scan service is running and clam.freshclam.

Permission on the files
drwxr-xr-x  2 clamscan virusgroup   80 Apr 25 13:36 .
drwxr-xr-x 52 root     root       1480 Apr 25 13:37 ..
-rw-r--r--  1 root     root          6 Apr 25 13:36 clamd.pid
srw-rw-rw-  1 clamscan virusgroup    0 Apr 25 13:36 clamd.sock

Stumped.

Thanks!!!

Wayne
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.