ISPConfigOSException error with autoinstaller (Debian 10)

Discussion in 'Installation/Configuration' started by jnrmy, Jun 9, 2021.

Page 2 of 2
  1. jnrmy

    jnrmy New Member

    Hello,

    So there is actually an issue with containers but only on Debian 10. That issue appears to be related to AppArmor, witch is not managed the same way on Debian 9 that it is on Debian 10, causing Bind9 to fail launching. That's why Bind9 was working when I was using Debian 9 on my container but not on Debian 10.
     
    jnrmy, Jun 13, 2021
    #21
  2. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    Do you have workaround info by chance, which the auto installer could set up?
     
    Jesse Norell, Jun 13, 2021
    #22
  3. jnrmy

    jnrmy New Member

    Sadly no. The only thing I know is that AppArmor is taught to not launch in a container.
     
    jnrmy, Jun 14, 2021
    #23
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Try
    Code:
    apt stop apparmor
systemctl disable apparmor
     
    Th0m, Jun 14, 2021
    #24
  5. jnrmy

    jnrmy New Member

    I already tried, but Bind9 needs AppArmor.

    Anyway, I stopped trying to fix this issue. As a temporary solution I will use Debian 9 instead and a manual installation for now. I plan to find a new web hoster by the end of the year.

    Thanks to anyone who helped.
     
    jnrmy, Jun 14, 2021
    #25
    till likes this.
  6. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    ? It doesn't need apparmor to function (eg. I just confirmed 2 nameservers in lxc containers here running debian 10 do not have apparmor). Maybe you meant it "needs" it to comply with your security policy or such? (For what it's worth, I also have some debian 10 nameservers which do have apparmor, but they're in a vm, not a container.)
     
    Jesse Norell, Jun 15, 2021
    #26
    ahrasis and Th0m like this.
  7. zyzzza

    zyzzza Member

    Whoever bumps into this thread . Had same issue today (2022/10/01) due to missing update-inetd (Ubuntu 20 and Ubuntu 18 images on hostinger) . Solved by :
    1. on clean Ubuntu 20 install, run installer with debug option:
    Code:
    wget -O - https://get.ispconfig.org | sh -s -- --use-ftp-ports=40110-40210 --unattended-upgrades --debug
    2. see which line breaks it ant rry running last command manually
    Code:
    apt-get dist-upgrade -o Dpkg::Options::="--force-overwrite" -qq -y
    in my case error here was :
    Code:
    update-inetd: command not found
    3. Reinstall fresh Ubuntu 20 , and BEFORE the ISPCONFIG install , install update-inetd by :
    Code:
    apt install update-inetd
    now your can install ISPConfig as usuall.
     
    zyzzza, Oct 1, 2022
    #27
    ahrasis and till like this.
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Hostinger must have manually uninstalled it on their systems, as it is part of any Ubuntu default installation.
    I'll add this to the auto-installer issue tracker so we can take care to force install it.
     
    till, Oct 1, 2022
    #28
  9. Sir Henry

    Sir Henry Member

    Same error here on a fresh Debian 10 installation on a Strato vServer. Manual install of update-inetd solved it, so it should perhaps be added to the script.
     
    Sir Henry, Nov 15, 2022
    #29
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    till, Nov 16, 2022
    #30
  11. 1337isp

    1337isp New Member

    Hi everyone,

    I got the error "ISPConfigOSException"

    In my case it seems that php sury repository was banning my host (russia).

    You can check your actual php version with php -v then force the version installed on the machine :

    wget -O - https://get.ispconfig.org | sh -s -- --use-ftp-ports=40110-40210 --unattended-upgrades --use-php=7.4

    Then the autoinstaller don't stuck on php8.

    You can add the php8 version later with dpkg or so.
     
    1337isp, Sep 6, 2024
    #31
    till likes this.
Page 2 of 2

Share This Page