SOLVED kcarectl error

[eitanc]

Hi,

I get alert email with:
Subject: Cron <[email protected]> /usr/bin/kcarectl -q --auto-update
Body: The `free` type patch is not found for your kernel. Please select existing patch type

I use the latest cpanel, 90.0.17 and latest centos 7 kernel.

What can I do to solve this?

 

[andrew.n]

It's a recent bug..they fixed it once but looks like it came back...what does your cron entry says? (etc/cron.d/kcare-cron)

 

[vacancy]

'free' patch type is unavailable for your kernel

Hello I am using kernel-3.10.0-1160.2.2.el7, I applied the free patch for this kernel a few days ago but now the following error appears when cron runs for 4 hours. The `free` type patch is not found for your kernel. Please select existing patch type *** The same error appears when I update...

www.cloudlinux.com

 

[cPRex]

@eitanc - can you let me know if things are working know after the response that @vacancy posted?

 

[eitanc]

OK, I run "kcarectl --update --test" twice:
1st:
"
Patch level 5 applied. Effective kernel version
Kernel is safe
"

2nd:
"
Updates already downloaded
No updates are needed for this kernel
Kernel is safe
"

If the issue will return - I will post about it here.

If all is OK - I will simply keep quiet and you can assume the issue is fixed by this move.

Thank you guys!

 

[eitanc]

The funny thing, btw, is that I do not use cloudlinux, so I it is not clear how this component is active for my cpanel.

 

[vacancy]

Kernelcare is developed by a cloudlinux. You don't need to use cloudlinux to use kernelcare.

You can run the commands below to see if the patch is active. If it returns 1 and 99, the patch is active.

sysctl -n fs.enforce_symlinksifowner
sysctl -n fs.symlinkown_gid

 

[eitanc]

Yep, I got the replies of 1 and 99, so it should be fine.
Thanks!

 

[cPRex]

I'm glad you were able to get this worked out!

 

[eitanc]

Well, guys, it came back, the same... what else can I do?

 

[morrow95]

Here for the same reason except mine is

The `extra` type patch is not found for your kernel. Please select existing patch type

I assume because I pay the $3 monthly my patch is different. From the link above at cloudlinux it looks like this should be fixed on Monday.

 

[cPRex]

It does look like this is scheduled to be resolved with a CloudLinux release on Monday, but you can always put in a ticket with our team if you'd like us to check things on our end just for peace of mind :D

 

[eitanc]

Thanks, but I will avoid bothering you guys and girls and I will wait for the great Monday...
Do I need to manually run any command on Monday to get this fix?

 

[cPRex]

The automatic updates on the system will take care of this so you won't need to do anything, if you have automatic updates enabled.

 

[eitanc]

Cool, thanks!

 

[morrow95]

"The `extra` type patch is not found for your kernel. Please select existing patch type"

Started back up for me. I just started paying the $3 monthly this past summer so kernel updates would be auto and this is at least the 3rd time there has been a 'problem' similar to this with KernelCare. The quality control of this needs to be stepped up a little in my opinion. One of the main points of KernelCare is updating the kernel unattended/automatically. If a kernel update is available it should only be updating if there is a patch available as well for that updated kernel - right? That and the patch release should be tested before going live. I would think these errors would be easy to avoid yet they keep happening. The last thing that should be happening is a kernel update if a patch doesn't exist or fails.

 

[cPRex]

@morrow95 - can you look at our guide here for more details on this issue?

Which KernelCare patch type should I use?

The best KernelCare patch type for you depends on your operating system. Consult with the chart below to find the most suitable patch type for your situation. Select the patch type I have C...

support.cpanel.net

This explains more about the patch type and will help work through those errors.

 

[andrew.n]

@morrow95 it's a bug again which they supposed to fix by now fyi.

 

[morrow95]

@morrow95 it's a bug again which they supposed to fix by now fyi.

I figured as much. The last time this happened it took a few days for them to update and the problem went away, but here we are again. Stuff like this kind of defeats the purpose of paying for the automatic/unattended ability IMO.

 

[andrew.n]

Well it won't affect the purpose I mean if there is a patch available for the kernel it will still patch it but due to the bug if there is no patch the warning message is not being suppressed