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

    XOA Source Error: socket hang up

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    3 Posts 2 Posters 1.1k 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.
    • H Offline
      Hightmar
      last edited by Hightmar

      Hello,

      I installed XCP-NG with XOA on a virtual machine to discover before installing it on a physical server (coming soon). Everything works fine, I was able to create a network, put pfSense in router etc, no issues.

      I tried to install XOA from source on a Debian 11 machine, following the steps given by the documentation.

      I can access the interface but problems occur when I connect my pool.

      The pool is always disconnected with Error: socket hang up.

      Voici ce qui se passe quand je lance yarn start

      root@debian:~/xen-orchestra/packages/xo-server# yarn start
      yarn run v1.22.19
      $ node dist/cli.mjs
      2023-01-11T19:33:02.656Z xo:main INFO Configuration loaded.
      2023-01-11T19:33:02.660Z xo:main INFO Web server listening on http://[::]:80
      2023-01-11T19:33:03.116Z xo:mixins:hooks WARN start failure {
        error: Error: spawn xenstore-read ENOENT
            at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
            at onErrorNT (node:internal/child_process:483:16)
            at processTicksAndRejections (node:internal/process/task_queues:82:21) {
          errno: -2,
          code: 'ENOENT',
          syscall: 'spawn xenstore-read',
          path: 'xenstore-read',
          spawnargs: [ 'vm' ],
          cmd: 'xenstore-read vm'
        }
      }
      2023-01-11T19:33:03.122Z xo:mixins:hooks WARN start failure {
        error: Error: spawn losetup ENOENT
            at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
            at onErrorNT (node:internal/child_process:483:16)
            at processTicksAndRejections (node:internal/process/task_queues:82:21) {
          errno: -2,
          code: 'ENOENT',
          syscall: 'spawn losetup',
          path: 'losetup',
          spawnargs: [ '-D' ],
          originalMessage: 'spawn losetup ENOENT',
          shortMessage: 'Command failed with ENOENT: losetup -D\nspawn losetup ENOENT',
          command: 'losetup -D',
          escapedCommand: 'losetup -D',
          exitCode: undefined,
          signal: undefined,
          signalDescription: undefined,
          stdout: '',
          stderr: '',
          failed: true,
          timedOut: false,
          isCanceled: false,
          killed: false
        }
      }
      2023-01-11T19:33:03.272Z xo:main INFO Setting up / → /root/xen-orchestra/packages/xo-web/dist
      2023-01-11T19:33:54.173Z xo:main INFO + Console proxy (admin@admin.net - ::ffff:192.168.50.1)
      2023-01-11T19:33:55.727Z xo:main INFO - Console proxy (admin@admin.net - ::ffff:192.168.50.1)
      2023-01-11T19:34:02.723Z xo:main INFO + Console proxy (admin@admin.net - ::ffff:192.168.50.1)
      2023-01-11T19:34:03.908Z xo:main INFO - Console proxy (admin@admin.net - ::ffff:192.168.50.1)
      _watchEvents Error: socket hang up
          at connResetException (node:internal/errors:718:14)
          at TLSSocket.socketCloseListener (node:_http_client:463:25)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.patchedEmit [as emit] (/root/xen-orchestra/@xen-orchestra/log/configure.js:135:17)
          at node:net:305:12
          at TCP.done (node:_tls_wrap:588:7)
          at TCP.callbackTrampoline (node:internal/async_hooks:130:17) {
        code: 'ECONNRESET',
        url: 'https://192.168.50.129/jsonrpc',
        call: {
          method: 'event.from',
          params: [ [Array], '00000000000000106186,00000000000000104805', 60.1 ]
        }
      }
      

      We can see that the call is made on https.

      I redid an installation, but this time using XenOrchestraInstallerUpdater installing a certificate and I encounter the same problem.

      Hardware config :

      XOA Source

      • Debian 11 (fresh minimal installation)
      • 1 CPU
      • Disk 10go
      • RAM 2go
      • NodeJS 19 from nodesource

      XCP-NG

      • XCP-NG 8.2.1
      • 4 CPU
      • Disk 2x90go
      • RAM 16go

      Did he encounter the same problem, or would he have an idea to solve it?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • H Offline
        Hightmar @olivierlambert
        last edited by

        @olivierlambert "Please always use latest Node LTS."... Ok my bad. I didn't check which version is the LTS version.
        Indeed, it works much better.
        Thank you!

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

          Hi,

          Please re-read the doc carefully, especially on the Node version.

          H 1 Reply Last reply Reply Quote 1
          • H Offline
            Hightmar @olivierlambert
            last edited by

            @olivierlambert "Please always use latest Node LTS."... Ok my bad. I didn't check which version is the LTS version.
            Indeed, it works much better.
            Thank you!

            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

            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