Noticing this now with CentOS kernel 2.6.32-642.el6, which is weird because the kernelcare kernel is using this version
# uname -r
# kcarectl --check
Unknown Kernel (CentOS 2.6.32-642.el6.x86_64)
# kcare-uname -r
Also getting an unknown kernel for the latest OpenVZ RHEL6 kernel - 042stab116.1.
After the cPanel 66.0.29 update installed last night, I began seeing the Security Advisor warning that I had no symlink race condition protection, and began investigating because I had successfully installed the "Extra" patchset for version 66.0.26. I'm getting the same error about the "Unknown kernel" as Derek. When I try to run the command:
Unknown kernel (CentOS 2.6.32-696.13.2.el6.x86_64), no patches available
I'm not sure, but I think the problem may be that Kernelcare is misidentifying the kernel. Take a look at what uname and kcare-uname output:
This kcare-uname -r issue is something we are aware of -- and will be fixing soon (2-4 weeks).
The issue with security advisor is that it doesn't know about extra/free patches and that it fixes symlink issue. cPanel team is aware of it, and is working on it as well. We got very early / approximate ETA of 2-3 months from now for the fix in security advisor.
Thanks for the info, Igor, but I am confused. The main issue for now is getting the "Extra" patch installed when the kernel is unrecognized. Are you saying it will be 2-4 weeks before we can expect a way to do so?
No, the new kernel will be supported in a few days. Overall, it is not worth it to update to a new kernel if you have KC. All critical security vulnerabilities are fixed in advance, so you do a reboot for nothing.
It is not on the list of supported kernels, unless you are very slow in updating the lists
We get this every time there is a kernel update & kernelcare is 3 or 4 days or even 1 week late in adding it after Cpanel does an auto-update & forces you to reboot
Unknown Kernel (CentOS 2.6.32-696.20.1.el6.x86_64) http://patches.kernelcare.com/
Shows most recent version as
kernel-2.6.32-696.18.7.el6(Last Updated: 2018-01-10 13:37:30)
Derek, sorry to misinform you.
This kernel is not in the list of supported as it has no known security vulnerabilities, and this is why we haven't built a stub for it yet.
You can safely ignore these warning messages ("Unknown Kernel" ). Or you can add in to your /etc/sysconfig/kcare/kcare.conf the following setting to ignore these messages:
More details here: http://docs.kernelcare.com/index.html?config_options.htm
Usually, we add KC support for the new kernels within 3-4 days.
You can always check if KernelCare supports your current kernel here: http://patches.kernelcare.com/