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

    Error When adding host to XO

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    5 Posts 2 Posters 1.5k Views 1 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.
    • F Offline
      fred974
      last edited by

      Hi,

      I keep seeing error messages in XO in ther server section like
      socket hang up
      this pool is already connected

      In order to try to rectify the issue, I remove the host from the pool and deleted from XO.
      When I added the host again, I now get this error connect EHOSTUNREACH 172.16.10.xxx:443

      Could anyone please advise why I get these error and how to fix them?

      Thank you

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

        You just need to add the pool master, and the pool master ONLY. Don't connect to other hosts of the pool.

        F 1 Reply Last reply Reply Quote 0
        • F Offline
          fred974 @olivierlambert
          last edited by

          @olivierlambert said in Error When adding host to XO:

          You just need to add the pool master, and the pool master ONLY. Don't connect to other hosts of the pool.

          Sorry, I am not following.
          Do I remove all the host from the pool and set 1 host to be master? How will the system know what host belong to the pool?

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

            The error message you got in XO was telling you that you tried to add a pool that was already added in XO earlier, via the host connection.

            As a "client" to a pool, XO (or XCP-ng Center) will connect only to one host member of the pool. If you connect to a slave, it won't fail and XO will redirect the connection to the master (because API will tell the master's IP address).

            Also, there's always a master in a pool, and there's always a pool (a "lone" host is in fact in its own pool).

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              fred974 @olivierlambert
              last edited by

              @olivierlambert Thank you.
              All back to normal now

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