kcarectl --auto-update --gradual-rollout=auto

[Nirjonadda]

Getting one email about kcarectl --auto-update --gradual-rollout=auto. Please let me know that what is happened?

Cron <[email protected]> /usr/bin/kcarectl --auto-update --gradual-rollout=auto

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

 

[rpvw]

That email indicates that you have installed a kernel that either has no Kernelcare patches applied to it as yet, or that is unsupported by Kernelcare.

Assuming it is a supported kernel, you will receive an email every 4 hours (the default frequency that Kernelcare checks for available kernel patches) until Cloudlinux has issued a patch for that particular kernel, and your system has downloaded it and installed it.

If it is an unsupported kernel, you will receive that email message indefinitely, and should investigate whether you are running a compatible kernel to work with Kernelcare.

I always get the same messages after re-basing my kernels to the latest issued. In theory, one shouldn't need to update the kernel at all if you are using Kernelcare, but I choose to re-base once a year (because I am old and grumpy and set in my ways !)

 

[cPanelMichael]

Hello,

The answer in the previous post is correct. Let us know if you have any additional questions.

Thank you.

 

[Nirjonadda]

Hello,

The answer in the previous post is correct. Let us know if you have any additional questions.

Thank you.

Yes but Its kernel installed by CENTOS yum update. So Kernelcare free patches are not work any more?

 

[cPanelMichael]

Yes but Its kernel installed by CENTOS yum update. So Kernelcare free patches are not work any more?

Hello,

CloudLinux explains why this happens on the following thread in their support forums:

Kernelcare - Unknown Kernel

This happens when CentOS publishes a new kernel, and CloudLinux has yet to release a patch for that kernel (it can sometimes take a few days before CloudLinux publishes the update).

Thank you.

 

[DriveSafe]

I got this message from Security Advisor, so I followed the instructions:

The system kernel is at version “3.10.0-693.21.1.el7.x86_64”, but an update is available: 3.10.0-862.el7.x86_64 Update the system (run “yum -y update” on the command line...)

yum updated to 3.10.0-862.2.3.el7.x86_64 (CentOS 7), and now I'm getting this error every four hours. Is it because it's .2.3 version of 3.10.0-862? If so, will kcare catch up eventually or is there a way to turn off the errors? Or am I better off rolling it back somehow?

edit: After checking KernelCare Directory I see that 862 isn't on the list, so I apparently jumped the gun with the update via yum. Is the kernel safe to run anyways while I wait for kcare to catch up? Maybe I should just turn kcare off until it does to avoid the emails every 4 hours?

 

[Fabio Jose]

Olá amigo
Eu estava recebendo esta mensagem também e depois de executar "yum update" ele fez a nova atualização do kernel e a mensagem desapareceu !!!
Obrigado !

 

[cPanelMichael]

Hello @DriveSafe and @Fabio Jose,

This is a separate issue that we are tracking on the following forums thread:

Security Advisor on CentOS7 servers with KernelCare have an incorrect reboot message.

Thank you.