WHM v66.0.14 - You must reboot the server to apply kernel updates
Hi,
Just did a force update to v66.0.14 and in WHM it saying:
You must reboot the server to apply kernel updates
I am running KernelCare that fully up to date and yum update doesn;t find anything.
I have also done a graceful reboot twice.
[root@katie ~]# uname -r
3.10.0-514.26.2.el7.x86_64
[root@katie ~]# yum install kernel
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 85.13.201.2
* cpanel-addons-production-feed: 85.13.201.2
* base: mirrors.linode.com
* extras: mirrors.linode.com
* updates: mirrors.linode.com
Package kernel-3.10.0-514.26.2.el7.x86_64 already installed and latest version
Nothing to do
[root@katie ~]#
-
Update: just click on v66.0.14 which takes you to: Upgrade to Latest Version I then clicked on Click to Upgrade. After it ran and I click on the WHM image, it has now gone 0 -
Hi, I just upgraded to WHM v66.0.14 and I see a message that says "You must reboot the server to update kernel." and I did it two times!! I'm still seeing same message. Do I still have to reboot? I thought it stuck! What can we do? Thanks. 0 -
did you run # yum update kernel upcp does not upgrade the kernel 0 -
Hello, Internal case CPANEL-15405 is open to address an issue where the use of non-stock kernels can result in the "You must reboot the server to update kernel" banner in WHM in cases where the active kernel is already installed and utilized. The resolution will include changes to ensure this feature isn't utilized on systems running custom kernels. I'll monitor this case and update this thread with more information as it becomes available. Thank you. 0 -
This is also occurring for systems running CLOUDLINUX 7.3 standard v66.0.14 0 -
did you run # yum update kernel upcp does not upgrade the kernel
yes I connected with ssh and yum clean all yum update there is nothing updated. still, I'm seeing the same message!?0 -
Hello, Internal case CPANEL-15405 is open to address an issue where the use of non-stock kernels can result in the "You must reboot the server to update kernel" banner in WHM in cases where the active kernel is already installed and utilized. The resolution will include changes to ensure this feature isn't utilized on systems running custom kernels. I'll monitor this case and update this thread with more information as it becomes available. Thank you.
SOLVED - cPanel 66 - Reboot Message in WHM I checked this threads and removed cache file. rm /run/system_needs_reboot.cache Its not showing anymore and also root@ocean:/run # kcarectl --uname -bash: kcarectl: command not found Do I need to track check this later?0 -
yes that error message appeared again. I'm not happy. :( You must reboot the server to apply kernel updates. 0 -
Hello, Internal case CPANEL-15405 will prevent the reboot banner from appearing on any system that uses a custom kernel. I'll update this thread again once the resolution is published. Thank you. 0 -
Hello, To update, the resolution is included with cPanel version 66.0.17 (available in the CURRENT build tier): Fixed case CPANEL-15405: Don't instruct users to reboot when they're running a custom kernel. This version should make it's way to the "RELEASE" build tier in the near future. You can read more about the product versions and release process at: Product Versions and the Release Process - cPanel Knowledge Base - cPanel Documentation Thank you. 0 -
Updated to 66.0.17 last night yet the message remains. 48527 0 -
Updated to 66.0.17 last night yet the message remains.
Hello, KernelCare updates the system to the latest kernel via its patching system, however it's possible the kernel RPM installed on the system is not updated to the latest version. Using the latest kernel RPM isn't required with KernelCare (it allows the system to run updated kernels without the latest RPM installed), however this can lead to cPanel displaying the "reboot warning" because the boot_version and running_version it detects are mismatched. A new case, CPANEL-15544, is now open to address this behavior. I'll monitor this case and update this thread with more information as it becomes available. In the meantime, you should be able to workaround this issue by installing the latest kernel RPM available from your OS (e.g. yum update kernel). Thank you.0 -
Hello, the message appears again on WHM/cPanel v66.0.17. Already running yum update kernel and nothing happened. [root@server ~]# yum update kernel Loaded plugins: fastestmirror, rhnplugin, universal-hooks This system is receiving updates from CLN. Loading mirror speeds from cached hostfile * EA4: 104.219.172.10 * cpanel-addons-production-feed: 104.219.172.10 * cloudlinux-x86_64-server-7: cl.banahosting.com No packages marked for update [root@server ~]# Thank you. 0 -
Hi Guys, Same issue for me, but I'm not using Kernel Care. Applied updates (yum update kernel) but warning message remains...? Cheers, Robin. 0 -
the message appears again on WHM/cPanel v66.0.17. Already running yum update kernel and nothing happened.
Does this server use KernelCare? If not, didyou reboot the server after applying the kernel update?Applied updates (yum update kernel) but warning message remains...?
Did you reboot the server after applying the kernel update? Thank you.0 -
Hi, I'm using Kernel Care with 66.0.17. I did what cPanelMichael as and reboot and no more kernel message. thanks. 0 -
Same problem here: Running 66.0.17 + KernelCare on all servers - the message never disappears. Had to reboot a server 5 times and still.. the message is here. This is getting very annoying. @ cPanel Team - Please fix this ASAP. 0 -
Hi Michael, Yes, I've rebooted the server more than 3 times, and the warning remains. Also, I've updated the kernel a few more times, both the "cp hardened kernel patch" and the basic yum, (yum update kernel) and rebooted again, and the warning remains. Also (sorry) I've updated to 66.18 - and updated kernel again, and it still show as "old" kernel... root@host.xxxxxxx.eu ~ $ uname -r 2.6.32-642.13.1.el6.x86_64 Any ideas, thank you. Regards, Robin. 0 -
Hi Michael, Yes, I've run "yum -y update kernel" 3 times & rebooted many times, but still the kernel refuses to upgrade, and I still get the warning message. I've also updated to 66.18, but still no improvement. Here is my current grub.conf info... ######################################################### # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/vda1 # initrd /boot/initrd-[generic-]version.img #boot=/dev/vda default=0 timeout=1 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-642.13.1.el6.x86_64) root (hd0,0) kernel /boot/vmlinuz-2.6.32-642.13.1.el6.x86_64 ro root=UUID=585e41ba-db5b-4e24-9b08-e4a27476f5fa rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=noop initrd /boot/initramfs-2.6.32-642.13.1.el6.x86_64.img title CentOS 6 (2.6.32-642.el6.x86_64) root (hd0,0) kernel /boot/vmlinuz-2.6.32-642.el6.x86_64 ro root=UUID=585e41ba-db5b-4e24-9b08-e4a27476f5fa rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=noop initrd /boot/initramfs-2.6.32-642.el6.x86_64.img ####################################################
Any ideas? Thank you. Regards, Robin.0 -
Yes, I've run "yum -y update kernel" 3 times & rebooted many times, but still the kernel refuses to upgrade, and I still get the warning message.
Please post the output from the following command:/usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;'
Thank you.0 -
Please post the output from the following command:
/usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;'
Thank you.
Thanks Michael, I have two cPanel VPS's showing this issue, both at latest version (.18)...root@srv.xxxxxxx.com ~ $ /usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;' $VAR1 = \{ 'reboot_required' => 1, 'boot_version' => '2.6.32-696.1.1.el6.x86_64', 'has_kernelcare' => 0, 'running_version' => '2.6.32-431.20.3.el6.x86_64' }; root@host.xxxxxx.eu ~ $ /usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;' $VAR1 = \{ 'running_version' => '2.6.32-642.13.1.el6.x86_64', 'boot_version' => '2.6.32-696.299.3.2.cp6.x86_64', 'reboot_required' => 1, 'has_kernelcare' => 0 };0 -
Hi Michael, ...and! - I have a third cPanel VPS which ISN'T showing this issue... root@srv.xxxxxeb.ie ~ $ /usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;' $VAR1 = \{ 'boot_version' => '2.6.32-696.299.3.2.cp6.x86_64', 'has_kernelcare' => 0, 'reboot_required' => '', 'running_version' => '2.6.32-696.299.3.2.cp6.x86_64' };0 -
Seems like your Kernel is not actually the one that should be on boot. (except the last results from the latest server you mention.) 0 -
Seems like your Kernel is not actually the one that should be on boot. (except the last results from the latest server you mention.)
Thanks GoZen, I haven't done or changed anything to the two server's setup, so why do you think they won't correctly update - or accept the kernel update? Can I specify which kernel software downloaded into the REM's is to be "accepted" - not sure I understand you comment. But I appreciate you input, as it's puzzling me! - Robin.0 -
I have two cPanel VPS's showing this issue, both at latest version (.18)...
Hello, Can you verify if these servers use KSplice? You can check by using a command such as:uptrack-uname -a
Thank you.0 -
Here is an output from one of my servers that running Cloudlinux 7 + cPanel 66.0.17 + KernelCare The reboot message is always there. Hope this will help debugging. ]# /usr/local/cpanel/3rdparty/bin/perl -e 'use Cpanel::Kernel::Status; use Data::Dumper; my $kernel = Cpanel::Kernel::Status::kernel_status(); print Dumper \$kernel;' $VAR1 = \{ 'running_latest' => '', 'reboot_required' => 1, 'boot_version' => '3.10.0-427.18.2.lve1.4.27.el7.x86_64', 'has_kernelcare' => 1, 'running_version' => '3.10.0-714.10.2.lve1.4.63.el7', 'unpatched_version' => '3.10.0-427.18.2.lve1.4.27.el7.x86_64' };0 -
New Here is an output from one of my servers that running Cloudlinux 7 + cPanel 66.0.17 + KernelCare
The internal case related to KernelCare is not yet published. Here's a link to the post about the current behavior: Post 2472499 Thank you.0 -
Hello, Can you verify if these servers use KSplice? You can check by using a command such as:
uptrack-uname -a
Thank you.
Hi Michael, Thanks for continuing to following up, it's great to have you here to help with matters like these that confound guys like me, you must be one of the busiest members of the great cPanel team!root@host.xxxxxxx.eu ~ $ uptrack-uname -a -bash: uptrack-uname: command not found
Opps, do I have to install Ksplice...? Installing Uptrack Preparation Ksplice is free with Oracle Linux Premier Support. If you do not have Oracle Linux Premier Support and use RHEL or Oracle Linux, you can try Ksplice free for 30 days. Access Key Unless running an instance inside of the Oracle Cloud, you will need an access key to install Ksplice which can be obtained by logging into the Unbreakable Linux Network and following the instructions to register your system for Ksplice. - Robin.0 -
Does this server use KernelCare? If not, didyou reboot the server after applying the kernel update?
Yes, I'm using KernelCare. Until now still get warning message.0 -
Yes, I'm using KernelCare. Until now still get warning message.
The internal case related to KernelCare is not yet published. Here's a link to the post about the current behavior: Post 2472499Opps, do I have to install Ksplice...?
Ksplice is not required. We have a separate case open for systems using Ksplice, so I wanted to verify if you were facing that same issue. Could you open a support ticket using the link in my signature so we can take a closer look at your system? Thank you.0
Please sign in to leave a comment.
Comments
60 comments