Amavisd and Clamav socket problems

Discussion in 'Installation/Configuration' started by MaxE, Dec 17, 2017.

  1. MaxE

    MaxE New Member

    Hello Til,
    Hope you can help me...

    I've had a successfully working ISPConfig 3 installation for a little while now. However, I have updated to ISPConfig 3.1.9 recently - and this is when things start going very wrong for me. The Amavisd - whatever I try to do - refuses to operate correctly:

    In /var/log/maillog, I get a loads of:

    Dec 17 16:40:44 vds amavis[4921]: (04921-01) (!)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
    Dec 17 16:40:44 vds amavis[4920]: (04920-01) (!)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
    Dec 17 16:40:44 vds amavis[4921]: (04921-01) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamav/clamd.sock, retrying (2)
    Dec 17 16:40:44 vds amavis[4920]: (04920-01) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamav/clamd.sock, retrying (2)
    Dec 17 16:40:50 vds amavis[4921]: (04921-01) (!)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
    Dec 17 16:40:50 vds amavis[4920]: (04920-01) (!)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
    Dec 17 16:40:50 vds amavis[4921]: (04921-01) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.sock (All attempts (1) failed connecting to /var/run/clamav/clamd.sock) at (eval 114) line 608.\n
    Dec 17 16:40:50 vds amavis[4920]: (04920-01) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.sock (All attempts (1) failed connecting to /var/run/clamav/clamd.sock) at (eval 114) line 608.\n

    Not happy. Consequently, no email has been delivered for a while now (although luckily it is queued).

    Some stats:
    Server is:
    Linux xxxxxxxxxxx 2.6.32-696.16.1.el6.x86_64 #1 SMP Wed Nov 15 16:51:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

    Amavis is showing as: amavisd-new-2.9.1 (20140627)
    Clamav is showing as: ClamAV 0.99.2/24137/Sun Dec 17 13:09:36 2017
    selinux is permissive

    I understand that the problem probably lies around the way that amavis.conf is configured, but I'm getting rather stuck.

    Any help would be apprechiated.

    Thanks


    Max
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The problem seems to be ClamAV and not amavis. Try to restart the clamav server / daemon and if it does not start, check the ClamAV log to see why it fails.
     

Share This Page