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

    ECONNRESET when new host added

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 3 Posters 1.4k Views 3 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.
    • olivier-monacoO Offline
      olivier-monaco
      last edited by olivierlambert

      Hi,

      I've installed XO from source on Debian 11. Added a remote host without issue. Now I try to add local host (XO VM is running on it) and had a ECONNRESET error. VM appears for a few seconds in XO before error.

      In XO logs I can see many times:

      _watchEvents Error: socket hang up
          at connResetException (node:internal/errors:711:14)
          at TLSSocket.socketCloseListener (node:_http_client:461:25)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:135:17)
          at node:net:298:12
          at TCP.done (node:_tls_wrap:587:7)
          at TCP.callbackTrampoline (node:internal/async_hooks:132:17) {
        code: 'ECONNRESET',
        url: 'https://10.42.0.250/jsonrpc',
        call: {
          method: 'event.from',
          params: [ [Array], '00000000000001258275,00000000000001258250', 60.1 ]
        }
      }
      

      I've found nothing in XCP-ng logs. XCP-ng Center 20.04.01 works. I've not rebooted host so far and will plan it if needed.

      Maybe it comes from my SR: I have a SR which is a local folder containing symlink to 4 hard disks. They are used to have direct access to these disks from one VM (something like https://www.zerodispersion.com/xenserver-whole-disk-passthrough/).

      Host : XCP-ng 8.2
      XO : xo-server : 5.106.1 and xo-web 5.107.0

      Does anyone has an idea?

      Regards,

      Olivier

      L 1 Reply Last reply Reply Quote 0
      • L Offline
        lukask @olivier-monaco
        last edited by

        Hi @olivier-monaco

        Have you tried during add host server tick Unauthorized Certificates? It must be ticked.

        0d8f418c-b779-4bab-88e6-bbdee635988b-Snímek obrazovky pořízený 2022-11-18 10-54-25.png

        olivier-monacoO 1 Reply Last reply Reply Quote 0
        • olivier-monacoO Offline
          olivier-monaco @lukask
          last edited by

          @lukask Yes.

          c54dc55e-8d62-4793-981f-ffb648254f2c-image.png

          L 1 Reply Last reply Reply Quote 0
          • L Offline
            lukask @olivier-monaco
            last edited by

            @olivier-monaco

            maybe try other version of nodejs, which version of nodejs you have? I have v16.17.0

            olivier-monacoO 1 Reply Last reply Reply Quote 0
            • olivier-monacoO Offline
              olivier-monaco @lukask
              last edited by

              Thanks @lukask, it was the nodejs version. I had version 19.1.0. Switching to 18.12.1 solved this issue.

              L 1 Reply Last reply Reply Quote 1
              • L Offline
                lukask @olivier-monaco
                last edited by

                @olivier-monaco Perfect

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

                  That's why we put that in bold in our documentation:
                  Please always use latest Node LTS.

                  😆

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