You need a space between the URL and the user name.

@hvilches said in XCP-ng Center 20.03.00 released:

is-a-template ( RW): true

Looks like this is the culprit...

@flipsidecreations There's a new Netdata plugin, which appears to only be available in XOA Premium edition. It doesn't appear that you will be able to enable the new Advanced Live Telemetry using the versions you are currently running.

@olivierlambert The "quick deploy" via web worked correctly this time

Congrats!

@amp88 FWIW, there's an open issue on GH dealing with this.

More details please --

• Are you running XOA or XO (from sources)?
• What version? Are you up to date?
• Have you tried checking the logs from CLI?

Could be an issue with the script you used to build the VM. One way to know for sure is to try manually building one and then retesting.

This has been previously explained a couple of times on the forum. Here's one example -- https://xen-orchestra.com/forum/topic/643/auth-ldap-plugin-is-not-shown

How much ram did you allocate to the VM? FWIW, I've seen this type of error before when ram was below 1G.

@beber75 Do you know what version of XO you were running prior to upgrading? Also, what is your base OS?

You can try to issue the following command from the \opt\xenorchestra directory --

rm -rf node_modules
yarn
yarn build

This will clear out the cache and initiate a rebuild. FWIW, I just ran the update script and didn't encounter this issue.

So you are running Citrix Hypervisor, not XCP-ng, correct?

What version of XCP / XS / CH? Is it fully patched?

May be unrelated, but I had a similar issue on my most recent backup. Here's the relevant portion of the log --

       "result": {
            "code": "VDI_IO_ERROR",
            "params": [
              "Device I/O errors"
            ],
            "task": {
              "uuid": "007fb970-600c-5dc8-c527-c047778b2854",
              "name_label": "[XO] VDI Export",
              "name_description": "xxxx03",
              "allowed_operations": [],
              "current_operations": {},
              "created": "20200504T05:09:54Z",
              "finished": "20200504T06:01:31Z",
              "status": "failure",
              "resident_on": "OpaqueRef:e2781353-8cd6-0938-108d-1b7933d4c739",
              "progress": 1,
              "type": "<none/>",
              "result": "",
              "error_info": [
                "VDI_IO_ERROR",
                "Device I/O errors"
              ],
              "other_config": {},
              "subtask_of": "OpaqueRef:NULL",
              "subtasks": [],
              "backtrace": "(((process xapi)(filename ocaml/xapi/vhd_tool_wrapper.ml)(line 59))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 35))((process xapi)(filename ocaml/xapi/export_raw_vdi.ml)(line 41))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 35))((process xapi)(filename ocaml/xapi/export_raw_vdi.ml)(line 62)))"
            },
            "message": "VDI_IO_ERROR(Device I/O errors)",
            "name": "XapiError",
            "stack": "XapiError: VDI_IO_ERROR(Device I/O errors)\n    at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)\n    at _default (/opt/xen-orchestra/packages/xen-api/src/_getTaskResult.js:11:29)\n    at Xapi._addRecordToCache (/opt/xen-orchestra/packages/xen-api/src/index.js:837:24)\n    at forEach (/opt/xen-orchestra/packages/xen-api/src/index.js:858:14)\n    at Array.forEach (<anonymous>)\n    at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:848:12)\n    at /opt/xen-orchestra/packages/xen-api/src/index.js:1009:14\n    at Generator.next (<anonymous>)\n    at asyncGeneratorStep (/opt/xen-orchestra/packages/xen-api/dist/index.js:62:103)\n    at _next (/opt/xen-orchestra/packages/xen-api/dist/index.js:64:194)\n    at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:547:31)\n    at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:604:18)\n    at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:649:10)\n    at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:729:18)\n    at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:93:12)\n    at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:86:9)\n    at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:102:5)\n    at Immediate.Async.drainQueues [as _onImmediate] (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:15:14)\n    at processImmediate (internal/timers.js:456:21)"
          }
        },

This is with xo-server 5.59.0 and xo-web 5.59.0. My timeout=6 under advanced settings. I restarted the failed backups and they completed on the 2nd attempt.

@Biggen Yeah... definitely easier to backup / restore the config file.

Don't forget to disable the backups in the old VM if you don't turn it off.

@rjt said in Console keyboard problems using Firefox:

Rule out problems with your old firefox profile by creating a new firefox profile dedicated to non internet stuff

Just tried this, but didn't resolve the issue for me. In the current scenario, I am trying to launch an SSH session. I clicked the "SSH as..." button, but my typing is going to the console instead of the popup window.

Seems to be intermittent. This issue will go away, but then returns if I switch away from and then back to the XO console tab.

@ccsmith Please update your XO VM and then retest.

I've experienced this as well using the Window's version of Firefox. Not sure of the cause, but a restart of the browser seemed to fix it for me.

If you are using XOA w/ support, you may want to open a support ticket.

What OS version? Could this be due to licensing?