Centos8: Amavis and Clamd scan not point to same .sock file

Discussion in 'Installation/Configuration' started by DarioL, Apr 19, 2021.

  1. DarioL

    DarioL Member

    I have done a fresh installation of ISPConfig 3.2.x on Centos 8: all work fine but Amavis and Clamd point to different .sock file:
    Code:
    [[email protected] ~]# grep sock /etc/amavisd/amavisd.conf /etc/clamd.d/amavisd.conf|grep -v '#'
    /etc/amavisd/amavisd.conf:  \&ask_daemon, ["CONTSCAN {}\n", "/var/spool/amavisd/clamd.sock"],
    /etc/clamd.d/amavisd.conf:LocalSocket /run/clamd.amavisd/clamd.sock
    For now I have change amavisd.conf and point it to /run/clamd.amavisd/clamd.sock and all work fine.
    Is this a correct solution ?
    It is a know issue or did I do something wrong during the installation?
    Many thanks for reply
    Dario
     
  2. DarioL

    DarioL Member

    I have found which is the reason of my problem.
    From the /etc/redhat-release files I see what the version of my Centos 8 is a "CentOS Stream release 8" and non a "CentOS Linux release 8".
    I have install accidentally a Centos Stream, and not a Centos Linux 8
    Then the install.php thing the server is a "Generic Redhat or compatible", and set the $distid to 'fedora9' in place of 'centos80'
    Will be Centos Stream release 8 certified in the near future?
    Or I must reinstall the server with Centos Linux Release 8?
    Many thanks
    Dario
     
    Last edited: Apr 22, 2021
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    We will probably add it in the future as CentOS 8 will become obsolete.
     
    Last edited: Apr 23, 2021
  4. DarioL

    DarioL Member

    Do you want I fill a request or a bug?
    Or It is sufficient a +1?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    I'll add a feature request in the issue tracker.
     
  6. Taleman

    Taleman Well-Known Member HowtoForge Supporter

Share This Page