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 ~]#
-
Hello, So, finally, will this issue be solved by cPanel update sooner or later? 66.0.19 has been released. Running Cloudlinux 7.4 + cPanel 66.0.18 + KernelCare Kernel version is the latest, but WHM shows, "You must reboot the server to apply kernel updates." root@server [~]# /usr/bin/kcarectl --info kpatch-state: patch is applied kpatch-description: 326-;3.10.0-714.10.2.lve1.4.63.el7 Thanks. 0 -
Running Cloudlinux 7.4 + cPanel 66.0.18 + KernelCare Kernel version is the latest, but WHM shows, "You must reboot the server to apply kernel updates."
The internal case related to KernelCare is not yet published. Here's a link to the post about the current behavior: Post 2472499 I'll update this thread as soon as more information on the case is available. Thank you.0 -
The internal case related to KernelCare is not yet published. Here's a link to the post about the current behavior: Post 2472499 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.
Yes, I'll do that now... thanks.0 -
I am currently attempting to help with the ticket, and noticed that the current installed v of my kernel and the newer (required) one are advisied in WHM's Security Advisor, but despite my rebooting the VPS they remain the same. Are the two differing GRUB files to blame.... /etc/grub.conf and /boot/grub/grub.conf I notice there are two in the system, and /etc/grub.conf has the correct updated kernel listed at it's top. Also, it's symlinked to/boot/grub/menu.lst which I believe is correct. (?) See attached image / screen-grab for info., perhaps this is helpful? - Robin. - Removed - 0 -
Hi @RobinF28, I see we are assisting you as part of ticket number 8865743. I'll monitor the ticket and update this thread with the outcome once it's closed. Thank you. 0 -
Thanks Michael. Yes, the issue with my particular VPS's was that the GRUB symlink setup was not correct when they were provisioned. To help anyone else following this thread who might have the same issue as I had, I have copied the good work & explanation your colleague did below... The menu.lst file should be a symlink to the grub.conf file under "/boot/grub" but this was not the case. By default grub looks at the grub.conf file when booting and updates add new kernel information to the menu.lst file when updating so there was a discrepancy between what kernel was booting and which kernel cPanel saw as installed.
Thank you for your help with this matter. - Robin.0 -
Same issue for me on all my cPanel servers. [LIST] - v66.0.23 You must reboot the server to apply kernel updates.
0 -
Same issue for me on all my cPanel servers. [LIST]
- v66.0.23 You must reboot the server to apply kernel updates.
I've been getting the same thing for over a month now. cPanel blames CL. CL blames cPanel. Not sure what the fix is, to be honest.0 -
Same issue for me on all my cPanel servers.
I've been getting the same thing for over a month now.
Is KernelCare installed on these systems? If so, note that there's no update to report on internal case CPANEL-15544 at this time. I'll update this thread with more information as soon as it's available. In the meantime, you can review this post for information about this case: WHM v66.0.14 - You must reboot the server to apply kernel updates Thank you.0 -
Is KernelCare installed on these systems?
Yes. The Cloudlinux folks told me that it was resolved in 66.0.17, however. I'm running .23. I'm guessing by the open case you list that it was not resolved in .17. No worries, just thought it was fixed.0 -
I got the same message lately... Tried to update and "/usr/bin/kcarectl --uname" - nothing helped :/ 0 -
Got the same message on 66.0.23, with KernelCare installed, did a reboot and it still there. 0 -
Got the same message on 66.0.23, with KernelCare installed... snipped
I ran this today on my servers w/KernelCare. Seems to have updated proper and the reboot message is gone now: WebHost Manager "Software "System Update, Include kernel packages0 -
I`ve got the same message on 66.0.23, yum update kernel and rebooting the vps does not work. Here are some info. : root@host [~]# which kcarectl /usr/bin/kcarectl
root@host [~]# /usr/bin/kcarectl --info kpatch-state: patch is applied kpatch-for: Linux version 3.10.0-514.26.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Tue Jul 4 15:04:05 UTC 2017 kpatch-build-time: Mon Sep 25 16:28:23 2017 kpatch-description: 9-;3.10.0-693.2.2.el7
root@host [~]# /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, 'unpatched_version' => '3.10.0-514.26.2.el7.x86_64', 'has_kernelcare' => 1, 'boot_version' => '3.10.0-514.26.2.el7.x86_64', 'running_version' => '3.10.0-693.2.2.el7' }; root@host [~]#0 -
Any update on this issue? My servers also exhibit this behavior running kcare /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' => '', 'unpatched_version' => '3.10.0-514.26.2.el7.x86_64', 'running_version' => '3.10.0-693.2.2.el7', 'has_kernelcare' => 1, 'boot_version' => '3.10.0-514.26.2.el7.x86_64', 'reboot_required' => 1 0 -
Hello, on my server i have running CENTOS 6.9 standard [server] v66.0.23. I also have installed KernelCare. Here is the output of /usr/bin/kcarectl --info: kpatch-state: patch is applied kpatch-for: Linux version 2.6.32-696.3.2.el6.x86_64 (mockbuild@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Tue Jun 20 01:26:55 UTC 2017 kpatch-build-time: Fri Sep 29 14:02:35 2017 kpatch-description: 207-;2.6.32-696.10.3.el6 The problem is that whm always alerts "You must reboot the server to apply kernel updates.". I have done this several times and the message is still there. The security advisor raises a Info with: "The system kernel is up-to-date at version "2.6.32-696.10.3.el6", thanks to KernelCare patches. However, on reboot, the system will briefly start with version "2.6.32-696.3.2.el6.x86_64" before being patched again by KernelCare.Install the latest "kernel" RPM package to immediately boot into the latest kernel.". Please help me to solve this issue. Thanks, Harald 0 -
Today I rebooted the vps and the warnign to reboot disappeared. 0 -
Hello, on my server i have running CENTOS 6.9 standard [server] v66.0.23. I also have installed KernelCare. Here is the output of /usr/bin/kcarectl --info: kpatch-state: patch is applied kpatch-for: Linux version 2.6.32-696.3.2.el6.x86_64 (mockbuild@c1bl.rdu2.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) ) #1 SMP Tue Jun 20 01:26:55 UTC 2017 kpatch-build-time: Fri Sep 29 14:02:35 2017 kpatch-description: 207-;2.6.32-696.10.3.el6 The problem is that whm always alerts "You must reboot the server to apply kernel updates.". I have done this several times and the message is still there. The security advisor raises a Info with: "The system kernel is up-to-date at version "2.6.32-696.10.3.el6", thanks to KernelCare patches. However, on reboot, the system will briefly start with version "2.6.32-696.3.2.el6.x86_64" before being patched again by KernelCare.Install the latest "kernel" RPM package to immediately boot into the latest kernel.". Please help me to solve this issue. Thanks, Harald
Today i run "yum update kernel" and successfully installed the new kernel "2.6.32-696.3.2.el6.x86_64". After that i got a little bit shocked because after a Graceful Server Reboot didn't work and i couldn't reach the server. So i sent a hard reset to the server. After that the server restarted successfully ... and the message is gone also the info message in the security advisor. So now i am running CENTOS 6.9 (kernel 2.6.32-696.3.2.el6.x86_64) with whm verison 66.0.23 and everything works as expected.0 -
Hello, To update, a resolution for internal case CPANEL-15544 is planned for inclusion with cPanel version 68 and will ensure the reboot warning related to a mismatched boot version and running version of the kernel does not appear on systems using a custom kernel, or on systems with kernels managed by KernelCare. Thank you. 0 -
Hi, Updated my vps to v66.0.25 and it's got the yellow banner up the top of WHM asking me to reboot. Running Kernal care on the system. CloudLinux release 7.4 (Georgy Grechko) [root@************~]# /usr/bin/kcarectl --info kpatch-state: patch is applied kpatch-for: Linux version 3.10.0-714.10.2.lve1.4.65.el7.x86_64 (mockbuild@build.cloudlinux.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Tue Sep 26 06:53:51 EDT 2017 kpatch-build-time: Thu Oct 12 13:19:47 2017 kpatch-description: 2-;3.10.0-714.10.2.lve1.4.66.el70 -
Updated my vps to v66.0.25 and it's got the yellow banner up the top of WHM asking me to reboot. Running Kernal care on the system.
The resolution is not part of cPanel version 66. It's included in cPanel version 68: Fixed case CPANEL-15544: Making reboot recommendation banner less sensitive. Thank you.0 -
The resolution is not part of cPanel version 66. It's included in cPanel version 68: Fixed case CPANEL-15544: Making reboot recommendation banner less sensitive. Thank you.
Hello, Now WHM version is 68.0.12. Does it mean that this warning messages disappear once reboot is done now? Did anyone succeed? Thanks.0 -
Does it mean that this warning messages disappear once reboot is done now? Did anyone succeed?
Hi @sadasan, In cPanel 68, the banner suggesting a reboot due to a mismatched installed kernel version compared to the booted kernel version will not appear on systems using KernelCare or a custom kernel type. Thank you.0 -
49531 Hi @sadasan, In cPanel 68, the banner suggesting a reboot due to a mismatched installed kernel version compared to the booted kernel version will not appear on systems using KernelCare or a custom kernel type. Thank you.
Hello, Must I reboot, then does the warning message disappear? Thanks.0 -
I am getting the same message. I do not use kernel care. I'm using Virtuozzo, which my hosting company (ServInt) says updates and protects the kernel. Can WHM please be fixed to stop showing this message? I do not want to restart my server on normal updates.
Yes, the best way is to disappear this message without rebooting, it's the merit of kernel care. I am waiting for the update of cPanel engineer whether one time reboot is required after the fix of the issue of CPANEL-15544.0 -
In my case, the "You must reboot" message disappeared after I did a Graceful Reboot in WHM (the preferred way to restart the server), following instructions from my hosting company, ServInt. I also found out that the reason WHM/cPanel won't restart the system automatically after a routine maintenance or update at 3 AM is that they want that procedure to be harmless, and rebooting is not always so (sometimes daemons are not restarted, they say). As a side note, there is a bug in Graceful Reboot in which a message appears saying that the reboot is starting, but no message ever appears saying that it is done (possibly due to simple programming). You can tell when it is done manually by running the Linux command "uptime" at the command prompt. If the uptime is very small, the system restart has completed. If you find that Graceful Reboot takes more than 15 minutes, there is a WHM option to speed it up, sometimes enormously so (WHM > Service Configuration > Apache Configuration > Piped Log Configuration). See WHM Graceful Reboot takes a very long time | Web Hosting Talk webhostingtalk.com/showthread.php?t=1678157 . All this information deserves to be better known. 0 -
I am getting the same message. I do not use kernel care. I'm using Virtuozzo, which my hosting company (ServInt) says updates and protects the kernel. Can WHM please be fixed to stop showing this message? I do not want to restart my server on normal updates.
Are you sure it's due to the kernel version? Check the output of the following command to see why a reboot is recommended:/usr/local/cpanel/3rdparty/perl/*/bin/perl -mCpanel::Serverinfo::CachedRebootStatus -e 'use Data::Dumper; print Dumper(Cpanel::Serverinfo::CachedRebootStatus->system_needs_reboot());'
Thank you.0 -
I never said it was "due to the kernel version", whatever you mean by that. Anyway, here is the result of that command: $VAR1 = { 'details' => {}, 'needs_reboot' => 0 }; 0 -
49599 My current inquiry is very simple. I'm still seeing "reboot message" on WHM v68 and want to erase it. How should I do? As for a long rebooting time, I guess that fsck may be running when graceful reboot is done. reboot -f from command line may solve it. 0 -
I never said it was "due to the kernel version", whatever you mean by that. Anyway, here is the result of that command: $VAR1 = { 'details' => {}, 'needs_reboot' => 0 };
I notice you mentioned the banner stopped appearing after a graceful reboot. Can you verify if the message continues to appear after additional updates? Thank you.0
Please sign in to leave a comment.
Comments
60 comments