Upgrade 3.1 to 3.2 on Ubuntu 14.04 LTS ESM

Discussion in 'Installation/Configuration' started by basmevissen, Oct 19, 2020.

  1. basmevissen

    basmevissen New Member

    Hi,
    Are there problems known that prohibit upgrading to 3.2 on Ubuntu 14.04? I've seen 3.2 does not support 14.04 officially. But my question is whether that is due to a known problem or just because it is an old Ubuntu version that is not tested upon.

    Thanks,

    Bas.
     
  2. ahrasis

    ahrasis Well-Known Member

    So far that we all know Ubuntu 14.04 LTS is no longer supported by Ubuntu itself since April 2019, so I really think it is clearly not wise to keep that version for a production server.
     
  3. basmevissen

    basmevissen New Member

    Ubuntu provides Extended Security Maintenance till 2022. So my server is still current and safe.
     
    Last edited: Oct 19, 2020
  4. ahrasis

    ahrasis Well-Known Member

    Yes. I noted that is the extended security maintenance from Ubuntu which must be opted. https://ubuntu.com/security/esm

    The best to get this supported in 3.2 is to open an issue in the git, so feel free to do that.
     
    Last edited: Oct 19, 2020
  5. michelangelo

    michelangelo New Member

    Ubuntu 14.04 LTS was freely supported until April 2019 and since then there is a service model (ESM) available which supports it until 2022 still with security fixes, for money.

    As far as I know ISPConfig 3.2 requires at least PHP 5.4. In theory even CentOS 6 should actually work with newest ISPConfig 3.2 as long as the "base requirements" are met. Also RHEL 6 supports an extended service model but officially EL6 (CentOS 6) support ends in the coming month.

    However, if one does not really have profound understanding in Linux systems then I do strongly encourage to upgrade to a newer OS version instead of running an older version. No matter if it still gets updates through a paid service model.
     
  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Maybe it would work, but it would be better to upgrade your server and then install ISPConfig 3.2. You can also install a new system following the Perfect Server tutorial and then use the migration tool to migrate your current setup to a new one. This way, you can migrate with 0 downtime (if done correctly).

    More information on the migration tool can be found here: https://www.ispconfig.org/add-ons/ispconfig-migration-tool/
     
  7. basmevissen

    basmevissen New Member

    I'm currently working on buying and configuring a new server that will run CentOS 8 with ISPConfig 3.2. I would like to upgrade my current server (which started as Ubuntu 11.04 and is running fine since 2011!) to 3.2 to ease the migration.
    I'm just trying to get some information on forehand and don't mind to fix a few things. I'll have to do that anyway due to some customisations.
    FYI: I'm quite impressed with the number and speed of updates in ESM. The clamav updates even come quicker than when it was an active release! So I don't really see much reason to hurry an upgrade if there is nothing requiring it.
     
  8. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    There should be no problem with migrating 3.1.15p3 to 3.2. But if 3.1.15p3 worked for you, 3.2 will most likely work aswell. But make a good backup through a snapshot and at the beginning of the update script, so you can eventually go back if things go south.
     
  9. basmevissen

    basmevissen New Member

    It will probably take some months before I migrate to the new server.
    Will there be maintenance on 3.1 when there is a security issue found? In that case, I can leave it running as it is.
     
  10. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    There are some security issues fixed in 3.2. There will be no 3.1.X upgrade.
     
  11. basmevissen

    basmevissen New Member

    Ok, so I cannot have the old server running for too long on 3.1.
    Thanks for the information, I'll give 3.2 a try!
     
    Th0m likes this.
  12. basmevissen

    basmevissen New Member

    Finally got around upgrading. Today 3.2.1 was released and that was a nice opportunity to pull the trigger. :)
    Upgrade went fine, except for the upadte script trying to start clamd and it refused to continue for some reason, with clamav taking quite some cycles. Now I'm not using clamd, so maybe something is misconfigured. I killed clamd from another terminal and the installation continued with some errors around this service, but completed successfully.

    Anyway, not bad for a server running for about 9 years without reinstalling (only a couple of system upgrades).
    Many thanks for all the work on ISPConfig!
     
    ahrasis, till and Th0m like this.
  13. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Good to hear. If you don't use clamd but it is installed, this can cause issues.

    Indeed not bad for such a old system ;) But I hope he can retire soon so you can use a modern OS with all security fixes.
     
  14. basmevissen

    basmevissen New Member

    As said before, it gets quite a lot of security updates from the ESM program. So I don't think it is insecure. Nevertheless, it is going to retire in a while anyway.
     
  15. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    True, for the critical security issues there are updates. But for minor security issues and regular issues I suspect there are no fixes. Not a member of the program so not sure ;)
     

Share This Page