Enable Linux kernel update during nightly maintenance

[MajorLancelot]

Does it really make sense to enable this when Kernelcare is installed?

Perhaps part of the tool-tip should say something about this.

Please what saith the community, gurus and moderators?

Thanks!

 

[Jcats]

Does it really make sense to enable this when Kernelcare is installed?

kernelcare is for kernel security related patches only, so because of that its still good to reboot into the new kernel. It just means you don't have to do it right away, plan your maintenance window and reboot at a later time. If you feel you will not benefit from any of the fixes/enhancements from the pending kernel release then just ignore it and don't reboot until one comes along that you would like to benefit from.

 

[MajorLancelot]

kernelcare is for kernel security-related patches only, so because of that its still good to reboot into the new kernel. It just means you don't have to do it right away, plan your maintenance window and reboot at a later time. If you feel you will not benefit from any of the fixes/enhancements from the pending kernel release then just ignore it and don't reboot until one comes along that you would like to benefit from.

Thanks, Jcats.

Rebooting a machine for necessary maintenance, such as to apply updates has always been part of system administration.

Yes, it's the recommended step to reboot a system after a kernel update.

However, Kernelcare marketing defines the tool as one that keeps "kernels secure & end reboots".

In fact, a visit to https://www.cloudlinux.com/all-products/product-overview/kernelcare touts how long it has been since the last reboot.

This question came to my mind when after running Security Advisor which advised rebooting the system or waiting for Kernelcare to do its thing.

But there were updates that CLoudLinux pushed & running a simple "yum -y update" & rebooting, two machines went unrecoverably dead.

I might be wrong but perhaps the right thing to do is to embrace one and leave the other.

I hope Igor or someone from the cPanel team will chip in on this.

Thanks again.

 

[cPanelMichael]

This question came to my mind when after running Security Advisor which advised rebooting the system or waiting for Kernelcare to do its thing.

Hello @MajorLancelot,

Internal case CPANEL-21707 fixes the false reboot suggestion when KernelCare is running and should address the concern you noted. It's planned for inclusion with an upcoming build of cPanel & WHM version 74. You can monitor the version 74 Change Log for this case number at:

74 Change Log - Change Logs - cPanel Documentation

Thank you.

 

[MajorLancelot]

Hello @MajorLancelot,

Internal case CPANEL-21707 fixes the false reboot suggestion when KernelCare is running and should address the concern you noted. It's planned for inclusion with an upcoming build of cPanel & WHM version 74. You can monitor the version 74 Change Log for this case number at:

74 Change Log - Change Logs - cPanel Documentation

Thank you.

Thank you, @[URL='https://forums.cpanel.net/members/cpanelmichael.256941/']cPanelMichael[/URL].
We will refrain from updating and rebooting any system until this is fixed.

 

[cPanelMichael]

We will refrain from updating and rebooting any system until this is fixed.

Hello @MajorLancelot,

Please feel free to update or reboot a system when necessary. The referenced case softens the reboot notification in Security Advisor on systems using KernelCare, but it doesn't negate the need to continue updating your system or kernel when needed.

Thank you.