As is well known, support for Centos 7 was discontinued in the summer of 2024, and the ISPManager 6 control panel can no longer run on a server with Centos 7 installed. This raises the question for many users: what should be done and which alternative should be chosen? The first thing to note is that migration is a very responsible process. Below, we will explain how to do it correctly.
The key tools for migration are the Elevate utility and the Leapp framework, which ensure a smooth transition between distribution versions.
Your server must meet the following requirements:
The AlmaLinux operating system is considered as an alternative to Centos 7. Once you are ready to migrate to this OS, the first thing you need to do is make a backup. The migration process will not be painful (even if you make some mistakes at a certain stage) if a backup company is created. To do this, prepare a snapshot of the system and a copy of the databases. This will automatically protect you from unnecessary problems and hassles.
Once the database is ready, check the current version of CentOS:
To do this, run the command:
cat /etc/centos-release
If the OS requirements are not met, you need to update the system packages using the command:
yum update
curl -o centos7-to-alma8.tgz "http://download.ispmanager.com/tools/centos7-to-alma8.tgz tar -xzvf centos7-to-alma8.tgz cd centos7-to-alma8screen python3 main.py --rebootImportant to know: an error may occur during the execution of the script. The reasons for this can vary greatly. There is only one solution: fix the error and run the script again. It will start working from the point where it was interrupted due to the error.
Then you just have to wait for the conversion process to complete, after which the server will go into a scheduled reboot. Keep in mind that the entire process can take a long time and requires special attention and caution. At the end, you can also view the original version of the configuration files at /var/config_backups/.
Converting MySQL databases below version 8.0.36 or MariaDB databases below version 5.5.68 may result in data corruption.
Using encrypted partitions or the xfc ftype=0 parameter may cause conversion errors.
The floppy, pata_acpi, and sata_via drivers must be removed.
If the system does not boot, try booting into recovery mode or using the AlmaLinux live CD/USB. Use chroot to access the system and reinstall the boot loader (e.g., GRUB2).
You should also check the application logs for errors. Make sure that all necessary libraries and dependencies are installed.
cat /etc/os-release.If specific applications were used (e.g., Afterlogic, PostgreSQL), consider possible changes after migration. For example, Afterlogic may be replaced with RoundCube, and PostgreSQL may require additional configuration.
/var/log/leapp/upgrade.log and /root/centos7-to-alma8/convertation.log/root/centos7-to-alma8/convertation-report.txtIf you encounter specific problems and difficulties, it is worth referring to the official ISPmanager and AlmaLinux documentation.