Forum
  1. Forums
  2. KernelCare
  3. KernelCare General Discussion
  1. Scott Mutter
  2. Monday, March 26, 2018
  3.  Subscribe via email
CentOS released kernel-2.6.32-696.23.1 on March 14th.

I am still showing Kernelcare using 2.6.32-696.20.1.

Are there plans to rebase Kernelcare to 2.6.32-696.23.1? That's typically what happens. It doesn't look like the patches applied to the upstream 2.6.32-696.23.1 kernel have been applied with Kernelcare. Granted, the changes don't appear to be very vital:

https://access.redhat.com/errata/RHSA-2018:0512

But typically I prefer to see the Kernelcare kernel being used being up to date with what upstream is using.

I thought this might've been an oversight.
Rate this post:
  1. 27.03.2018 11:03:36
  2. # 1
Posts: 172
Joined: 31.01.2017
0
Votes
Undo
Scott,

Please, find the updated reply below
  1. 27.03.2018 16:03:20
  2. # 2
Scott Mutter Accepted Answer
Posts: 56
Joined: 23.04.2014
0
Votes
Undo
Not really an issue of whether or not Kernelcare support the kernel.

It's a question of "why isn't kcarectl --uname reporting the kernel version as being 2.6.32-696.23.1?"


# uname -r
2.6.32-696.18.7.el6.x86_64
# kcarectl --uname
2.6.32-696.20.1.el6
# kcarectl --check
The latest patch is applied.
# kcarectl --update
Kernel is safe
# kcarectl --uname
2.6.32-696.20.1.el6
# kcarectl --check
The latest patch is applied.
# kcarectl --patch-info | head -n 5
OS: centos6
kernel: kernel-2.6.32-696.18.7.el6
time: 2018-03-08 16:53:50


Again...

The latest version of the CentOS 6 kernel is 2.6.32-696.23.1.

As you can see in this example, the underlying kernel being run on this server is 2.6.32-696.18.7 - because I haven't rebooted in quite a while.

kcarectl --uname is reporting the kernel version as being 2.6.32-696.20.1 why isn't this reporting 2.6.32-696.23.1?

CentOS released the 2.6.32-696.23.1 kernel on March 14th, 2018. According to the patch-info from Kernelcare, the kernel that Kernelcare is running was last updated on 2018-03-08 16:53:50.

Now to be clear, I'm not really having any issues. I don't think the 2.6.32-696.23.1 kernel that CentOS released really fixes anything major. And rebasing the Kernelcare kernels to their upstream equivalents isn't something your team necessarily has to do - but it is something that your team typically does.

I'm just wondering if this was an oversight. It's March 27th now, it's been nearly two weeks since CentOS released the 2.6.32-696.23.1 kernel. That's what makes me think that this may be something that slipped through the cracks.
  1. 28.03.2018 11:03:37
  2. # 3
Posts: 172
Joined: 31.01.2017
0
Votes
Undo
Scott,

I've got an update from KernelCare developers that the latest patch set contains all security fixes to make the kernel to be patched to the level of v.2.6.32-696.23.1. However, 'kcarectl --uname' still shows the previous kernel version (2.6.32-696.20.1) because we have some difficulties with kernel version displaying. Please note, that this is only displaying issue, it will be fixed shortly as our developers are working on it at this moment.
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
Guest
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,zip,rar,pdf
• Remove Upload Files (Maximum File Size: 2 MB)
You may insert polls into your post. The poll would then appear in the post.
Vote Options
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.