Error installing cpanel whm OVH / hetzner

[Quintanilha-RJ]

Good afternoon, I have a problem installing cpanel whm for more than 2 months and I can't solve it and ask for help.

When completing the installation of cpanel whm I have the following message:

[2022-10-04 18:22:44 +0200] [90365] ( WARN): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2022-10-04 18:22:44 +0200] [90365] ( WARN): Your system kernel may have been updated.
[2022-10-04 18:22:44 +0200] [90365] ( WARN): Current kernel (4.18.0-348.20.1.el8_5.x86_64) has been changed to: 4.18.0-372.26.1.el8_6.x86_64
[2022-10-04 18:22:44 +0200] [90365] ( WARN): Before rebooting the system, please ensure that the installed kernel version is compatible with your deployment.
[2022-10-04 18:22:44 +0200] [90365] ( WARN): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Apparently everything is normal but when I restart my dedicated server the server simply does not come back online. I believe what is happening is this kernel change on the server and so it doesn't come back online with the cpanel whm panel. I tested it in two datacenters at OVH and Hetzner and got the same error.

could someone from friends help me, i need to install cpanel whm directly on non-virtualized dedicated server, the current server settings is:

• AMD Ryzen 9 5950X 16 núcleos (Zen3)
• 128 GB DDR4 ECC RAM
• 2 x 3,84 TB NVMe SSD Datacenter Edition (Software-RAID 0)

follow below print of the error :

 

[cPRex]

Hey there! I'm not sure there is much we can help with on the cPanel-side of things for this particular error. I would recommend reaching out to the host about this kernel issue and having them confirm this is compatible with your system and hardware. What is most likely happening is that the "yum update" process is downloading a new kernel as part of the cPanel installation, but that isn't a part of the server that we manage.

 

[Quintanilha-RJ]

What I'm finding strange is that it's not just in one datacenter, but in two different datacenters and different dedicated servers. I believe it's not just me who is going through this, but many users who are currently installing the cpanel whm panel.

 

[cPRex]

Could you create a ticket with our team with a fresh installation of your operating system so we can check that on our end?

 

[vacancy]

This probably has nothing to do with the kernel.

The problem is with the network configuration.

Cpanel uses networkd for network settings, some servers of ovh and hetzner take ip distribution via dhcp. There are some incompatibilities between DHCP and networkd service. NetworkManager is required for it to work smoothly with DHCP. When the server operating system is installed, it comes with NetworkManager, when you install cpanel, the cpanel setup agent closes NetworkManager and activates networkd. When you restart the server, the server cannot get ip over dhcp and there is an access problem.

We've had this problem on many servers set up via ovh and hetzner automation. After the cpanel installation is complete, run the systemctl enable NetworkManager.service and systemctl disable network.service commands and restart the server. The networkd service will be disabled at startup and the Network.Manager service will run. In this way, your server will start pinging by taking ip over dhcp.

 

[Quintanilha-RJ]

my friend solved you are the guy, it was 2 months to solve this. thank you very much, I would even buy you a pizza now thank you

 

[Quintanilha-RJ]

Good afternoon friend, could I ask a question?

After I installed cloudlinux and made all the settings the error returned, is there any way to fix this error in rescue mode? because the server did not come back and the same is already set up!

 

[vacancy]

If you have kvm, you can login with root and run commands, if you don't have kvm, you can try by chrooting directories in recovery mode.

I have heard that the cloudlinux kernel is incompatible with some new amd processors, except for the network problem, you may be experiencing incompatibility problems between cloudlinux and new amd processors. It is necessary to see what error the system gives with kvm.

 

[Quintanilha-RJ]

Good evening, your command worked, but only when I restarted the server for the first time, when restarting the server for the second time the error occurred again.

I ran the commands:

systemctl enable NetworkManager.service

systemctl disable network.service

and restarted the server it pinged again, but when I restarted it again the ping did not come back. is there any way to fix this command. because if I forget to perform the procedure when restarting the server it will cause problems.

 

[vacancy]

Good evening, your command worked, but only when I restarted the server for the first time, when restarting the server for the second time the error occurred again.

I ran the commands:

systemctl enable NetworkManager.service

systemctl disable network.service

and restarted the server it pinged again, but when I restarted it again the ping did not come back. is there any way to fix this command. because if I forget to perform the procedure when restarting the server it will cause problems.

You can run the commands automatically at startup by adding them to /etc/rc.local.