Upgrading from Ubuntu 20.04 to 22.04 and updating ISPConfig on two connected servers: advice, tips?

Discussion in 'General' started by sprotni, Apr 30, 2024.

  1. sprotni

    sprotni New Member

    Hello everyone! :rolleyes:

    I'm seeking some advice on the following problem:
    I would like to upgrade my Ubuntu 20.04 operating system to 22.04 and also update my ISPConfig version since the current one is not the latest.
    I have two connected servers:
    • Server1: Ubuntu PRO 20.04.6 LTS (Focal Fossa), ISPConfig 3.2.8p2. Services: DNS, web, mail, file, and database.
    • Server2: Ubuntu PRO 20.04.6 LTS (Focal Fossa), ISPConfig 3.2.8p2. Service: Mirror DNS.
    What recommendations and tips can you provide for the upgrade? What should I pay special attention to? How can I make backups? How can I prevent clients from temporarily accessing the server while I am upgrading it, in order to minimize potential issues and data loss such as emails if it becomes necessary to revert to the pre-upgrade state?
    The operating system is kept up to date, regularly updated using apt update and apt upgrade commands.

    Thank you! ;)
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    Follow the tutorial provided by HowToForge. https://www.howtoforge.com/update-the-ispconfig-perfect-server-from-ubuntu-20-04-to-ubuntu-22-04/

    The tutorial describes everything you should be aware of.

    Snapshot both machines if they are VMs.

    While updateing ISPConfig the system should be in maintaince mode to prevent excatly this.

    This is good, but you run a upgrade before the os upgrade anyways :)
    sprotni and ahrasis like this.
  3. sprotni

    sprotni New Member

    Thank you for your help!
    I'll back to you with results.

    So, if I understand correctly, when ISPConfig is put into maintenance mode, neither the webserver nor the receiving and sending of emails will work?
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    No, this will just disable the ability for users to log into ISPConfig.
    sprotni likes this.
  5. sprotni

    sprotni New Member

    Could it be a good solution to only keep ports 53, 8080, 8081, and SSH open while I deal with the update? I will also put ISPConfig into maintenance mode. Additionally, can I specifically ensure that during this time the server cannot receive or send emails, and that the websites are inaccessible?

  6. pyte

    pyte Well-Known Member HowtoForge Supporter

    There's no need to do that. Just put the system into maintenance mode and upgrade as the guide instructs. However if you want to block access to the server for whatever reason, you might want to do this on the firewall itself temporary and not on the ISPConfig server(s)
    sprotni likes this.
  7. sprotni

    sprotni New Member



    I have updated the ISPConfig versions. The update was successful for both the master and the mirror servers. Under the monitor tab, the ISPConfig version has changed for the master server. However, for the mirror server, it hasn't changed. Running the updater again doesn't solve the issue, especially since it now indicates that this is the current version.

    Where could something have gotten stuck?

    The operating system has not been modified in any way yet.

    Thank you!
  8. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Set to five minutes and let it be. It will normally update itself sooner, if not later. If you check via command line shows that it is already upgraded, then it sure is.
    sprotni and pyte like this.
  9. pyte

    pyte Well-Known Member HowtoForge Supporter

    Does the ispconfig update on that 2nd node report any errors?
    sprotni likes this.
  10. sprotni

    sprotni New Member


    There is no error in the ispconfig_install.log, ispconfig.log, cron.log, or any log file.

    The server functions are also working properly, it's just the version that hasn't changed under the monitor tab. It doesn't help if I wait on the page with a 5-minute refresh interval set.
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    sprotni and ahrasis like this.
  12. sprotni

    sprotni New Member

    Wow! :D

    The execution of server.sh and cron.sh did not result in any errors. I cleared the sys_cron table and then ran the server.sh and cron.sh files on the mirror server, and now it perfectly indicates the same version!

    Many thanks for it!!

    I've also attached my MariaDB commands for you, so if anyone encounters the same problem, they can see how to do it. :cool:

    Attached Files:

    ahrasis and till like this.

Share This Page