KernelCare down?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • m.rahnev
    Member
    Forum Explorer
    • Mar 2021
    • 42

    #1

    KernelCare down?

    All of my machines are getting this error..

    [root@windburn home]# /usr/bin/kcarectl --patch-info
    [Errno 111] Connection refused

    [root@fury home]# /usr/bin/kcarectl --patch-info
    [Errno 111] Connection refused
  • kobiidykhata
    Member
    • Apr 2017
    • 94

    #2
    Sorry for the lack of timely response. Indeed, it was a temporary problem with our patch-server availability.

    Comment

    • admin
      Member
      • Mar 2018
      • 52

      #3
      Im getting this again today. Are things down?

      Comment

      • admin
        Member
        • Mar 2018
        • 52

        #4
        We are seeing this across all servers as well:

        root@ollie [~]# /usr/bin/kcarectl --auto-update
        [Errno 113] No route to host

        [root@server ~]# /usr/bin/kcarectl --auto-update
        <urlopen error [Errno 113] No route to host>

        Comment

        • admin
          Member
          • Mar 2018
          • 52

          #5
          Im getting similar - [Errno 113] No route to host
          for the last few hours.

          Comment

          • admin
            Member
            • Mar 2018
            • 52

            #6
            connect(4, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("69.175.3.11")}, 16) = -1 EHOSTUNREACH (No route to host)

            Comment

            • admin
              Member
              • Mar 2018
              • 52

              #7
              Ditto...

              [Errno 113] No route to host

              Comment

              • admin
                Member
                • Mar 2018
                • 52

                #8
                Seeing this across all our servers for 3-4 hours now as well:

                ~]# kcarectl -u
                [Errno 111] Connection refused

                Guessing something is going on?

                Comment

                • admin
                  Member
                  • Mar 2018
                  • 52

                  #9
                  Same here; Germany. Quite a quick trial outcome

                  Comment

                  • iseletsk
                    Senior Member
                    • Dec 2017
                    • 1199

                    #10
                    Sorry, everyone. Everything should be back up now. A human error resulted in patches being wiped out on both production server and failover server.
                    We re-deployed all the patches -- so things should be back to normal.

                    I am sorry for both -- the incident and the poor communication on our part. The communication part is where I will focus the most next, as we had planned way to solve this particular issue with servers -- and it worked well.

                    Comment

                    • iseletsk
                      Senior Member
                      • Dec 2017
                      • 1199

                      #11
                      Still with problems here(proxmox server):

                      root@nx4:~# /usr/bin/kcarectl --auto-update
                      <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
                      root@nx4:~# /usr/bin/kcarectl --auto-update --no-check-cert
                      <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
                      root@nx4:~# /usr/bin/kcarectl --no-check-cert --auto-update
                      <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
                      root@nx4:~# /usr/bin/kcarectl --no-check-cert --auto-update --kpatch-debug
                      <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
                      root@nx4:~# /usr/bin/kcarectl --plugin-info
                      <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)>
                      root@nx4:~#

                      root@nx4:~# uname -a
                      Linux nx4 4.4.62-1-pve #1 SMP PVE 4.4.62-88 (Thu, 18 May 2017 09:18:43 +0200) x86_64 GNU/Linux
                      root@nx4:~#

                      Comment

                      • iseletsk
                        Senior Member
                        • Dec 2017
                        • 1199

                        #12
                        @robertp

                        You (probably) need to install pyOpenSSL (available in base repos on CentOS6 and CentOS7, I dont know about anything else). It enables SNI for kernelcare according to the warning when you update to the latest version of kernelcare rpm.

                        Paul.

                        Comment

                        • iseletsk
                          Senior Member
                          • Dec 2017
                          • 1199

                          #13
                          Currently I am getting connection time outs:

                          [root@dev-el7 ~]# kcarectl -i
                          [Errno 110] Connection timed out

                          De/Registering works howerver

                          Comment

                          Working...
                          X