Skip to main content

Kernelcare - Unknown Kernel

Comments

34 comments

  • Scott Mutter
    I get the following error when running kcarectl:

    # kcarectl --check
    Unknown Kernel (CentOS 2.6.32-573.18.1.el6.x86_64)

    # kcarectl --version
    2.5-2
    0
  • Chris Danks
    HI
    you can only use kernel care with cloudlinux and not centos
    0
  • Igor Seletskiy (iseletsk
    KernelCare works with CentOS kernel as well as bunch of others, like Ubuntu, Debian, RHEL, Virtuozzo, Proxmox.
    This particular kernel was recognized on Feb 14th.
    0
  • Scott Mutter
    Noticing this now with CentOS kernel 2.6.32-642.el6, which is weird because the kernelcare kernel is using this version

    # uname -r
    2.6.32-642.el6.x86_64
    # kcarectl --check
    Unknown Kernel (CentOS 2.6.32-642.el6.x86_64)
    # kcare-uname -r
    2.6.32-642.el6.x86_64

    Also getting an unknown kernel for the latest OpenVZ RHEL6 kernel - 042stab116.1.

    # uname -r
    2.6.32-042stab116.1
    # kcarectl --check
    Unknown Kernel (CentOS 2.6.32-042stab116.1)
    # kcare-uname -r
    2.6.32-042stab116.1
    0
  • Bob Lindner
    Did you ever get a resolution on this? We are seeing the same thing today, for kernel CentOS 2.6.32-696.10.3.el6.x86_64

    - Scott
    0
  • Bob Lindner
    I have just purchased kernel care via cpanel and it appears to have installed correctly. however I get this message when trying to install extra patches as shown in this post https://www.cloudlinux.com/imunify360-imunifysensor-blog/entry/the-kernelcare-extra-patchset-with-symlink-protection-is-now-available

    root [/]# kcarectl --set-patch-type extra --update
    Unknown Kernel (CentOS 2.6.32-696.13.2.el6.x86_64)
    root [/]# _


    Why am I paying for something that doesn't work.
    0
  • Irina Semenova
    This kernel should work. Could you check again, please? Or you can create support ticket and we will fix your problem shortly!
    0
  • Jay
    After the cPanel 66.0.29 update installed last night, I began seeing the Security Advisor warning that I had no symlink race condition protection, and began investigating because I had successfully installed the "Extra" patchset for version 66.0.26. I'm getting the same error about the "Unknown kernel" as Derek. When I try to run the command:

    kcarectl --patch-info

    I get:

    Unknown kernel (CentOS 2.6.32-696.13.2.el6.x86_64), no patches available

    I'm not sure, but I think the problem may be that Kernelcare is misidentifying the kernel. Take a look at what uname and kcare-uname output:

    [root@host ~]# uname -r
    2.6.32-696.13.2.el6.x86_64

    [root@host ~]# kcare-uname -r
    2.6.32-696.13.2.el6.x86_64.x86_64

    Kcare-uname has an extra ".x86_64" tacked on the end of the kernel name. That can't be good.

    Is there any fix for this yet?
    0
  • Igor Seletskiy (iseletsk
    This kcare-uname -r issue is something we are aware of -- and will be fixing soon (2-4 weeks).

    The issue with security advisor is that it doesn't know about extra/free patches and that it fixes symlink issue. cPanel team is aware of it, and is working on it as well. We got very early / approximate ETA of 2-3 months from now for the fix in security advisor.
    0
  • Jay
    Thanks for the info, Igor, but I am confused. The main issue for now is getting the "Extra" patch installed when the kernel is unrecognized. Are you saying it will be 2-4 weeks before we can expect a way to do so?
    0
  • Igor Seletskiy (iseletsk
    No, the new kernel will be supported in a few days. Overall, it is not worth it to update to a new kernel if you have KC. All critical security vulnerabilities are fixed in advance, so you do a reboot for nothing.
    0
  • Igor Seletskiy (iseletsk
    I am also getting the following message

    /usr/bin/kcarectl --update
    Unknown Kernel (CloudLinux 3.10.0-714.10.2.lve1.5.3.el7.x86_64)
    0
  • Igor Seletskiy (iseletsk
    Now getting Unknown Kernel (CentOS 2.6.32-696.18.7.el6.x86_64)
    /usr/bin/kcarectl --auto-update --gradual-rollout=auto

    why is cloudlinux so slow on updating kernel care to fix these new bugs
    0
  • Igor Seletskiy (iseletsk
    Why: Details are here: https://www.cloudlinux.com/cloudlinux-os-blog/entry/intel-cpu-bug-kernelcare-and-cloudlinux

    We are the only vendor who is even trying to get the patch. Everyone else gave up even before they started due to how massive change is, and how hard it is to apply to the running kernel.
    0
  • Marci
    Also getting Unknown kernel for CentOS6.9 latest... on the free patch type (for symlink protection).

    # kcarectl --set-patch-type free --update
    Unknown Kernel (CentOS 2.6.32-696.18.7.el6.x86_64)

    # kcarectl --check
    Unknown kernel (CentOS 2.6.32-696.18.7.el6.x86_64), no patches available

    # kcarectl --version
    2.14-2

    # uname -r
    2.6.32-696.18.7.el6.x86_64

    # kcare-uname -r
    2.6.32-696.18.7.el6.x86_64.x86_64

    (Following guidance at https://documentation.cpanel.net/display/EA4/Symlink+Race+Condition+Protection for rolling back from their now-discontinued hardened kernel and https://www.cloudlinux.com/kernelcare-blog/entry/symlink-protection-patchset-centos-6-7-kernelcare?start=20)
    0
  • Alexandre Parubochyi
    New kernels are usually added to the list of supported by KernelCare within a few days. This error will disappear since then, so no additional actions are required from customer's side.
    0
  • Marci
    Excellent - thanks Alexandre...
    0
  • Marci
    Any ideas when kernelcare will update to
    root [/]# /usr/bin/kcarectl --update
    Unknown Kernel (CentOS 2.6.32-696.20.1.el6.x86_64)
    root [/]# _
    0
  • Marci
    It is not on the list of supported kernels, unless you are very slow in updating the lists
    We get this every time there is a kernel update & kernelcare is 3 or 4 days or even 1 week late in adding it after Cpanel does an auto-update & forces you to reboot
    Unknown Kernel (CentOS 2.6.32-696.20.1.el6.x86_64)
    http://patches.kernelcare.com/
    Shows most recent version as
    kernel-2.6.32-696.18.7.el6(Last Updated: 2018-01-10 13:37:30)
    0
  • Alexandre Parubochyi
    Derek, sorry to misinform you.
    This kernel is not in the list of supported as it has no known security vulnerabilities, and this is why we haven't built a stub for it yet.
    You can safely ignore these warning messages ("Unknown Kernel" ). Or you can add in to your /etc/sysconfig/kcare/kcare.conf the following setting to ignore these messages:
    IGNORE_UNKNOWN_KERNEL=True
    More details here: http://docs.kernelcare.com/index.html?config_options.htm
    Usually, we add KC support for the new kernels within 3-4 days.
    You can always check if KernelCare supports your current kernel here:
    http://patches.kernelcare.com/
    0
  • Alexandre Parubochyi
    I don't want to ignore the messages, I need to know when it will be added, so I can use the symlink protections. I cannot enable them until you add it to kernelcare
    0
  • Alexandre Parubochyi
    This problem can be avoided if you are subscribed to all KC patches (not only symlink protection) as there's no need to update kernel manually (and wait 3-4 days for KC support) in this case.
    0
  • Alexandre Parubochyi
    3.10.0-714.10.2.lve1.5.7.el7.x86_64 Unknown kernel. This was a cPanel kernel update, and I do not see it on the list of supported CL7 kernels. The update was over a week ago.
    0
  • Alexandre Parubochyi
    I have since added, IGNORE_UNKNOWN_KERNEL=True to my kcare.conf file, after reading the below in another thread. I am assuming this is the issue at hand.


    "This kernel is not in the list of supported as it has no known security vulnerabilities, and this is why we haven't built a stub for it yet.
    You can safely ignore these warning messages ("Unknown Kernel" ). Or you can add in to your /etc/sysconfig/kcare/kcare.conf the following setting to ignore these messages:
    IGNORE_UNKNOWN_KERNEL=True
    More details here: http://docs.kernelcare.com/index.html?config_options.htm
    Usually, we add KC support for the new kernels within 3-4 days. "


    This is the first time in over a year of running kcare, that ANY issue has arisen. Great program, from great programmers. Thank you.

    -DeanoX
    0
  • Alexandre Parubochyi
    3.10.0-714.10.2.lve1.5.7.el7.x86_64 is a beta kernel, we do not support beta-kernels with KernelCare. Please, upgrade to the latest supported (3.10.0-714.10.2.lve1.5.9.el7 as of the time of writing this)
    0
  • Alexandre Parubochyi
    Thanks for the info.

    Why does cPanel, or why did, cPanel update CloudLinux, with a beta version? Any idea?

    And as a novice with CloudLinux, how do I easily, revert to the latest supported version of 3.10.0-714.10.2.lve1.5.9.el7 ?


    Thank you,
    -DeanoX
    0
  • Marci
    Ask the cPanel questions at https://forums.cpanel.net/forums/cloudlinux.391/ - I severely doubt CloudLinux can speak to why cPanel made any particular choices or decisions.
    0
  • Alexandre Parubochyi
    Why does cPanel, or why did, cPanel update CloudLinux, with a beta version? Any idea?

    Perhaps your system is set up to be updated from "cloudlinux-updates-testing" repo.
    You might need to contact our support to move it to the stable repo (https://cloudlinux.zendesk.com)
    0
  • Alexandre Parubochyi
    /usr/bin/kcarectl --auto-update --gradual-rollout=auto
    Unknown Kernel (CentOS Linux 3.10.0-862.14.4.el7.x86_64)
    0
  • Alexandre Parubochyi
    It usually takes a few days for new kernels to be added to the list of supported by KernelCare. No additional action is required on user side to make it work when it becomes supported.
    0

Please sign in to leave a comment.