XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XOA Updater Down?

    Scheduled Pinned Locked Moved Solved Management
    6 Posts 5 Posters 173 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      joneill
      last edited by

      Is anyone else having issues getting the xoa-updater command to run?

      I keep getting various errors like:

      ✖ { message: 'HTTP connection has timed out' }
      ✖ { message: 'Unexpected end of JSON input' }
      ✖ { message: '' }

      Sometimes it will work but then loses connection when the command is running.
      I have also confirmed that it is not a DNS issue.

      Thanks.

      D TheNorthernLightT 2 Replies Last reply Reply Quote 0
      • D Offline
        DustinB @joneill
        last edited by

        @joneill I'm seeing this

        c9f78456-ddf8-480f-91aa-1abfd439e4e2-image.png

        1 Reply Last reply Reply Quote 0
        • TheNorthernLightT Offline
          TheNorthernLight @joneill
          last edited by

          @joneill I've been having periodic access issues as well for the past week. It seem xen-orchestry.com is acting with really slow response times (almost like a ddos attack, or something like that).

          1 Reply Last reply Reply Quote 0
          • M Offline
            marekm
            last edited by

            Same here, getting timeouts when trying to update but "ping xen-orchestra.com" seems normal (about 40 ms from here), so more like crashing server processes (out of memory?) than a DDoS (which usually saturates links resulting in high latency and packet loss).

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Hello,

              We had an issue with the growing number of XOAs running all around the world. It was a legacy code (7 years old) that was untouched, and the number of calls started to be faster than we could process. We identified the specific call causing the issue, and implemented a neat cache solution in our code.

              I let you watch the before/after on the CPU load in that VM hosting this code:

              image (4).png

              Anyway, now the updater service should work perfectly 🙂

              M 1 Reply Last reply Reply Quote 1
              • olivierlambertO olivierlambert marked this topic as a question on
              • olivierlambertO olivierlambert has marked this topic as solved on
              • M Offline
                marekm @olivierlambert
                last edited by

                @olivierlambert Thanks for the quick fix - update worked fine when I tried again, right after I wrote my post 🙂

                1 Reply Last reply Reply Quote 1
                • First post
                  Last post