@julien-f Thank you! That appears to fix the error. Greatly appreciate your help and @olivierlambert.
Posts made by stevewest15
-
RE: Health Check Failing After Recent XOCE Update
-
RE: Health Check Failing After Recent XOCE Update
@Danp Thanks! So is this a bug or did I fail to make some changes after updating that's now causing these errors?
-
RE: Health Check Failing After Recent XOCE Update
@olivierlambert Thank you for assistance! I have updated nodejs to v18.19.0 and ran a quick backup test and still getting the same error (see below):
{ "data": { "mode": "delta", "reportWhen": "always" }, "id": "1704403800003", "jobId": "bff2ddd9-42c4-4e2f-9cbf-d1677c4722f7", "jobName": "Test Backup", "message": "backup", "scheduleId": "86086afa-89b4-4c97-b81f-f5b84bfd0de8", "start": 1704403800003, "status": "failure", "infos": [ { "data": { "vms": [ "605507d7-29cc-acee-176a-2e26a3726d39" ] }, "message": "vms" } ], "tasks": [ { "data": { "type": "VM", "id": "605507d7-29cc-acee-176a-2e26a3726d39", "name_label": "Email-Relay" }, "id": "1704403803299", "message": "backup VM", "start": 1704403803299, "status": "failure", "tasks": [ { "id": "1704403803307", "message": "clean-vm", "start": 1704403803307, "status": "success", "end": 1704403803362, "result": { "merge": false } }, { "id": "1704403803373", "message": "snapshot", "start": 1704403803373, "status": "success", "end": 1704403806203, "result": "b41c174e-511d-69cb-800d-c5d98c806fb2" }, { "data": { "id": "45ff0925-797b-43dd-a95c-7e298c61ad02", "isFull": true, "type": "remote" }, "id": "1704403806213", "message": "export", "start": 1704403806213, "status": "success", "tasks": [ { "id": "1704403807469", "message": "transfer", "start": 1704403807469, "status": "success", "end": 1704403945962, "result": { "size": 9496147968 } }, { "id": "1704403946008", "message": "health check", "start": 1704403946008, "status": "success", "tasks": [ { "id": "1704403946082", "message": "transfer", "start": 1704403946082, "status": "success", "end": 1704404004994, "result": { "size": 9496147456, "id": "6a6770c4-52f9-440b-5fd6-9bd7decc3930" } }, { "id": "1704404004994:0", "message": "vmstart", "start": 1704404004994, "status": "success", "end": 1704404030700 } ], "end": 1704404032136 }, { "id": "1704404032136:0", "message": "clean-vm", "start": 1704404032136, "status": "success", "end": 1704404032158, "result": { "merge": false } } ], "end": 1704404032159 }, { "data": { "id": "349e7130-da43-6550-e7c0-aa0a84102e0f", "isFull": true, "name_label": "Local storage", "type": "SR" }, "id": "1704403806214", "message": "export", "start": 1704403806214, "status": "failure", "tasks": [ { "id": "1704403807467", "message": "transfer", "start": 1704403807467, "status": "success", "end": 1704403944794, "result": { "size": 9496147968 } }, { "id": "1704403946008:0", "message": "health check", "start": 1704403946008, "status": "failure", "tasks": [ { "id": "1704403946078", "message": "copying-vm", "start": 1704403946078, "status": "success", "end": 1704404030703, "result": "OpaqueRef:3029e1b8-507e-436d-9634-d4e24b5e82c2" } ], "end": 1704404031113, "result": { "message": "healthCheckVm.add_tag is not a function", "name": "TypeError", "stack": "TypeError: healthCheckVm.add_tag is not a function\n at file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:61:33\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)" } } ], "end": 1704404031113, "result": { "message": "healthCheckVm.add_tag is not a function", "name": "TypeError", "stack": "TypeError: healthCheckVm.add_tag is not a function\n at file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:61:33\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)" } } ], "end": 1704404032159 } ], "end": 1704404032159 }
Thank you again for your assistance!
SW
-
Health Check Failing After Recent XOCE Update
Xen Orchestra, commit 0f00c
Master, commit 0f00cn lts: v20.10.0 (with npm 10.2.3)
nodejs: v12.22.5Hi,
XO backups have been working fine but after updating XCP 8.2 to 8.2.1 and updating XOCE to the latest build, the nightly backups are all failing the health check with the error "healthCheckVm.add_tag is not a function":
"result": { "message": "healthCheckVm.add_tag is not a function", "name": "TypeError", "stack": "TypeError: healthCheckVm.add_tag is not a function\n at file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:61:33\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
I'm unsure if the XCP update or the XOCE recent update is causing the above error.
I'm wondering if it is safe to revert XOCE VM to an older version or will that break something w/ XCP?
Thank you,
SW
-
RE: Continuous Replication job fails "TypeError: Cannot read properties of undefined (reading 'uuid')" at #isAlreadyOnHealthCheckSr
@florent Thank you for your assistance!
I'm also running into this issue after upgrading to the latest build (Xen Orchestra, commit d3077):
{ "data": { "id": "349e7130-da43-6550-e7c0-aa0a84102e0f", "isFull": false, "name_label": "Local storage", "type": "SR" }, "id": "1690857015572:0", "message": "export", "start": 1690857015572, "status": "failure", "tasks": [ { "id": "1690857016890", "message": "transfer", "start": 1690857016890, "status": "success", "end": 1690857173019, "result": { "size": 8317447680 } }, { "id": "1690857209204:0", "message": "health check", "start": 1690857209204, "status": "failure", "end": 1690857209217, "result": { "message": "Cannot read properties of undefined (reading 'uuid')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'uuid')\n at #isAlreadyOnHealthCheckSr (file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:21:49)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:43:17" } } ], "end": 1690857209217, "result": { "message": "Cannot read properties of undefined (reading 'uuid')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'uuid')\n at #isAlreadyOnHealthCheckSr (file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:21:49)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:43:17" } } ], "end": 1690857647768 }, { "data": { "type": "VM", "id": "a0ba50c3-f6d3-32ff-cda7-9243d291a6c0", "name_label": "XOCE" }, "id": "1690857647776", "message": "backup VM", "start": 1690857647776, "status": "failure", "tasks": [ { "id": "1690857647781", "message": "clean-vm", "start": 1690857647781, "status": "success", "end": 1690857647865, "result": { "merge": false } }, { "id": "1690857647964", "message": "snapshot", "start": 1690857647964, "status": "success", "end": 1690857649748, "result": "a25a21f6-cfdd-5f8d-9753-36a7f1eb7302" }, { "data": { "id": "45ff0925-797b-43dd-a95c-7e298c61ad02", "isFull": false, "type": "remote" }, "id": "1690857649748:0", "message": "export", "start": 1690857649748, "status": "success", "tasks": [ { "id": "1690857651540", "message": "transfer", "start": 1690857651540, "status": "success", "end": 1690857709369, "result": { "size": 1015333376 } }, { "id": "1690857713360", "message": "health check", "start": 1690857713360, "status": "success", "tasks": [ { "id": "1690857713479", "message": "transfer", "start": 1690857713479, "status": "success", "end": 1690857820321, "result": { "size": 18864355840, "id": "2d68d34a-7a93-39fb-0095-a505a761c590" } }, { "id": "1690857820321:0", "message": "vmstart", "start": 1690857820321, "status": "success", "end": 1690857840697 } ], "end": 1690857842923 }, { "id": "1690857842923:0", "message": "clean-vm", "start": 1690857842923, "status": "success", "end": 1690857842950, "result": { "merge": true } } ], "end": 1690857842962 }, { "data": { "id": "349e7130-da43-6550-e7c0-aa0a84102e0f", "isFull": false, "name_label": "Local storage", "type": "SR" }, "id": "1690857649749", "message": "export", "start": 1690857649749, "status": "failure", "tasks": [ { "id": "1690857651536", "message": "transfer", "start": 1690857651536, "status": "success", "end": 1690857708807, "result": { "size": 1015333376 } }, { "id": "1690857713360:0", "message": "health check", "start": 1690857713360, "status": "failure", "end": 1690857713370, "result": { "message": "Cannot read properties of undefined (reading 'uuid')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'uuid')\n at #isAlreadyOnHealthCheckSr (file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:21:49)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:43:17" } } ], "end": 1690857713370, "result": { "message": "Cannot read properties of undefined (reading 'uuid')", "name": "TypeError", "stack": "TypeError: Cannot read properties of undefined (reading 'uuid')\n at #isAlreadyOnHealthCheckSr (file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:21:49)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async file:///opt/xen-orchestra/@xen-orchestra/backups/_runners/_writers/_MixinXapiWriter.mjs:43:17" } } ], "end": 1690857842962 },
Thank you again!
SW
-
RE: MTU change
Hi,
I'm trying to change the MTU but keep getting "The uuid you supplied was invalid" error (see screenshot below). I'm copying the network uuid to use in the cli command. Any thoughts/recommendations?
Thx,
SW
-
RE: Migrate VM Error: VDI_NOT_IN_MAP
@Darkbeldin Thank you, I looked at the SMlog and searched for this snapshot where I only saw activity back in March 27 and yesterday (April 26). See attachment.
smlog.txt@olivierlambert Thank you! How do I add a new disk and ensure it doesn't use the same device id (/dev/xvdc) as that is currently used by the VM? The VM currently sees this:
/dev/xvda1 94G 18G 76G 19% /
/dev/xvdb1 12G 4.4G 7.7G 37% /var/lib
/dev/xvdc1 80G 23G 58G 28% /var/www
/dev/xvdd1 200G 54G 147G 27% /EmailsWhat does "Import VDI content" and "Export VDI content" do? Just trying to see if I can copy this snapshot and then attach it to the VM:
Thank You,
SW
-
Migrate VM Error: VDI_NOT_IN_MAP
Hi,
Trying to migrate VM from old XCP-NG (8.0.1) to a newer server running xcp-ng (8.2.1) and I'm getting the following error:
Xen Orchestra, commit d1f2e
xo-server 5.112.0vm.migrate { "vm": "012b07a1-24cf-6d59-5faf-804e0e187b7a", "mapVdisSrs": { "94396c87-11b4-4f0e-a996-985cb74d07bf": "088980d4-0fdd-18bf-4c36-a555c35b011b", "7a1a6cce-5143-4fd9-b311-6c82d5b26d02": "191299cb-bb3b-872b-3f42-6ae2c3ccab38", "220b6828-53d8-42d0-99b3-83e731f19904": "088980d4-0fdd-18bf-4c36-a555c35b011b" }, "mapVifsNetworks": { "f6b40ac2-0e4a-51a0-d478-b1c989be72d7": "3a0b3ba8-e6e9-c73c-d968-dde5511f98be", "7984e99e-c8df-2f72-fe93-ad1388e7f50f": "67982c5b-b56d-f9dc-0288-b369ee90e16b" }, "migrationNetwork": "3a0b3ba8-e6e9-c73c-d968-dde5511f98be", "sr": "47bdfc16-4832-a187-8c8a-0bb377b9e255", "targetHost": "675fbc71-a2c7-4301-856a-6dd6a1b9651e" } { "code": 21, "data": { "objectId": "012b07a1-24cf-6d59-5faf-804e0e187b7a", "code": "VDI_NOT_IN_MAP" }, "message": "operation failed", "name": "XoError", "stack": "XoError: operation failed at operationFailed (/opt/xen-orchestra/packages/xo-common/api-errors.js:26:11) at file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:561:15 at Xo.migrate (file:///opt/xen-orchestra/packages/xo-server/src/api/vm.mjs:547:3) at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:401:20)" }
This VM has four attached local storage but XO is only showing 3 local storage while XCP-ng Center (20.04.01) shows the correct number:
When I go in XO Health, it's reporting the following:
When I open up the disk in XO, I see the following:
After about 30 minutes, the list of disks changed and now it shows the following:
Any recommendations on what could be the issue(s)? And how best I should proceed to fix the issue(s)?
Thank You,
SW
-
RE: Recommendations on heterogeneous pools
@tjkreidl Thank you for your assistance and recommendation!
-
Recommendations on heterogeneous pools
Hi,
Hoping someone here can help me with if I can create a pool from the below hosts without negatively impacting VM stability / live migrations. I read the docs but it seems the doc are missing a link to "see Hosts and resource pools".
Here are my current hosts which are all currently not in a pool:
Host 1: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Host 2: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Host 3: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
Host 4: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
Host 5: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
Host 6: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHzShared NFS storage will be either TrueNAS or Synology depending on which storage offers best performance and VM reliability.
The goal is to build this pool for HA or have two different pools each setup as HA.
Thank You,
SW
-
RE: Troubleshooting Controll Domain High Memory Warning
@olivierlambert Thank You Oliver! I've been meaning to move these 2 VMs to newer servers running latest XCP-ng. The issue in trying to move them is the migration takes so long as the VMs are very large.
Any recommendations on how best to move large VMs that use a mix of local and network storage to a new XCP-ng?
-
Troubleshooting Controll Domain High Memory Warning
Hi,
I'm running an older version of XCP-ng (v 8.0.1) which I'm trying to figure out what is causing the Dom0 high memory usage:
Checking dmesg shows tons of the following messages but not sure what they mean:
[39998832.644126] block tdx: sector-size: 512/512 capacity: 167772160 [39998833.318498] block tdy: sector-size: 512/512 capacity: 209715200 [39998844.591972] block tdz: sector-size: 512/512 capacity: 25165824 [39998844.612378] block tdab: sector-size: 512/512 capacity: 209715200 [39998844.665207] block tdaa: sector-size: 512/512 capacity: 209715200 [39998844.825059] block tdac: sector-size: 512/512 capacity: 167772160 [39998847.072573] block tdad: sector-size: 512/512 capacity: 25165824 [39998847.342641] block tdae: sector-size: 512/512 capacity: 209715200 [39998847.382385] block tdaf: sector-size: 512/512 capacity: 209715200 [39998848.091827] block tdag: sector-size: 512/512 capacity: 167772160 [39999260.166570] block tdr: sector-size: 512/512 capacity: 62914560 [39999262.000706] block tds: sector-size: 512/512 capacity: 62914560 [39999277.792759] block tds: sector-size: 512/512 capacity: 8388608 [39999277.793975] block tdt: sector-size: 512/512 capacity: 31457280 [39999277.800976] block tdr: sector-size: 512/512 capacity: 104857600 [39999277.839117] block tdu: sector-size: 512/512 capacity: 419430400 [39999278.241445] block tdv: sector-size: 512/512 capacity: 629145600 [39999280.463193] block tdw: sector-size: 512/512 capacity: 31457280 [39999280.546328] block tdx: sector-size: 512/512 capacity: 104857600 [39999280.684838] block tdy: sector-size: 512/512 capacity: 8388608 [39999280.733995] block tdz: sector-size: 512/512 capacity: 419430400 [39999281.088353] block tdaa: sector-size: 512/512 capacity: 629145600
Any recommendations on what to check before I do a full restart of the server?
Thank You,
SW
-
RE: Backup started to fail
@Darkbeldin Thank you! I was able to get in after 1st logging to the xen-orchestra.com website, updating my profile, and then clicking on support from that portal.
Here is the Ticket#775709.
Look forward to your update!
Best Regards,
SW
-
RE: Backup started to fail
@florent Thank you but can't seem to login to the support ticket system:
Login failed. Have you double-checked your credentials and completed the email verification step?
Not sure how to get the email verification or to reset password as I don't see that option on the login page.
-
RE: Backup started to fail
XO 5.67.0
Hi,
@florent @julien-f I just updated XO via the web browser from an older version to the latest version 5.67.0 and now I'm getting the same issue as @fred974 :
Mar 07 08:20:29 xoa xo-server[13189]: at S3Handler._list (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/fs/src/s3.js:199:21) Mar 07 08:20:29 xoa xo-server[13189]: at runMicrotasks (<anonymous>) Mar 07 08:20:29 xoa xo-server[13189]: at processTicksAndRejections (node:internal/process/task_queues:96:5) { Mar 07 08:20:29 xoa xo-server[13189]: dir: '/xo-vm-backups' Mar 07 08:20:29 xoa xo-server[13189]: } Mar 07 08:20:29 xoa xo-server[13189]: } Mar 07 08:34:12 xoa xo-server[13189]: 2022-03-07T13:34:12.720Z xo:xo-mixins:backups-ng WARN listVmBackups for remote 53745311-c2b2-41d9-bf98-67d9789b16a3: { Mar 07 08:34:12 xoa xo-server[13189]: error: Error: more than 1000 objects, unsupported in this implementation Mar 07 08:34:12 xoa xo-server[13189]: at S3Handler._list (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/fs/src/s3.js:199:21) Mar 07 08:34:12 xoa xo-server[13189]: at runMicrotasks (<anonymous>) Mar 07 08:34:12 xoa xo-server[13189]: at processTicksAndRejections (node:internal/process/task_queues:96:5) { Mar 07 08:34:12 xoa xo-server[13189]: dir: '/xo-vm-backups' Mar 07 08:34:12 xoa xo-server[13189]: } Mar 07 08:34:12 xoa xo-server[13189]: }
Backblaze Bucket:
After doing the XO update, I can't see the list of backups when I go to Backup > Restore:
Prior to updating XO to the latest version, I was able to see the backups on Backblaze when going to Backup > Restore.
Here is the prior version of XOA installed which didn't have this issue:
Mar 7 06:52:13 xoa xoa-updater[479]: stable channel selected Mar 7 06:52:13 xoa xoa-updater[479]: Following packages will be removed: Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra-upload-ova 0.1.4 Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra 5.65.3 Mar 7 06:52:13 xoa xoa-updater[479]: xo-server-telemetry 0.5.0 Mar 7 06:52:13 xoa xoa-updater[479]: xo-server-xoa 0.12.0 Mar 7 06:52:13 xoa xoa-updater[479]: xo-server 5.85.1 Mar 7 06:52:13 xoa xoa-updater[479]: xo-web-free 5.90.0 Mar 7 06:52:13 xoa xoa-updater[479]: xoa-cli 0.28.0 Mar 7 06:52:13 xoa xoa-updater[479]: xoa-updater 0.39.0 Mar 7 06:52:13 xoa xoa-updater[479]: New versions available: Mar 7 06:52:13 xoa xoa-updater[479]: node 16.13.2 (14.17.5 installed) Mar 7 06:52:13 xoa xoa-updater[479]: npm 8.4.0 (6.14.13 installed) Mar 7 06:52:13 xoa xoa-updater[479]: New versions available: Mar 7 06:52:13 xoa xoa-updater[479]: xoa-updater 0.39.0 (0.39.0 installed) Mar 7 06:52:13 xoa xoa-updater[479]: New versions available: Mar 7 06:52:13 xoa xoa-updater[479]: xen-orchestra 5.67.0 (5.65.3 installed) Mar 7 06:52:13 xoa xoa-updater[479]: xo-server 5.87.0 (5.85.1 installed) Mar 7 06:52:13 xoa xoa-updater[479]: xo-web-free 5.92.0 (5.90.0 installed) Mar 7 06:52:13 xoa xoa-updater[479]: xoa-cli 0.29.0 (0.28.0 installed) Mar 7 06:52:16 xoa xoa-updater[479]: stable channel selected Mar 7 06:52:16 xoa xoa-updater[479]: Following packages will be removed: Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra-upload-ova 0.1.4 Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra 5.65.3 Mar 7 06:52:16 xoa xoa-updater[479]: xo-server-telemetry 0.5.0 Mar 7 06:52:16 xoa xoa-updater[479]: xo-server-xoa 0.12.0 Mar 7 06:52:16 xoa xoa-updater[479]: xo-server 5.85.1 Mar 7 06:52:16 xoa xoa-updater[479]: xo-web-free 5.90.0 Mar 7 06:52:16 xoa xoa-updater[479]: xoa-cli 0.28.0 Mar 7 06:52:16 xoa xoa-updater[479]: xoa-updater 0.39.0 Mar 7 06:52:16 xoa xoa-updater[479]: New versions available: Mar 7 06:52:16 xoa xoa-updater[479]: node 16.13.2 (14.17.5 installed) Mar 7 06:52:16 xoa xoa-updater[479]: npm 8.4.0 (6.14.13 installed) Mar 7 06:52:16 xoa xoa-updater[479]: New versions available: Mar 7 06:52:16 xoa xoa-updater[479]: xoa-updater 0.39.0 (0.39.0 installed) Mar 7 06:52:16 xoa xoa-updater[479]: New versions available: Mar 7 06:52:16 xoa xoa-updater[479]: xen-orchestra 5.67.0 (5.65.3 installed) Mar 7 06:52:16 xoa xoa-updater[479]: xo-server 5.87.0 (5.85.1 installed) Mar 7 06:52:16 xoa xoa-updater[479]: xo-web-free 5.92.0 (5.90.0 installed) Mar 7 06:52:16 xoa xoa-updater[479]: xoa-cli 0.29.0 (0.28.0 installed)
-
RE: Xen Orchestra from source with Let's Encrypt certificates
Hi,
I'm testing using certbot to install SSL cert for XOCE using Lets Encrypt instructions but need to know what is the path for XOCE webroot?
Thx,
SW
-
RE: Initial Backup only creates Delta Restore
Thank you @olivierlambert & @Danp . Greatly appreciate your assistance!
-
Initial Backup only creates Delta Restore
Xen Orchestra, commit 2e8e2
xo-server 5.86.3
xo-web 5.91.2I have created a new backup job and set "Full Backup interval" to 7. Per the docs, I thought the 1st backup would be a full one and then deltas.
I see in the backup logs "Full" but when I go to restore, I only see option for "Delta". Where can I find the "Full" backup? Also, why would there be a delta if this job only ran once?
Thank You,
SW
-
RE: S3 Backup Restore File Issue
Thank you greatly appreciate your assistance as always!