Kernel conflicts on OVH servers due to missing exclude line in /etc/yum.repos.d/OVH-kernel.repo
Hello,
I have 3 servers out of 8 throwing a similar error when cpanel tries to update to current version. cPanel throws the following notice to the admin:
Then I did some research and saw that I some threads asked to run '/usr/local/cpanel/scripts/rpmup' manually to see the output. Below is a sample of that output.
I'm not sure where to start. I have not tried to reboot the servers and run update after reboot. I may try that this weekend. When I saw the kernel conflicts I checked the servers kernels and found the following.
Any idea on where to start on this? Thanks, Mike
2019-05-31 07:33:01 -0500] E [/usr/local/cpanel/scripts/rpmup] The "/usr/local/cpanel/scripts/rpmup" command (process 21012) reported error number 1 when it ended.
Then I did some research and saw that I some threads asked to run '/usr/local/cpanel/scripts/rpmup' manually to see the output. Below is a sample of that output.
file /usr/include/scsi/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64
file /usr/include/scsi/fc/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64
file /usr/include/sound/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64
file /usr/include/video/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64
file /usr/include/xen/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64
I'm not sure where to start. I have not tried to reboot the servers and run update after reboot. I may try that this weekend. When I saw the kernel conflicts I checked the servers kernels and found the following.
host86 is booting from internal hard disks to kernel 4.19.18-xxxx-std-ipv6-64
host88 is booting from netboot to kernel 4.14.63-xxxx-std-ipv6-64
host90 is booting from netboot to kernel 4.14.63-xxxx-std-ipv6-64
Any idea on where to start on this? Thanks, Mike
-
I have the same problem. Can you help me? Regards. 0 -
Hello, I'm still trying to fix this. It seems cPanel does not provide Kernel support. I'm waiting for the weekend to reboot the server with a new kernel installed to see if that fixes the issue. - Mike 0 -
that because you are using a non standard kernel "OVH's" 0 -
Hello, I'm still trying to fix this. It seems cPanel does not provide Kernel support. I'm waiting for the weekend to reboot the server with a new kernel installed to see if that fixes the issue. - Mike
With the netboot - Network ---> error conflicts And the netbot - Hard disk ---> error conflictsthat because you are using a non standard kernel "OVH's"
We assume that an OVH kernel is optimized for its machines.0 -
Hello, I have 3 out of 8 server with the above kernel issue. The are all running OVH kernels, since OVH optimizes them with correct drivers and what not run the hardware and system boards without having to load 3 party drivers manually. It two of the three netboot and have an error, one is hard disk boot with exact same error. It is not clear why the above example is throwing an error for kernel-4.19-ovh-xxxx-std-ipv6-64 when it is running a netboot kernel of 4.14.63-xxxx-std-ipv6-64. My other 5 servers that hard drive boot to OVH kernels update cPanel without error. I'm just looking for some direction on where to start troubleshooting. - Mike 0 -
To have 4 affected servers. The 4 servers recently installed. I also dont understand the error. It is not understandable. Surely there are more affected. 0 -
It is only affecting 3 of my 8 servers. To have 4 affected servers. The 4 servers recently installed. I also dont understand the error. It is not understandable. Surely there are more affected.
0 -
Hello, Oh, so we just need to manually update the kernel on these servers? So the cPanel update won't work with kernels lower than 4.19.18-xxxx-std-ipv6-64?? What is the correct kernel to update to, 4.19.45-xxxx-std-ipv6-64? Thanks, Mike Hello Everyone, This looks to be isolated to dedicated servers using outdated OVH kernels. OVH documents how to perform kernel updates on dedicated servers on the link below:
0 -
Hello, I looked at the servers that are updating without error and they are all running kernel 4.19.18-xxxx-std-ipv6-64. Our server host86 that is booting from internal hard disks is also running 4.19.18-xxxx-std-ipv6-64. So I'm sure that is a specific kernel issue, though I can try to update to 4.19.45-xxxx-std-ipv6-64 and see if that makes a difference. Kernel 4.14.63-xxxx-std-ipv6-64 is from August 2018, is that really considered out of date or old? - Mike 0 -
So the cPanel update won't work with kernels lower than 4.19.18-xxxx-std-ipv6-64??
Hello Mike, It's not the cPanel update itself, but rather your system's kernel RPMs failing to update upon execution of the command below (it runs as part of the cPanel update process):/usr/local/cpanel/scripts/rpmup
Thank you.0 -
Hello, host86 has "Enable Linux kernel update during nightly maintenance." set to off. host88 has "Enable Linux kernel update during nightly maintenance." set to off. host90 has "Enable Linux kernel update during nightly maintenance." set to off. The above are the three servers throwing the original error during /usr/local/cpanel/scripts/rpmup execution. - Mike 0 -
Hello Mike, Do you notice any errors when running the "yum update" command on an affected system? Thank you. 0 -
Hello. I changed the option on my server with kernel version 4.14 (Enable Linux kernel update during nightly maintenance." to ON) and executed "/usr/local/cpanel/scripts/upcp" but the problem persist. Servers with lower versions(4.9) of kernel work correctly. I need update kernel manually to 4.19 ? Or open one ticket to OVH ? Regards. 0 -
Hello, I'll run yum update and see what comes of it. - Mike Hello Mike, Do you notice any errors when running the "yum update" command on an affected system? Thank you.
0 -
Hello, I have attached a TXT with output from "yum update" Here is summary info: ---> Package kernel-4.19-ovh-mod-std-ipv6-64-headers.x86_64 0:4.19_ovh_mod_std_ipv6_64-732421 will be obsoleting ---> Package kernel-4.19-ovh-xxxx-std-ipv6-64-headers.x86_64 0:4.19_ovh_xxxx_std_ipv6_64-732421 will be obsoleting ---> Package kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers.x86_64 0:4.19_ovh_xxxx_std_ipv6_64_hz1000-732421 will be obsoleting ---> Package kernel-headers.x86_64 0:3.10.0-957.12.2.el7 will be obsoleted ---> Package kmod-libs.x86_64 0:20-21.el7 will be updated ---> Package kmod-libs.x86_64 0:20-23.el7 will be an update ---> Package ovhkernel_4.9_xxxx_std_ipv6.x86_64 0:4.9.178_xxxx_std_ipv6_64-730913 will be updated ---> Package ovhkernel_4.9_xxxx_std_ipv6.x86_64 0:4.9.180_xxxx_std_ipv6_64-746430 will be an update --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================================================================== Installing: kernel-4.19-ovh-mod-std-ipv6-64-headers x86_64 4.19_ovh_mod_std_ipv6_64-732421 ovhkernel 1.3 M replacing kernel-headers.x86_64 3.10.0-957.12.2.el7 kernel-4.19-ovh-xxxx-std-ipv6-64-headers x86_64 4.19_ovh_xxxx_std_ipv6_64-732421 ovhkernel 1.3 M replacing kernel-headers.x86_64 3.10.0-957.12.2.el7 kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers x86_64 4.19_ovh_xxxx_std_ipv6_64_hz1000-732421 ovhkernel 1.3 M replacing kernel-headers.x86_64 3.10.0-957.12.2.el7 Then a munch of these: Total size: 74 M Total download size: 50 k Is this ok [y/d/N]: y Downloading packages: No Presto metadata available for base kmod-libs-20-23.el7.x86_64.rpm | 50 kB 00:00:00 Running transaction check Running transaction test Transaction check error: file /usr/include/asm-generic/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers-4.19_ovh_xxxx_std_ipv6_64_hz1000-732421.x86_64 file /usr/include/asm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers-4.19_ovh_xxxx_std_ipv6_64_hz1000-732421.x86_64 file /usr/include/drm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers-4.19_ovh_xxxx_std_ipv6_64_hz1000-732421.x86_64 file /usr/include/linux/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers-4.19_ovh_xxxx_std_ipv6_64_hz1000-732421.x86_640 -
I opened a ticket to OVH with this problem. I also made reference to this discussion. This is the answer: OVH:"Regarding your query about this case, unfortunately there is no possibility to launch the installation of the operating system from the client area with a custom kernel. For this type of operations, you should use the rescue mode and install the kernel that you consider appropriate from this mode on the operating system installed on the server disks." I want to cry. 0 -
Hello, Kernel updates are important, however you could try temporarily excluding the kernel and ovhkernel RPMs from the YUM update process until you've received a solution approved by OVH. To do this, first open the /etc/yum.conf file with your preferred text editor via SSH. EX: vi /etc/yum.conf
In this file, you'll see an "exclude=" line like this:exclude=courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* nsd* p0f php* proftpd* pure-ftpd* spamassassin*
Add kernel* and ovhkernel* to this line like this:exclude=kernel* ovhkernel* courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* nsd* p0f php* proftpd* pure-ftpd* spamassassin*
Then, run the following commands again to confirm the temporary workaround solves the issue:yum clean all yum update
If the "yum update" command succeeds this time, attempt another cPanel update (/scripts/upcp) and let us know of any additional errors. Thank you.0 -
Hello everyone, OVH support is horrible, I had the same problem on four servers with CentOS 7. They replied (2 days later) that even being the OVH kernel, they do not support distributions and cannot help since "it's a unmanaged server"... OVH is very good, stable and good prices, but have the worst support ever. I use them only for non-critical services, because I cant trust them in emergency situations. When purchasing a new dedicated server in OVH, choose to install the native kernel and not the OVH kernel. Anyway, to stop the error, edit the file: vi /etc/yum.repos.d/OVH-kernel.repo
and set:enabled = 00 -
Hello, I'm testing this now with one of the servers. - Mike 0 -
Hello, On host86 I ddi the Yum exclude, clean and update. That worked that time. I'll try the other options too so see how that fares, I'm guessing they both accomplish the same task of excluding the kernal updates automatically. We do manually kernel updates anyway. Thanks for your help. - Mike 0 -
Hello, I'd have to say with OVH you get what you pay for. They are very strict and have a no software support policy. You have to be your own system admin. That is what makes their prices so good. The infrastructure and pricing and features are hard to beat. You just have know this going in to it when signing with OVH. Once you get your head around that and find others for support like cpanel forum and linux forums, it is not as bad as horrible. It is actually very good. Also, I'd recommend the opposite regarding OVH kernels. If you install the native kernel you may in for a world of hurt looking for drivers and other items to get the system to boot. Better to go with OVH kernels and manually update from time to time. My 2 cents on OVH. If you use them for what they are good for then you'll have no complaints. They have always been receptive to replacing failing hard drives or raid controllers. - Mike Hello everyone, OVH support is horrible, I had the same problem on four servers with CentOS 7. They replied (2 days later) that even being the OVH kernel, they do not support distributions and cannot help since "it's a unmanaged server"... OVH is very good, stable and good prices, but have the worst support ever. I use them only for non-critical services, because I cant trust them in emergency situations. When purchasing a new dedicated server in OVH, choose to install the native kernel and not the OVH kernel.
0 -
Also, I'd recommend the opposite regarding OVH kernels. If you install the native kernel you may in for a world of hurt looking for drivers and other items to get the system to boot. Better to go with OVH kernels and manually update from time to time.
Well, I don't agree. Better use a known and world-wide used kernel. As you can see, a lot of people are having problems, and this kind of problem (OVH kernel repo conflicts) is a way to destroy your server.My 2 cents on OVH. If you use them for what they are good for then you'll have no complaints. They have always been receptive to replacing failing hard drives or raid controllers.
You're luck. Last time I have this kind of problem, they took 2 days to reply the ticket, and more 3 days to replace parts... Not even a good status system do they have ... just something like OVH Tasks0 -
Hello. I run yum exclude, clean and update and also worked. In my servers. I think that OVH dont want you to use other Kernels because if your own kernel has problems (malware for example), it is also a problem for them. But they should verify these cases. Thanks to all of you. 0 -
I have the same problem with a server and another identical one that works on CENTOS 7.6 On the one that does not work, / boot/initramfs has been deleted and grub not updated during the yum update. At the next reboot, it displays the grub prompt because it tries to boot to a kernel that no longer exists. After analyzing the server that works, it appears that the exclude line is missing in the OVH repo: nano /etc/yum.repos.d/OVH-kernel.repo [ovhkernel] name=OVH kernel repo enabled=1 baseurl=http://last-public-ovh-kernel.snap.mirrors.ovh.net/ovhkernel-rpm/ #gpgcheck=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-OVH exclude=kernel-4.19-ovh-xxxx-std-ipv6-64-headers,kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers,kernel-4.19-ovh-mod-std-ipv6-64-headers
This restores kernel updates and cleanly reinstalls the latest version with its initramfs. For those on the prompt grub, you have to restart in netboot and update grub grub2-mkconfig -o /boot/grub2/grub.cfg grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg It seems to be an ovh error in its installation template.0 -
Few more things worth mentioning in this thread as it was a result of a kernel update (client updated cPanel for patching exim exploit) and a OVH server. Situation : Kernel was updated, rebooted the server and didn't come back. Client' server was EFI + Grub2 + no IPMI. Initial check to do : - Check whether it is an EFI or normal BIOS
- Check whether it runs grub2 or grub.
- Check whether your server has IPMI enabled. Troubleshooting becomes simpler if it is.
- Try to boot from netboot. You are lucky, if it can run from netboot.
- If that fails, boot to rescue
- cat /etc/fstab and if it is UEFI firmware, check for a efi partition and mount it inside the /boot/efi. And inside check for grub.cfg. In this particular case grub.cfg was missing. If it's BIOS based check for /boot/grub2/grub.cfg
- Also check for initramfs, if that is missing, you have to do some more extra steps so that you can build
- Again check for /etc/default/grub to make sure that the OVH kernel is selected and not the "saved".
0 -
I have the same problem with a server and another identical one that works on CENTOS 7.6 On the one that does not work, / boot/initramfs has been deleted and grub not updated during the yum update. At the next reboot, it displays the grub prompt because it tries to boot to a kernel that no longer exists. After analyzing the server that works, it appears that the exclude line is missing in the OVH repo: nano /etc/yum.repos.d/OVH-kernel.repo
[ovhkernel] name=OVH kernel repo enabled=1 baseurl=http://last-public-ovh-kernel.snap.mirrors.ovh.net/ovhkernel-rpm/ #gpgcheck=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-OVH exclude=kernel-4.19-ovh-xxxx-std-ipv6-64-headers,kernel-4.19-ovh-xxxx-std-ipv6-64-hz1000-headers,kernel-4.19-ovh-mod-std-ipv6-64-headers
This restores kernel updates and cleanly reinstalls the latest version with its initramfs. For those on the prompt grub, you have to restart in netboot and update grub grub2-mkconfig -o /boot/grub2/grub.cfg grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg It seems to be an ovh error in its installation template.
I had this conflict issue after WHM upgraded to v80.0.18 on CentOS 7.6 and just confirmed that the quoted solution above worked for one of my servers! The issue: [QUOTE][2019-06-22 00:03:21 +0000] [/usr/local/cpanel/scripts/rpmup] file /usr/include/asm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64
The solution that worked for me: - Boot using OVH latest network kernel - nano /etc/yum.repos.d/OVH-kernel.repo and add the exclude= line to the bottom - yum update (updated kernel to latest) - Run both grub2-mkconfig commands - Change netboot back to HDD - Reboot Success! Thank you @pasanja!0 -
Hello everyone, OVH support is horrible, I had the same problem on four servers with CentOS 7. They replied (2 days later) that even being the OVH kernel, they do not support distributions and cannot help since "it's a unmanaged server"... OVH is very good, stable and good prices, but have the worst support ever. I use them only for non-critical services, because I cant trust them in emergency situations. When purchasing a new dedicated server in OVH, choose to install the native kernel and not the OVH kernel. Anyway, to stop the error, edit the file:
vi /etc/yum.repos.d/OVH-kernel.repo
and set:enabled = 0
Thanks alot, that worked for me. I edited the file and did a yum update and everything went fine. But the question now is that going to make any issues when restarting the server as the server already using the network to boot (BootOVH kernel (includes up-to-date intel microcodes) ) ??0
Please sign in to leave a comment.
Comments
29 comments