Most often, with the SolusVM cPanel Installation template, we may find that the installation is unable to complete.
SolusVM cPanel installation loses network connectivity
As part of our Server Management Services, we assist our customers with several SolusVM queries.
Today, let us see how we can fix the SolusVM cPanel installation error easily.
SolusVM cPanel Installation unable to complete
Recently, we had a customer who tried the SolusVM cPanel Installation. However, he was unable to complete the process.
During the installation process, the installation stops at this point:
2020-07-23 04:38:30 1372  (DEBUG): Retrieving http://httpupdate.cpanel.net/cpanelsync/188.8.131.52/cpanel/scripts/fix-cpanel-perl.xz to the fix-cpanel-perl.xz file... 2020-07-23 04:38:31 1372  (DEBUG): Retrieving http://httpupdate.cpanel.net/cpanelsync/184.108.40.206/cpanel/scripts/fix-cpanel-perl.xz.asc to the fix-cpanel-perl.xz.asc file... 2020-07-23 04:38:31 1848  (DEBUG): - ssystem [END] 2020-07-23 04:38:31 1850  ( INFO): The system set the clock to: Thu Jul 23 04:38:31 2020
Generally, with the users who have experienced the SolusVM template issue, the issue is with the status of SELinux.
Our Support Techs recommend we disable the SELinux to prevent issues with installation regardless of the environment that administrators install cPanel on.
Now that we know the issue, we can easily fix it.
Moving ahead, let us see how we can fix the installation error. To do so, we follow the below steps,
In order to make the system compatible with cPanel & WHM, we need to disable SELinux.
To disable SELinux security features, we use either of the following methods:
- Use the graphical interface to disable SELinux while we configure the operating system, and then reboot the server.
- Edit the
/etc/selinux/configfile to set the
disabled, and then reboot the server.
The contents of the
/etc/selinux/configfile will resemble the following example:
1 2 3 4 5 6 7 8 9 10
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
[Need help with the fix? We can help you]
To conclude, mostly this error occurs if we do not disable SELinux. Today, we saw how our Support Techs go about this error for our customers.