Here are the pitfalls of cPanel ELevate Script when upgrading from Centos 7. Our cpanel Support team is here to help you with your questions and concerns.

Pitfalls of cPanel ELevate Script Centos 7

Upgrading a cPanel & WHM CentOS 7 server to AlmaLinux 8 using the cPanel ELevate script is usually a smooth process. However, sometimes there may be some issues that may arise during the migration.

Recently, many of our customers running CentOS7 have been coming across the following warning message:

cpanel & whm version 110 will be the last version that supports centos 7. support for version 110 will end june 30, 2024. we encourage you to migrate to a server running almalinux 8, rocky linux 8, or cloudlinux™ 8 before june 30, 2024. for more information, read our cpanel deprecation plan documentation. click the “elevate to almalinux 8” button below to read about a script you can use to upgrade cpanel & whm installations on centos 7 to almalinux 8.

So if you are in a rush to upgrade from CentOS 7 via the Elevate script it is a good idea to be aware of the challenges.

Some of the common issues that our Experts have come across include:

• x86_64 RPMs:

  Upgrading RPMs not in the primary CentOS repos may occur, requiring careful validation.
• EA4 RPMs:

  This is due to incorrect EA4 RPMs.
• cPanel Binaries:

  The cPanel binaries are invalid.
• Third-Party Repo Packages:

  Third-party repo packages are not upgraded.
• Manually Installed Perl XS:

  Manually installed Perl XS (arch) CPAN may become invalid during the process.

• YUM Repo:
  Verify the compatibility of enabled YUM repos to prevent unsupported scenarios.
• Elevation Blocker:

  Machines with multiple NICs using kernel-names (ethX) may run into elevation problems.

Common Pitfalls of Updating cPanel via Elevate

1. Dependency Issues:

   The cPanel elevate script will fail in case of missing dependencies or misconfigured server’s package repositories. Then, users have to resolve dependency issues manually ahead of running the script.
2. SELinux Interference:

   Did you know that by default CentOS 7 ships with SELinux?

   Unfortunately, it tends to interfere with the cPanel installation process. In these cases, users run into permission-denied errors or other issues related to SELinux policies. However, we can disable SELinux temporarily or configure SELinux policies to allow cPanel operations to avoid this pitfall.
3. Firewall Configuration:

   Furthermore, the server’s firewall settings can prevent cPanel from functioning properly by blocking necessary ports. So, users have to make sure that the firewall permits inbound and outbound traffic on the necessary ports.
4. Network Connectivity:

   If the server does not have DNS resolution or proper network connectivity, the cPanel elevate script will not download needed packages or carry out needed tasks. Hence, users should have to verify the server’s internet access and the functioning of DNS resolution.
5. Server Resource Constraints:

   Insufficient server resources will lead to unsuccessful cPanel installation process failure or poor performance. Therefore, before executing the elevate script, we have to confirm that the server meets the minimal system requirements set by cPanel.
6. Conflicting Software:

   In some cases, conflicting software like control panels or web servers will cause issues. So, we have to uninstall them before executing the elevate script.
7. Outdated Software:

   Additionally, outdated or incompatible server software packages may lead to issues. Hence, update the server’s software repositories and packages.
8. Incorrect Usage:

   If we not using the cPanel elevate script correctly, we are likely to run into problems. Hence review the script’s documentation carefully ahead of running it.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts introduced us to the many pitfalls of eLevate Script when upgrading from cPanel Centos 7.