XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. erwand
    3. Posts
    E
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 15
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Unable to reconnect XCP server after XOA update

      @Danp a couple of days

      I've make some new tests if it can help:

      When i try to start orchestra using this commande in rc.local of my ubuntu 20.04.6

       cd /usr/src/xen-orchestra/packages/xo-server && forever start dist/cli.mjs
      

      it's not working, i can connect to the web interface bu unable to connect to XCP

      but if i lauch the same command on the CLI just after the start, it works

      posted in Xen Orchestra
      E
      erwand
    • RE: Unable to reconnect XCP server after XOA update

      In fact, the problem seems to come from the way I launch the orchestra server.

      If I run it manually with the "Yarn star" command, everything works fine.

      However, if I use the "Forever-service" method in this case, the XCP servers connect then disconnect before displaying an authentication error message.

      I've tried running xoa-server as root and also sudo with another user and the problem is identical.

      But if i just user "forever start dist/cli.mjs" as root it works

      Does anyone have any ideas?

      posted in Xen Orchestra
      E
      erwand
    • RE: Unable to reconnect XCP server after XOA update

      @Andrew Same things happen wit node 18.17.1

      posted in Xen Orchestra
      E
      erwand
    • RE: Unable to reconnect XCP server after XOA update

      @Andrew node version is v20.5.1

      posted in Xen Orchestra
      E
      erwand
    • RE: Unable to reconnect XCP server after XOA update

      @Danp Thnks for the replys

      It's a Pool master and pointing on the good IP address.

      I've check and no conflict

      posted in Xen Orchestra
      E
      erwand
    • RE: Unable to reconnect XCP server after XOA update

      @erwand

      I'dont know if it's related but on the XCP server i've got this error message when i try to connect

      Aug 16 16:47:30 xcp-ng8 xapi: [debug||5054 HTTPS aaa.bbb.cc.zzz->:::80|session.login_with_password D:4854db6a1911|xapi_session] Success: local auth, user root from HTTP request from Internet with User-Agent: unknown
      Aug 16 16:47:30 xcp-ng8 xapi: [ info||5054 HTTPS aaa.bbb.cc.zzz->:::80|session.login_with_password D:4854db6a1911|xapi_session] Session.create trackid=142f95adb60374a681fd4b96d756e616 pool=false uname=root originator= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49
      Aug 16 16:47:30 xcp-ng8 xapi: [debug||5055 /var/lib/xcp/xapi||dummytaskhelper] task dispatch:pool.get_all D:5763c1938d1e created by task D:4854db6a1911
      Aug 16 16:47:30 xcp-ng8 xapi: [debug||5056 :::80||api_effect] pool.add_to_other_config
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 HTTPS aaa.bbb.cc.zzz->:::80|pool.add_to_other_config D:9e2b8e1bc66f|sql] Duplicate key in set or map: table pool; field other_config; ref OpaqueRef:ccd0e30e-c0e1-4428-be2d-1d0e4534546c; key xo:clientInfo:yt8uh0ytrxj
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] pool.add_to_other_config D:9e2b8e1bc66f failed with exception Db_exn.Duplicate_key("pool", "other_config", "OpaqueRef:ccd0e30e-c0e1-4428-be2d-1d0e4534546c", "xo:clientInfo:yt8uh0ytrxj")
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] Raised Db_exn.Duplicate_key("pool", "other_config", "OpaqueRef:ccd0e30e-c0e1-4428-be2d-1d0e4534546c", "xo:clientInfo:yt8uh0ytrxj")
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 1/8 xapi Raised at file ocaml/database/db_cache_impl.ml, line 316
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 2/8 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 3/8 xapi Called from file ocaml/xapi/rbac.ml, line 205
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 4/8 xapi Called from file ocaml/xapi/server_helpers.ml, line 92
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 5/8 xapi Called from file ocaml/xapi/server_helpers.ml, line 113
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 6/8 xapi Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 7/8 xapi Called from file map.ml, line 135
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace] 8/8 xapi Called from file src/sexp_conv.ml, line 156
      Aug 16 16:47:30 xcp-ng8 xapi: [error||5056 :::80||backtrace]
      Aug 16 16:47:30 xcp-ng8 xapi: [debug||5056 :::80||api_effect] pool.remove_from_other_config
      Aug 16 16:47:30 xcp-ng8 xapi: [debug||5056 :::80||api_effect] pool.add_to_other_config
      
      
      posted in Xen Orchestra
      E
      erwand
    • Unable to reconnect XCP server after XOA update

      Hi all ,

      I've got an old version of XOA and update to the latest master branch using Git. Before everything work fine.

      Bu now i'm unable to reconnect my server in log i've got this message

      watchEvents Error: HTTP connection has timed out
      août 16 11:23:27 xoa xo-server[5237]:     at ClientRequest.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202308161116/node_modules/http-request-plus/index.js:61:25)
      août 16 11:23:27 xoa xo-server[5237]:     at ClientRequest.emit (node:events:514:28)
      août 16 11:23:27 xoa xo-server[5237]:     at ClientRequest.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202308161116/@xen-orchestra/log/configure.js:52:17)
      août 16 11:23:27 xoa xo-server[5237]:     at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
      août 16 11:23:27 xoa xo-server[5237]:     at Object.onceWrapper (node:events:628:28)
      août 16 11:23:27 xoa xo-server[5237]:     at TLSSocket.emit (node:events:526:35)
      août 16 11:23:27 xoa xo-server[5237]:     at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202308161116/@xen-orchestra/log/configure.js:52:17)
      août 16 11:23:27 xoa xo-server[5237]:     at TLSSocket.Socket._onTimeout (node:net:589:8)
      août 16 11:23:27 xoa xo-server[5237]:     at listOnTimeout (node:internal/timers:573:17)
      août 16 11:23:27 xoa xo-server[5237]:     at processTimers (node:internal/timers:514:7) {
      août 16 11:23:27 xoa xo-server[5237]:   url: 'https://195.xxx.yy.zz/jsonrpc',
      août 16 11:23:27 xoa xo-server[5237]:   originalUrl: 'https://195.xxx.yy.zz/jsonrpc',
      août 16 11:23:27 xoa xo-server[5237]:   call: {
      août 16 11:23:27 xoa xo-server[5237]:     method: 'event.from',
      août 16 11:23:27 xoa xo-server[5237]:     params: [ [Array], '00000000000002030971,00000000000001764125', 60.1 ]
      août 16 11:23:27 xoa xo-server[5237]:   }
      
      

      I've try opening the adress in a browser the adresse 'https://195.xxx.yy.zz/jsonrpc', and i've got 404

      I've check the network between XOA and XCP server and no restriction, no firewal, ...

      Have you got an idea ?

      FYI; XCP version (8.2 LTS)

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @julien-f said in Backup failed with message "HTTP request has been canceled":

      node -p 'require.resolve("xen-api")'

      Hi all,

      I think the problem is fixed now. thanks for your help

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @olivierlambert said in Backup failed with message "HTTP request has been canceled":

      git rev-parse HEAD

      51f013851d6d72275a16d37cd92b0ff88e7046d8

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @olivierlambert I think: xen-orchestra-202106151431

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @olivierlambert
      I've double check and i'm on the laster master check out on 15/06/2021 and everything rebuild

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @olivierlambert Im using XO installed using the script provide by
      f3fa7d75-1328-4d23-95c5-ad121eb69f19-image.png

      40e5fbbf-1320-4839-a547-faa3e727e8ad-image.png

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @olivierlambert I've update to latest XOA and same thing happen today ? Anything i can check to solve ?

      posted in Xen Orchestra
      E
      erwand
    • RE: Backup failed with message "HTTP request has been canceled"

      @julien-f

      thanks for your reply, where i can find the parameter "callconcurrency" you talk about in your post ?

      posted in Xen Orchestra
      E
      erwand
    • Backup failed with message "HTTP request has been canceled"

      Hi all, i've got several backup failed with this kind of message, when i try to launch the backup manually it work but with many VM in the backup it failed for some (9) and work for most (83)

      any idea ?

      thanks

      31aa98ce-aba6-4c57-98d0-4fd463261d1e-image.png

      {
            "data": {
              "type": "VM",
              "id": "9c0d7ef5-0bd2-dbd0-ea08-4d27d2a49a8f"
            },
            "id": "1623714947448",
            "message": "backup VM",
            "start": 1623714947448,
            "status": "failure",
            "tasks": [
              {
                "id": "1623714947719",
                "message": "snapshot",
                "start": 1623714947719,
                "status": "success",
                "end": 1623715166291,
                "result": "b0248f70-64d4-3ac6-d2a8-5ae92bc334b5"
              },
              {
                "data": {
                  "id": "4433dda6-d07a-42ae-9732-f40156bf71e7",
                  "isFull": false,
                  "type": "remote"
                },
                "id": "1623715166292",
                "message": "export",
                "start": 1623715166292,
                "status": "failure",
                "tasks": [
                  {
                    "id": "1623715166378",
                    "message": "transfer",
                    "start": 1623715166378,
                    "status": "failure",
                    "end": 1623715466379,
                    "result": {
                      "canceled": true,
                      "method": "GET",
                      "url": "https://10.89.*.*/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3A3b3fc0fe-9599-4eb0-8dee-88c6f41ed5b2&base=OpaqueRef%3A04eb8c1a-97f7-4737-986d-45d615e55a8e&session_id=OpaqueRef%3Abbfab2de-0aa5-42f8-816e-541675874a9c&task_id=OpaqueRef%3A772c8265-4b67-4daf-ab11-c43e39d8653e",
                      "message": "HTTP request has been canceled",
                      "name": "Error",
                      "stack": "Error: HTTP request has been canceled\n    at IncomingMessage.emitAbortedError (/opt/xo/xo-builds/xen-orchestra-202106101449/node_modules/http-request-plus/index.js:75:19)\n    at Object.onceWrapper (events.js:482:28)\n    at IncomingMessage.emit (events.js:376:20)\n    at IncomingMessage.patchedEmit (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/log/configure.js:93:17)\n    at IncomingMessage.emit (domain.js:470:12)\n    at TLSSocket.socketCloseListener (_http_client.js:432:11)\n    at TLSSocket.emit (events.js:388:22)\n    at TLSSocket.patchedEmit (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/log/configure.js:93:17)\n    at TLSSocket.emit (domain.js:470:12)\n    at net.js:673:12"
                    }
                  }
                ],
                "end": 1623715466379,
                "result": {
                  "canceled": true,
                  "method": "GET",
                  "url": "https://10.89.*.*/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3A3b3fc0fe-9599-4eb0-8dee-88c6f41ed5b2&base=OpaqueRef%3A04eb8c1a-97f7-4737-986d-45d615e55a8e&session_id=OpaqueRef%3Abbfab2de-0aa5-42f8-816e-541675874a9c&task_id=OpaqueRef%3A772c8265-4b67-4daf-ab11-c43e39d8653e",
                  "message": "HTTP request has been canceled",
                  "name": "Error",
                  "stack": "Error: HTTP request has been canceled\n    at IncomingMessage.emitAbortedError (/opt/xo/xo-builds/xen-orchestra-202106101449/node_modules/http-request-plus/index.js:75:19)\n    at Object.onceWrapper (events.js:482:28)\n    at IncomingMessage.emit (events.js:376:20)\n    at IncomingMessage.patchedEmit (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/log/configure.js:93:17)\n    at IncomingMessage.emit (domain.js:470:12)\n    at TLSSocket.socketCloseListener (_http_client.js:432:11)\n    at TLSSocket.emit (events.js:388:22)\n    at TLSSocket.patchedEmit (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/log/configure.js:93:17)\n    at TLSSocket.emit (domain.js:470:12)\n    at net.js:673:12"
                }
              }
            ],
            "end": 1623715866307,
            "result": {
              "message": "all targets have failed, step: writer.transfer()",
              "name": "Error",
              "stack": "Error: all targets have failed, step: writer.transfer()\n    at VmBackup._callWriters (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/backups/_VmBackup.js:118:13)\n    at async VmBackup._copyDelta (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/backups/_VmBackup.js:190:5)\n    at async VmBackup.run (/opt/xo/xo-builds/xen-orchestra-202106101449/@xen-orchestra/backups/_VmBackup.js:371:9)"
            }
          }
      
      posted in Xen Orchestra
      E
      erwand