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

    XO From Github : drop connection to host - unknown pool

    Scheduled Pinned Locked Moved Solved Management
    3 Posts 2 Posters 161 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.
    • M Offline
      mestafin
      last edited by Danp

      I have installed the xcp-ng on a HPE DL360 Gen10 server and build the community edition of XO on Ubuntu 22.04 LTS.

      XO is build is

      Xen Orchestra, commit 41a8a.
      

      After logging into the community edition of XO, I tried to connect to the host

      XO finds the host, lists the pool with the same name as the host for about 4 seconds, then the pool name changes to 'unknown pool' for about 2 seconds and then the pool name goes blank.

      It looks like it connects to the host, but then looses the connection.

      When connecting XO to the host, I had to enable the switch for Unauthorized Certificates

      If you go to the Home menu, there is no entry for hosts or pools.

      Just to check, I can ping the host from the the XO vm without issues.

      I have tried to run XO on a vm on the host itself and as a vm on a separate VMware host - same issues.

      To check the host configuration, I installed the free version of XOA and it finds the pool (and added the XOA vm to the pool).
      The versions are:

      xo-server 5.80.0;    xo-web 5.84.0
      

      Going back to the XO version running on the VMware host, the error is still the same - it connects, but then seem to loose the connection.

      A M 2 Replies Last reply Reply Quote 0
      • A Offline
        Andrew Top contributor @mestafin
        last edited by

        @mestafin Don't use Node version 20..... You need to use Node version 18.

        1 Reply Last reply Reply Quote 1
        • M Offline
          mestafin @mestafin
          last edited by

          @mestafin

          Found my problem - I used node V21 instead of node 18

          1 Reply Last reply Reply Quote 0
          • olivierlambertO olivierlambert marked this topic as a question on
          • olivierlambertO olivierlambert has marked this topic as solved on
          • First post
            Last post