cPanel reports problem with kernel boot version.

[mariusfv]

There are almost 3 weeks we start to getting this messages in WHM, security advisor:

The system kernel is at version “3.10.0-714.10.2.lve1.5.12.el7”, but is set to boot to version “3.10.0-714.10.2.lve1.5.9.el7.x86_64”.

You must take one of the following actions to ensure the system is up-to-date:

Wait a few days for KernelCare to publish a kernel patch.

Reboot the system.

After reboot is the same situation.

Can Cloudlinux team colaborate with cPanel team to avoid in the near future this kind of situations? Or to try Cloudlinux to update the boot kernel when WHM upgrade?

We bought Cloudlinux & Kernelcare specialy to avoid this threats of security.

[apb]

Marius, fortunately both kernels you mentioned are already supported by KC

[mariusfv]

Cloudlinux 7.4 & WHM/cPanel v68.0.28
The system kernel is at version “3.10.0-714.10.2.lve1.4.77.el7”, but is set to boot to version “3.10.0-714.10.2.lve1.5.9.el7.x86_64”.

You must take one of the following actions to ensure the system is up-to-date:

Wait a few days for KernelCare to publish a kernel patch.

[ighertesco]

Hello,

# uname -r shows the current booted kernel, and # kcare-uname -r shows effective kernel patched by KernelCare.

You can find more info in our docs.

The output looks normal, no actions required.

[ighertesco]

This is based on a result from the security advisor in WHM.
I saw on the forums the ques for this results, thats why I post my question here.

[ighertesco]

Hello,

kcare-uname -r shows effective kernel version, this is normal.

Could you please describe the issue in more details?

[vmarchuk]

Hello, I have WHM CLOUDLINUX 7.4 standard v68.0.21

I got this:
[root@jake ~]# uname -r
3.10.0-714.10.2.lve1.4.74.el7.x86_64
[root@jake ~]# sudo kcare-uname -r
3.10.0-714.10.2.lve1.4.77.el7.x86_64
[root@jake ~]#

It has been there for a couple of weeks or maybe more, I did restart the server a couple of times but no success...

[vmarchuk]

Thank you for your reply.

It appears that this is indeed cPanel bug (CPANEL-15544). A resolution for this case is planned for inclusion with cPanel version 68 and will ensure the reboot warning does not appear on systems using a custom kernel.

[netops]

# uname -r
3.10.0-427.10.1.lve1.4.7.el7.x86_64
# sudo kcare-uname -r
3.10.0-714.10.2.lve1.4.65.el7.x86_64

[vmarchuk]

Hello.

Could you please show me the output of the following commands:
# uname -r
# kcare-uname -r

[2webmaster]

This is a cPanel bug that goes back to at least August. See this cPanel thread for details, https://forums.cpanel.net/threads/wh...pdates.608403/.

[2webmaster]

I have two servers with the same warning. However running uname -r the version that reply is the same as version it claims to want to boot in.

you can check out my post here if you want:

https://www.cloudlinux.com/forum/kernelcare/intersting-email-sent-via-whm

Frank

[2webmaster]

Hi!

A few days ago we received the following message via WHM, Security Advisor:
-------
The system kernel is at version “3.10.0-714.10.2.lve1.4.63.el7”, but is set to boot to version “3.10.0-427.36.1.lve1.4.39.el7.x86_64”.
You must take one of the following actions to ensure the system is up-to-date:
Wait a few days for KernelCare to publish a kernel patch.
Reboot the system.
-------

Although not very happy, we rebooted the server, but the message kept coming up, thus the problem was not solved. We also waited a few days (about 15) in case KernelCare solved the problem itself... but still the problem exists up until now.
Our cPanel version is v66.0.23 on Cloudlinux 7.

Please advise.