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

    Unable to add a Host to Xen Orchestra - no errors

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 3 Posters 1.6k 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.
    • X Offline
      Xelosu
      last edited by

      Hello,

      I've recently installed Xen Orchestra from source following the official guide (running version is Xen Orchestra, commit 6056a) and I am having weird problem that I cannot add a Host to management panel, it seems to connect for a few seconds then disappears without any error from everywhere outside of the settings tab.

      When I toggle the "Enable" button I can see for a second it reads the information about the pool.
      9c439849-0bd5-4bde-90bd-50a4055a6322-image.png

      I can then go to Host menu and VM menu end everything is fine for a few seconds.
      cbdcffcf-8eb2-40dc-98f3-f24a74ca99b1-image.png

      And then without any errors, the pool information is gone.
      7021eb0c-06a0-43ff-941f-293ff5ccc213-image.png

      And the Host menu looks like no servers were added
      1d323447-3711-46f7-be8b-5e3a02f02a84-image.png

      All I remember to be out of the ordinary that might have possibly trigger this behavior is that initially I put the XOA admin username in the "Username" for host connection and got a bunch of connection errors as a result. I have since then change it to the proper username, I have tried to delete this entry re-add it with new name but the issue persist.
      I also have another instance of XOA running older version and I can confirm the Host can be read by the other XOA instance without any issues.
      The host is running XCP-ng 8.2.1.

      Like I mention in the title, the XOA itself is not displaying any errors and I am not sure where to look for the relevant logs in the backend.

      Any tips would be appreciated.

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DustinB @Xelosu
        last edited by

        @Xelosu What is the pool master for KP22?

        Is it the same IP as 172.17.0.5? If not add the pool master instead and see if the connection works.

        X 1 Reply Last reply Reply Quote 0
        • X Offline
          Xelosu @DustinB
          last edited by

          @DustinB Hi,
          172.17.0.5 is the pool master - this is a single pool, single machine setup.
          The XOA VM is running on that host, I can also ssh into the 172.17.0.5 host from the VM running XOA just fine so I think this is not a networking problem.

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            DustinB @Xelosu
            last edited by

            @Xelosu I'm confused then... it appears like its connected from the initial screenshot..

            X 1 Reply Last reply Reply Quote 0
            • X Offline
              Xelosu @DustinB
              last edited by

              I've restarted the entire VM running XOA and the problem still persist, however I can now see some tasks
              43d82741-ea99-4562-b3ac-aef39d14bde6-image.png

              Raw log of the failed task is (The username, has current XOA admin account name in it)
              a7774e59-585a-40fb-95d9-e012b4d9e85d-image.png

              Raw log of the task in "started" status is "Not Found"

              X 1 Reply Last reply Reply Quote 0
              • X Offline
                Xelosu @Xelosu
                last edited by

                I've updated the local git clone and rebuild the XOA, now I a on commit c10e3, the issue persist.

                I dug around the logs inside the XOA VM and found this issue in /var/log/orchestra.log

                2024-03-11T18:37:20.691Z xo:plugin INFO register transport-email
2024-03-11T18:37:20.693Z xo:plugin INFO register transport-icinga2
2024-03-11T18:37:20.699Z xo:plugin INFO register transport-nagios
2024-03-11T18:37:20.701Z xo:plugin INFO register transport-slack
2024-03-11T18:37:20.702Z xo:plugin INFO register transport-xmpp
2024-03-11T18:37:20.703Z xo:plugin INFO register usage-report
2024-03-11T18:37:20.712Z xo:plugin INFO register web-hooks
2024-03-11T18:37:20.714Z xo:plugin INFO failed register test
2024-03-11T18:37:20.714Z xo:plugin INFO Cannot find module '/srv/xen-orchestra/packages/xo-server-test/dist'. Please verify that the package.json has a valid "main" entry {
  error: Error: Cannot find module '/srv/xen-orchestra/packages/xo-server-test/dist'. Please verify that the package.json has a valid "main" entry
      at tryPackage (node:internal/modules/cjs/loader:444:19)
      at Function.Module._findPath (node:internal/modules/cjs/loader:715:18)
      at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
      at requireResolve (node:internal/modules/helpers:187:19)
      at Xo.call (file:///srv/xen-orchestra/packages/xo-server/src/index.mjs:346:32)
      at Xo.call (file:///srv/xen-orchestra/packages/xo-server/src/index.mjs:398:25)
      at from (file:///srv/xen-orchestra/packages/xo-server/src/index.mjs:434:95)
      at Function.from (<anonymous>)
      at registerPlugins (file:///srv/xen-orchestra/packages/xo-server/src/index.mjs:434:27)
      at main (file:///srv/xen-orchestra/packages/xo-server/src/index.mjs:903:5) {
    code: 'MODULE_NOT_FOUND',
    path: '/srv/xen-orchestra/packages/xo-server-test/package.json',
    requestPath: '/srv/xen-orchestra/packages/xo-server-test'
  }
}
strict mode: required property "discoveryURL" is not defined at "#/anyOf/0" (strictRequired)
strict mode: missing type "object" for keyword "required" at "#/anyOf/1/properties/advanced" (strictTypes)
strict mode: required property "authorizationURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
strict mode: required property "issuer" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
strict mode: required property "userInfoURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
strict mode: required property "tokenURL" is not defined at "#/anyOf/1/properties/advanced" (strictRequired)
2024-03-11T18:37:22.421Z xo:plugin INFO successfully register auth-github
2024-03-11T18:37:22.422Z xo:plugin INFO successfully register auth-google
2024-03-11T18:37:22.422Z xo:plugin INFO successfully register auth-ldap
2024-03-11T18:37:22.422Z xo:plugin INFO successfully register auth-oidc
2024-03-11T18:37:22.422Z xo:plugin INFO successfully register auth-saml
2024-03-11T18:37:22.422Z xo:plugin INFO successfully register netbox
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register test-plugin
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register transport-email
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register transport-icinga2
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register transport-nagios
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register transport-slack
2024-03-11T18:37:22.423Z xo:plugin INFO successfully register transport-xmpp
2024-03-11T18:37:22.424Z xo:plugin INFO successfully register usage-report
2024-03-11T18:37:22.424Z xo:plugin INFO successfully register web-hooks
2024-03-11T18:37:22.424Z xo:plugin INFO successfully register backup-reports
2024-03-11T18:37:22.445Z xo:plugin INFO successfully register audit
2024-03-11T18:37:22.445Z xo:plugin INFO successfully register load-balancer
2024-03-11T18:37:22.445Z xo:plugin INFO successfully register perf-alert
2024-03-11T18:37:22.570Z xo:plugin INFO successfully register sdn-controller
_watchEvents Error: HTTP connection has timed out
    at ClientRequest.<anonymous> (/srv/xen-orchestra/node_modules/http-request-plus/index.js:61:25)
    at ClientRequest.emit (node:events:518:28)
    at ClientRequest.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
    at Object.onceWrapper (node:events:632:28)
    at TLSSocket.emit (node:events:530:35)
    at TLSSocket.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.Socket._onTimeout (node:net:589:8)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7) {
  url: 'https://172.17.0.5/jsonrpc',
  originalUrl: 'https://172.17.0.5/jsonrpc',
  call: {
    method: 'event.from',
    params: [ [Array], '00000000000000290240,00000000000000037270', 60.1 ]
  }
}
_watchEvents Error: HTTP connection has timed out
    at ClientRequest.<anonymous> (/srv/xen-orchestra/node_modules/http-request-plus/index.js:61:25)
    at ClientRequest.emit (node:events:518:28)
    at ClientRequest.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
    at Object.onceWrapper (node:events:632:28)
    at TLSSocket.emit (node:events:530:35)
    at TLSSocket.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.Socket._onTimeout (node:net:589:8)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7) {
  url: 'https://172.17.0.5/jsonrpc',
  originalUrl: 'https://172.17.0.5/jsonrpc',
  call: {
    method: 'event.from',
    params: [ [Array], '00000000000000290394,00000000000000037270', 60.1 ]
  }
}
_watchEvents Error: HTTP connection has timed out
    at ClientRequest.<anonymous> (/srv/xen-orchestra/node_modules/http-request-plus/index.js:61:25)
    at ClientRequest.emit (node:events:518:28)
    at ClientRequest.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
    at Object.onceWrapper (node:events:632:28)
    at TLSSocket.emit (node:events:530:35)
    at TLSSocket.patchedEmit [as emit] (/srv/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.Socket._onTimeout (node:net:589:8)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7) {
  url: 'https://172.17.0.5/jsonrpc',
  originalUrl: 'https://172.17.0.5/jsonrpc',
  call: {
    method: 'event.from',
    params: [ [Array], '00000000000000290394,00000000000000037270', 60.1 ]
  }
}
                DanpD 1 Reply Last reply Reply Quote 0
                • DanpD Offline
                  Danp Pro Support Team @Xelosu
                  last edited by

                  @Xelosu FWIW, the log entries related to xo-server-test are benign and should be ignored.

                  1 Reply Last reply Reply Quote 0

                  Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                  Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                  With your input, this post could be even better 💗

                  Register Login
                  • First post
                    Last post