Bullseye for ISPConfig

Discussion in 'Installation/Configuration' started by brainsys, Aug 16, 2021.

  1. brainsys

    brainsys Member

    Debian 11 was released Saturday and I see my favourite cloud hoster already has it as an option.
    I tried installing ISPConfig 3.2.5 on a VM pre-release of Debian 11. The auto-installer script reject it on sight as expected. So I followed the Debian 10 Perfect Server guide. It all seemed to work - except phpmyadmin which I installed from the apt repository rather than the manual installation outdated version. I rely on phpMyAdmin to sort out a lot of configuration issues. It might just be mistyping. But this leads me to the question:

    "Is it worth debugging my installation - or will a tutorial/new script be along in the not too distant future?"

    While it, hopefully, is not an urgent question for me - if I had to do a re-install or add another server - it would be good to go with Debian 11 if only that it comes with php 7.4 native so we don't get into the sury multi-version complications if we want to support php beyond this December (when 7.3 goes EOL).

    Another bonus is you can support a later version of Roundcube that has a new default theme that you can sensibly use on a mobile/tablet!
     
    Gwyneth Llewelyn likes this.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Debian 11 support will get added to ISPConfig and also to the auto installer.
     
  3. brainsys

    brainsys Member

    Thanks. I have solved the phpmyadmin issue. DON'T install with apt but follow the Debian 10 instructions. I substituted 5.1.1 for 4.9.0.1 to bring it up it date and it all worked. So I don't think you will have to do much of a rewrite!

    Let me know if you need a beta tester.
     
    ahrasis and till like this.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    I've planned to update the guide in the way to switch from mpm_prefork to mpm_event and also use Rspamd as default. But good to know that the instructions are still valid. That's one of the benefits of Debian: continuity - which makes admin's life much easier :)
     
  5. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Offhand, what issues did you run in to there? Installing a newer, packaged version is normally preferable to installing an old version from source.
     
  6. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Sorry, I misread your comments saying you did update the newer version (than bullseye, which includes 5.0.4). Still curious why the packaged phpmyadmin wouldn't work...
     
  7. brainsys

    brainsys Member

    It looks like a location issue. This from the apache2 log:
    PHP Fatal error: require_once(): Failed opening required 'PhpMyAdmin/MoTranslator/autoload.php' (include_path='.') in /usr/share/phpmyadmin/autoload.php on line 2

    MoTranslator was present at /usr/share/php/PhpMyAdmin/ but it looks like it wasn't being found by /usr/share/phpmyadmin/autoload.php. Google suggests this is an issue not confined to ISPConfig use.
     
  8. GhostRider

    GhostRider New Member

    Hi Till, I can't wait to see the new version, really good work and very grateful. Thank you so much. :D
    An approximate date of the script?
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    We are working on Debian 11 support in ISPConfig while writing the new tutorial and I will publish it when it's finished :)
     
  10. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    For what it is worth, my opinion on upgrading OS is that I plan to update my production Debian 10 servers to Debian 11 when the 11.2 version is released. Then I trust the new OS works and upgrading goes smoothly. It is possible releasing 11.2 goes to next year, so for me there is no rush getting ISPConfig support for Bullseye.
    I did install Debian 11 yesterday to test BTRFS, however. Went smootly and works as expected.
     
    ahrasis likes this.
  11. brainsys

    brainsys Member

    Maintaining perfect comparability with Debian Release Management:
    "quando paratus est" :)
     
  12. bch

    bch Member

    You probably already know, but webalizer has been replaced by awffull
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    Thank you for the info.
     
  14. brainsys

    brainsys Member

    Replaced? I note the last release of awfful was in 2008 and webalizer in 2013. Both abandoned? Is there not a better more modern option with output that looks as though it came from this millennium?
     
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    That's why ISPConfig supports goaccess now besides awstats.
     
  16. brainsys

    brainsys Member

    I hadn't noticed that at the bottom of the dropdown list having always used awstats. Thanks.

    I followed the Perfect Tutorial instructions to add goaccess. <domain>/stats produces a 404. Is this because it needs to be installed before ISPConfig or does it rely on a cron job yet to be executed?

    Maybe worth making a Perfect Tutorial note that goaccess is not available for ARMH & ARM64 servers unlike cross-platform awstats.
     
  17. till

    till Super Moderator Staff Member ISPConfig Developer

    It needs to be installed first and then you have to wait 24h after switching a site to goaccess before you can use it.
     
  18. lollollollol

    lollollollol Member

    Hello everyone,

    For what it's worth, Debian 10 to 11 is the simplest upgrade I've ever seen ...
    I already upgrade 3 servers (from Buster to Bullseye) without almost any problems.

    Warning: It is not a good idea and it was at my own risks. ;)

    The only problem was the change from MariaDB 10.3 to 10.5. During the upgrade apt "forgot" to install the new version of Mariadb ...
    This was simply fixed with:
    # apt install mariadb-server mariadb-client
     
  19. brainsys

    brainsys Member

    Did you have the sury php7. 3/7.4 setup and was this preserved through upgrade? Has ISPConfig moved from using the former to the latter?

    I always install the latest combination on new servers. Old servers I skip the next generation so went Jessie to Buster before a re-install. Buster will go Bookworm and so on. That gives servers a four year life. I don't like the risk of a failed upgrade or hidden issues when running other folk's sites and email.

    Whereas desktops are a different matter.
     
  20. lollollollol

    lollollollol Member

    Salut,

    Yes no problem with Sury. I modified the sury.list (Buster to Bullseye) and I upgraded php with all the rest.
    Code:
    # update-alternatives --config php
    Il existe 5 choix pour l'alternative php (qui fournit /usr/bin/php).
    
      Sélection   Chemin                Priorité  État
    ------------------------------------------------------------
      0            /usr/bin/php.default   100       mode automatique
      1            /usr/bin/php.default   100       mode manuel
      2            /usr/bin/php7.0        70        mode manuel
      3            /usr/bin/php7.3        73        mode manuel
    * 4            /usr/bin/php7.4        74        mode manuel
      5            /usr/bin/php8.0        80        mode manuel
    
    Appuyez sur <Entrée> pour conserver la valeur par défaut[*] ou choisissez le numéro sélectionné :
    
    # update-alternatives --config php-cgi
    Il existe 4 choix pour l'alternative php-cgi (qui fournit /usr/bin/php-cgi).
    
      Sélection   Chemin               Priorité  État
    ------------------------------------------------------------
      0            /usr/bin/php-cgi8.0   80        mode automatique
      1            /usr/bin/php-cgi7.0   70        mode manuel
      2            /usr/bin/php-cgi7.3   73        mode manuel
    * 3            /usr/bin/php-cgi7.4   74        mode manuel
      4            /usr/bin/php-cgi8.0   80        mode manuel
    
    Appuyez sur <Entrée> pour conserver la valeur par défaut[*] ou choisissez le numéro sélectionné :

    IspConfig didn't see the difference as they are the same versions in the Sury repositories.
    Code:
    # apt policy php7.4
    php7.4:
      Installé : (aucun)
      Candidat : 7.4.23-1+0~20210826.50+debian11~1.gbpb41c6a
     Table de version :
         7.4.23-1+0~20210826.50+debian11~1.gbpb41c6a 500
            500 https://packages.sury.org/php bullseye/main amd64 Packages
         7.4.23-1+0~20210826.50+debian10~1.gbpb41c6a 500
            500 https://packages.sury.org/php buster/main amd64 Packages
         7.4.21-1+deb11u1 500
            500 http://deb.debian.org/debian bullseye/main amd64 Packages
    No one likes risks.
    I had tested several times in a virtual machine before doing it on a test live server...
    Of course, Debian must be as close as possible to its original configuration ...
    Franken-Debian must be avoided absolutely. https://wiki.debian.org/DontBreakDebian

    I advise to take it slow:

    Code:
    apt update
    apt upgrade --without-new-pkgs
    reboot
    apt upgrade
    reboot
    apt full-upgrade
    apt install mariadb-server mariadb-client
    reboot
     
    Steini86 likes this.

Share This Page