Kernel version and system release don't match
Hi,
on my VPS with cPanel and KernelCare installed i noticed that Security Advisor takes too much time to finish, especially during Cpanel::Security::Advisor::Assessors::Kernel 1.06
I checked the kernel version and this is the output
The system release is
Now why there is a difference between the kernel ver and release. CentOS 7.6 kernel version is 3.10.0-957 not 3.10.0-327 o_O Update: when Security Advisor finish (about 8 mins), this is the message about kernel
I checked kernelcare info and this is the output
I'm a bit confused :confused: What's wrong with that???
uname -s -r
Linux 3.10.0-327.4.4.el7.centos.plus.x86_64The system release is
cat /etc/system-release
CentOS Linux release 7.6.1810 (Core)Now why there is a difference between the kernel ver and release. CentOS 7.6 kernel version is 3.10.0-957 not 3.10.0-327 o_O Update: when Security Advisor finish (about 8 mins), this is the message about kernel
The system kernel is up-to-date at version "3.10.0-957.10.1.el7".I checked kernelcare info and this is the output
kcarectl --info
kpatch-state: patch is applied
kpatch-for: Linux version 3.10.0-327.4.4.el7.centos.plus.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Wed Jan 6 00:35:56 UTC 2016
kpatch-build-time: Mon Apr 1 23:22:58 2019
kpatch-description: 247-:1557788646;3.10.0-957.10.1.el7I'm a bit confused :confused: What's wrong with that???
-
on my VPS with cPanel and KernelCare installed i noticed that Security Advisor takes too much time to finish, especially during Cpanel::Security::Advisor::Assessors::Kernel 1.06
Hello, To update, the Security Advisor scan could not finish on the affected system due to a firewall rule blocking connections to the IP addresses associated with one of the system's YUM repos. Disabling the firewall rule that blocked these IP addresses allowed Security Advisor scan to finish successfully. [QUOTE]The system kernel is up-to-date at version "3.10.0-957.10.1.el7".
This message is accurate, as your system kernel version you see in the uname output won't change until the server is rebooted. With KernelCare, your system is operating with a live patched kernel (use kcarectl --info to see the version) despite what appears in the uname output. Thank you.0
Please sign in to leave a comment.
Comments
3 comments