Installation Guide - Troubleshoot Your Installation
This documentation describes additional steps to use if you install cPanel & WHM with this guide, but still experience problems.
You see license errors during or after the installation process (for example, a License File Expired message).
- Your license may be expired or improperly configured.
- Your system may not connect properly to the cPanel, L.L.C. license servers.
- Your server may use an invalid hostname.
- Your server may use an incorrect date and time.
To troubleshoot this issue, perform the steps in our How to Fix License File Errors documentation. content/knowledge-base/cpanel-product/how-to-fix-license-file-errors
Perl installation errors
You see the following error message during the installation process:
Fatal! Perl must be installed before proceeding!
Perl must exist on your server before the installation script for cPanel & WHM can run successfully. If Perl does not exist during installation, the cPanel & WHM installer attempts to install Perl via the
yum -y install perl command. If the installation does not succeed, the system displays this error message.
We strongly recommend that you allow your operating system’s distribution to control the system Perl installation. Do not customize this Perl installation.
For more information about Perl on your server, and which versions of Perl ship with specific operating systems, read our Guide to Perl in cPanel & WHM documentation. cPanel & WHM servers use multiple Perl environments.
Problems with yum generally cause this error. Make certain that yum functions properly on your server.
To attempt to install Perl again, run the following command:
yum install perl
High CPU load on Hyper-V
The server reports a high CPU load, and Hyper-V’s Dynamic Memory option is enabled.
This problem is due to an issue with sleep interruptibility in Hyper-V.
For more information and a patch to fix the issue, visit the LKML website.
RPM installation failures
One or more RPMs fail during installation.
There are several reasons why your operating system’s RPM installations may fail.
For steps to fix this issue, read our RPM Installation Failures documentation.
You experience problems that relate to DNS.
You may need to set up resolvers. Resolvers allow your server to communicate with DNS servers to find IPv4 or IPv6 addresses that correspond to domain names.
One or more directories or partitions may be improperly configured.
To check your server’s resolvers, run the following command, where example.com represents a domain on your server:
If this command did not return results, the
/etc/resolv.conf file does not contain resolvers. Use WHM’s Resolver Configuration interface (Home >> Networking Setup >> Resolver Configuration) to add resolvers to your server.
To determine whether your server can communicate with a resolver, perform the following steps:
Use SSH to log in to your server via the command line.
Run the following commands to check communication via IPv4 and IPv6:
- If these commands fail, make certain that you used the correct IP addresses. Then, run the following commands to find the problem:
184.108.40.206with the desired resolver’s IPv4 address.
2001:4860:4860::8888with the desired resolver’s IPv6 address.
- Due to networking requirements, you cannot run an IPv6-only cPanel & WHM server. You must have at least one IPv4 address.
A cloud-hosted server does not retain the hostname setting.
dhclient script that the cloud hosting provider uses may interfere with cPanel & WHM’s hostname configuration script.
For steps to fix this issue, read our Cloud-Hosted Hostname Solution documentation.