On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Email notification is sent from KernelCare: /usr/bin/kcarectl --auto-update --gradual-rollout=auto Unknown Kernel

Follow

Comments

6 comments

  • Avatar
    Alan Melnikov

    Hello, this message comes to me too: Cron <root@static> /usr/bin/kcarectl --auto-update --gradual-rollout=auto, Can you tell me what to do?

    0
    Comment actions Permalink
  • Avatar
    Taras Ermoshin

    Hello @Alan Melnikov !

    Is there the text starting with "Unknown Kernel" after "--gradual-rollout=auto" ? If yes, then this article describes your case and you should follow the instructions from the Resolution section.

    Also, this article from CloudLinux (they develop KernelCare) can help you find out if your kernel is supported or not.

    0
    Comment actions Permalink
  • Avatar
    Georg Schreier

    Hello, after I removed the extension, I still get the notification. Does something else have to be considered in addition to the instructions? Thanks in advance.

    0
    Comment actions Permalink
  • Avatar
    Anna Morozyuk

    Hi @Georg Schreier!

    Most probably you have faced a Plesk bug with ID: EXTCERT-200.

    Use the Resolution from the article below:
    https://support.plesk.com/hc/en-us/articles/115002396785-Errors-are-emailed-after-KernelCare-extension-removal-bin-sh-1-usr-bin-kcarectl-not-found
    And feel free to subscribe to the article below to get informed, when it is going to be fixed.

    0
    Comment actions Permalink
  • Avatar
    Georg Schreier

    Hi @Anna Morozyuk,

    thank you, that was the solution.

    Best regards.

    0
    Comment actions Permalink
  • Avatar
    Carlos Oropesa

    Another solution,

    Don't remove the extension, just disable the cronjob (via commands).

    #> nano /etc/cron.d/kcare-cron

    Comments the line and save it.

    #57 */4 * * * root /usr/bin/kcarectl -q --auto-update

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request