CentOS 7 reaches end-of-life on June 30, 2024. Does Plesk support an in-place upgrade from Centos 7 to AlmaLinux 8?
How such a conversion can be done?
We prepared a CLI script that in-place converts a Plesk server with CentOS 7 to AlmaLinux 8.
Warning: Plesk services, hosted websites, and emails will be unavailable during the conversion process for about 30 to 60 minutes.
Warning: The conversion is a complex and potentially dangerous task. Make sure to create a server-wide backup in Plesk and/or server snapshot in advance. Check the Requirements and Limitations and Preparation and Timing sections before proceeding.
The script was prepared by developers in the scope of https://jira.plesk.ru/browse/PPP-58796. Check the Assignee and Reporter there. Assignee and Reporter are the point of contact in case of any questions. You can also create 3rd-lines in case of issues.
Plesk Obsidian 18.0.43 or later.
CentOS 7.9 or later.
Note: The script was not tested on other Red Hat Enterprise Linux 7-based distributions. The conversion process may have unexpected results if started on a server running with OSes other than CentOS 7.9.
grubpackage must be installed.
At least 5GB of free disk space.
At least 1 GB of free RAM.
PHP 7.1 and earlier are not supported in AlmaLinux 8, and will not receive any updates after the conversion. These PHP versions are deprecated and may have security vulnerabilities. So we force to remove these versions before the conversion. Domains using PHP 7.1 and earlier should be switched to an up-to-date PHP version.
Conversion inside containers (Virtuozzo containers, Docker Containers, etc.) is not supported.
More than one kernel named interfaces (like
ethX) are not supported.
When the PostgreSQL database server before version 10 is installed, it is not possible to run the conversion script due to potential data loss.
In such cases either upgrade PostgreSQL to version 10 manually before initiating the conversion or create a complete backup of the database and force the conversion using the
During the conversion process, if the tool detects Perl modules that were installed via CPAN and cannot determine their corresponding RPM packages, it will fail with a warning. This restriction is in place because such modules will not be available after the conversion.
To avoid issues, check for RPM package analogs for the modules, remove the CPAN modules, and then reinstall them after the conversion is complete. If such modules are no longer required, it is possible to remove them forcefully by running the tool with the
To avoid downtime and data loss:
Create a server-wide backup in Plesk and/or create a server snapshot in advance, so it can be used as a recovery point in case the convention process fails.
Ensure that you have a way to restart the server without a direct SSH connection. A serial port connection to the server can be used to monitor the status of the conversion process in real time and to reboot the server if necessary.
The conversion process is expected to take up from 30 to 60 minutes.
Warning: Plesk services, hosted websites, and emails will be unavailable during the entirety of the conversion process.
The conversion process itself consists of three stages:
Conversion, which takes between 15 and 30 minutes.
Note: During this stage, the server will not be available remotely. To monitor the progress use a serial port console.
- Finalization, which takes between 5 and 10 minutes.
After the preparation is done and the list of
Requirements and limitations is checked, to convert from Centos 7.9 to Almalinux 8 follow the steps from the below instruction on GitHub.