Unknown Kernel (CentOS Linux 3.10.0-1062.18.1.el7.x86_64)

[martin MHC]

We receieved a series of alerts this morning from Cron <root@basic> /usr/bin/kcarectl -q --auto-update that :

Unknown Kernel ( CentOS Linux 3.10.0-1062.18.1.el7.x86_64 )

The system Kernel was requesting to be updated last night and this was done so. Ther Kernel does not have a paid Kernelcare .

We have never received this alerty before.
I have read Kernelcare - Unknown Kernel but this doesn't seem to identify the issue and simply states to "wait" which we are uneasy just waiting.

Current stated Kcare version is:
2.24-1.el7
(which seems very old?)

WHM version:
v86.0.16

On CENTOS 7.7


How should we help the system to rediscover the correct kcare version?

 

[cPanelLauren]

Hello,


What has happened is the kernel has updated to a version that kernelcare does not support yet. So, if you're using kernelcare's free symlink protection patch it is not currently covering this kernel version

 

[CloudLinux Skhristich]

Hello Martin,
Your kernel is the newest and not supported yet. This kernel 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. Or you can add in to your /etc/sysconfig/kcare/kcare.conf the following setting to ignore the email notifications with these messages:
IGNORE_UNKNOWN_KERNEL=True
More details here: http://docs.kernelcare.com/index.html?config_options.htm
Once the kernel's support will be added to KC - the warning messages will disappear automatically.
Thanks

 

[martin MHC]

Thank you both for your feedback on this. Cheeers

 

[WorkinOnIt]

@CloudLinux Skhristich

It's great that your company provides this symlink protection for free and I thank you for that, but these notifications are a bit annoying. It seems as though everytime we update the kernel, we get this long delay until you update the patch. It's not really a moan, but curiosity.... Is there not a way to synchronize the rollout between your free patch and the updated kernel when a new version is released?

If one upgrades to the paid Kernel Care from your company, does that then mean a faster coverage of the free kernel patch?

And finally, is there a CloudLinux status page that shows changelog that we can refer to, to see when a new patch is released?

 

[CloudLinux Skhristich]

@CloudLinux Skhristich

It's great that your company provides this symlink protection for free and I thank you for that, but these notifications are a bit annoying. It seems as though everytime we update the kernel, we get this long delay until you update the patch. It's not really a moan, but curiosity.... Is there not a way to synchronize the rollout between your free patch and the updated kernel when a new version is released?

If one upgrades to the paid Kernel Care from your company, does that then mean a faster coverage of the free kernel patch?

And finally, is there a CloudLinux status page that shows changelog that we can refer to, to see when a new patch is released?

Hello,
Thank you for reaching out!
This delay you describe happens mostly because vendors release binaries but not release sources simultaneously. Meaning we should wait for sources to add our support. We do some manual work also to adopt the latest changes. So this amount time, it's a half-day approximately should be counted as well.

In general we're working on improving our time-to-market, so such feedback is greatly appreciated. If you have a specific example of a kernel that was tremendously delayed - please share.

The paid product wouldn't give you the ability to receive coverage faster due to the mentioned reasons.

KernelCare - should give you an ability to monitor releases.

Thank you.

 

[WorkinOnIt]

@CloudLinux Skhristich

That's helped to clear up my understanding, thank you. Could you give a rough estimate of the expected time to market generally - e.g. 7 - 10 days following a new release. And I am assuming we need to manually update kernel care patch from SSH when it's released (assuming one doesn't have the automated kernel care product)

Cheers

 

[CloudLinux Skhristich]

@CloudLinux Skhristich

That's helped to clear up my understanding, thank you. Could you give a rough estimate of the expected time to market generally - e.g. 7 - 10 days following a new release. And I am assuming we need to manually update kernel care patch from SSH when it's released (assuming one doesn't have the automated kernel care product)

Cheers

Hello,
Thanks for following up! We usually add within 5 working days and always strive to do this as quickly as possible.