upsforum

Well-Known Member
Jul 27, 2005
473
0
166
every 4 hours I receive this alert from all my vps:

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

thi is the command: Cron <[email protected]> /usr/bin/kcarectl --auto-update --gradual-rollout=auto

I can hide this alert or I need of fix it?
 

sparek-3

Well-Known Member
Aug 10, 2002
2,051
232
368
cPanel Access Level
Root Administrator
CloudLinux/Kernelcare not releasing Kernelcare updates in a timely fashion?!?! Say it ain't so!

Seriously people, use the forum search.

CloudLinux (these people also make KernelCare) have a forum you can complain to - CloudLinux - Main | New template

You may have to scroll down to see the Kernelcare forum. I know.. that's a little bit of work, it doesn't jump out of the screen and punch you when you visit the site.
 
  • Like
Reactions: rpvw

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,295
1,275
313
Houston
Hello @upsforum

As indicated already, there is a lot of posts on this already. Ultimately it boils down to either kernelcare full or symlink protection is not supporting your current kernel. This is either because of a recent update and they have yet to patch it or you're using a non-stock kernel. In your case, the issue is that they haven't patched it as of yet.

This is also noted in their forums here when will free-patch support be added for CentOS Kernel 3.10.0-862.11.6.el7.x86_64

It appears they're planning on releasing the patch today.

Thanks!
 

baronn

Member
Dec 27, 2017
24
6
3
manchester
cPanel Access Level
Root Administrator
We are having the same issue as @upsforum

For managing 1 server/vps its not an issue. We can patiently wait for an updated patch set but when managing multiple servers/vps every 4 hours we get inundated with cron emails! My inbox gets clogged up every 4 hours. Not good.

This started after the maintenance release on the 5th dec 2018. It was a easy fix in that instance by just updating the frequency longer than 4 hours. However another security release was on the 13th dec 2018 and the crons have gone back to 4 hours.

Q. how can we adjust the cron time schedule to say 12/24 hours delay rather than every 4 hours? and keep that in place IF another release to rpms is given? Need to do this on multiple set-ups...