Announcement

Collapse
No announcement yet.

free patch type is unavailable for your kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • free patch type is unavailable for your kernel

    Hello

    I am using kernel-3.10.0-1160.2.2.el7, I applied the free patch for this kernel a few days ago but now the following error appears when cron runs for 4 hours.

    The `free` type patch is not found for your kernel. Please select existing patch type

    ***

    The same error appears when I update manually.

    [root@server kcare]# kcarectl --set-patch-type free --update
    free patch type is unavailable for your kernel

    ***

    When I check sysctl, I see that patch is active.

    [root@185-248-57-175 kcare]# sysctl -n fs.enforce_symlinksifowner
    1
    [root@185-248-57-175 kcare]# sysctl -n fs.symlinkown_gid
    99

  • #2
    Hello Micheal,
    Thank you for reaching out! We are really sorry about your experience. This is a single time issue, due to changes in our deployment process. Free, extra, and EDF patches for the latest centos 7 update is available now in the test feed.
    To manually apply them run: kcarectl --update --test
    and will be available in the main feed on Monday.
    Thank you.

    Comment


    • #3
      Hi,

      I am having the same issue, under the latest cpanel, 90.0.17 and latest centos 7 kernel.

      I get alert email with:
      Subject: Cron <root@servername> /usr/bin/kcarectl -q --auto-update
      Body: The `free` type patch is not found for your kernel. Please select existing patch type

      In this cpanel forum post, https://forums.cpanel.net/threads/kc.../#post-2802541, I was directed to this post so I run "kcarectl --update --test" twice:
      1st:
      "
      Patch level 5 applied. Effective kernel version
      Kernel is safe
      "

      2nd:
      "
      Updates already downloaded
      No updates are needed for this kernel
      Kernel is safe
      "

      Then run
      sysctl -n fs.enforce_symlinksifowner
      sysctl -n fs.symlinkown_gid

      The first resulted in 1 and the 2nd with 99 but still the initial error is keep arriving by as an alert email.

      What can I do?

      Comment


      • #4
        Hello Eitan,
        Thank you for reaching out! This problem will be fixed during the day. Stay tuned please.

        Comment


        • #5
          Hello,

          I am having the same issue. I try to run:

          kcarectl --update --test
          Downloading updates
          Requesting trial license for IP x.y.z.a. Please wait...
          HTTP Error 403: Forbidden: https://patches.kernelcare.com/test/...b/3/kpatch.bin

          Can you help me?

          Thank you!

          Comment


          • #6
            Hi Manuel,

            It looks like a temporary network issue - please try again and if no success, submit a ticket at https://cloudlinux.zendesk.com (KernelCare department)

            Comment


            • #7
              Yep, gusy, this issue is back...! can you fix it in a definite way??

              Comment


              • #8
                Hello,

                Please remove the string with PATCH_TYPE=free from your KC config file /etc/sysconfig/kcare/kcare.conf

                Then you can check KernelCare is working with the following commands:
                kcarectl --info
                kcarectl --update

                Comment


                • #9
                  Thanks. I did this with support, so I hope it solved it.

                  I would just recommend to do the info command first as it will first get a trial license, otherwise the update will fail because there is no license of any kind - so first do the info one and then the update and then run the update again to get the message that you are fully updated.

                  Comment


                  • #10
                    Thank you, Eitan!

                    Comment


                    • #11
                      The problem seems to have started again.

                      Comment


                      • #12
                        > The problem seems to have started again.

                        Hello Micheal,
                        Im sorry for the delay with the answer. The patch was updated; you can found them here https://patches03.kernelcare.com/#Al...0-1160.2.2.el7

                        Comment


                        • #13
                          Thank you sergey, problem resolved.

                          Comment

                          Working...
                          X