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

    XO SocketError: other side closed

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    12 Posts 2 Posters 251 Views 2 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.
    • B Offline
      bogikornel @olivierlambert
      last edited by

      @olivierlambert

      None. The XCP-ng host also runs XO. Same VLAN, same IP range (XCP-ng 172.31.30.3, XO: 172.31.30.4). So the packet doesn't even need to go out to a switch.

      The XO has an old Xenserver 7.0 (I'm migrating from it), it runs stable, its IP is 172.31.30.5.

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

        Do you have the problem with a regular XOA (vs XO source), because I'd like to rule out an environment problem

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bogikornel @olivierlambert
          last edited by

          @olivierlambert
          I will check with XOA. For now, it seems to me to be a local problem, because I use quite a few XOs and I haven't had this problem yet. If I find something I will report it.

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

            Check on the side of the Node version maybe

            B 1 Reply Last reply Reply Quote 0
            • B Offline
              bogikornel @olivierlambert
              last edited by

              @olivierlambert

              root@xoa:~# node -v
              v22.16.0
              
              
              1 Reply Last reply Reply Quote 0
              • olivierlambertO Online
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Thanks, to rule out a Node issue, can you try with Node 20?

                B 1 Reply Last reply Reply Quote 0
                • B Offline
                  bogikornel @olivierlambert
                  last edited by

                  @olivierlambert

                  downgraded to version 20.19.2 . Unfortunately no change.

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

                    Okay let's see if you have the same problem with an XOA in latest then…

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      bogikornel @olivierlambert
                      last edited by

                      @olivierlambert I updated the XO from source, it looks good for now.

                      1 Reply Last reply Reply Quote 1
                      • olivierlambertO olivierlambert marked this topic as a question
                      • olivierlambertO olivierlambert has marked this topic as solved
                      • olivierlambertO Online
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Excellent news! Thanks for keeping us posted 🙂

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