XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 21
    • Posts 76
    • Groups 0
    K Offline
    1. Home
    2. Kajetan321
    3. Posts

    Posts

    Recent Best Controversial
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      @FritzGerald

      Thanks! Running

      systemctl enable --now ups-driver.service
      

      got ups-driver.service going, then following the instructions you provided earlier got the rest of the two services running, even after a reboot.

      I'm now able to run upsc apc@localhost and get the correct output listing all the properties of the UPS even after a reboot.

      posted in XCP-ng
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      @FritzGerald Thank you for the follow up. It looks to me like none of the three services are running after a reboot.

      Executing

      systemctl status ups-driver.service nut-server.service nut-monitor.service
      

      Results in:

      ● ups-driver.service - NUT UPS Driver
         Loaded: loaded (/etc/systemd/system/ups-driver.service; disabled; vendor preset: disabled)
         Active: inactive (dead)
      
      ● nut-server.service - Network UPS Tools - power devices information server
         Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled; vendor preset: disabled)
        Drop-In: /etc/systemd/system/nut-server.service.d
                 └─ups-driver.conf
         Active: inactive (dead)
      
      ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
         Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled; vendor preset: disabled)
        Drop-In: /etc/systemd/system/nut-monitor.service.d
                 └─nut-server.conf
         Active: inactive (dead)
      
      posted in XCP-ng
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      @FritzGerald I followed the procedure outline above. I did not see any errors when following the procedure however when I rebooted and then ran "upsc apc@localhost" I got "Error: Connection failure: Cannot assign requested address"

      When I run "sudo systemctl status nut-server" I get " Active: inactive (dead)"

      Running

      upsdrvctl start
      systemctl start nut-server.service
      systemctl start nut-monitor.service
      

      fixes the issue. It looks like nut-server still does not start automatically at boot. How would I troubleshoot this further? I'm not a Linux system admin 😞

      Gemini suggested rebooting and running "journalctl -u nut-server.service -b 0" which resulted in "-- No entries --"

      posted in XCP-ng
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      @FritzGerald Understood. Thanks for posting. I will get back to this as soon as I have some time.

      posted in XCP-ng
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      @FritzGerald Thank you for taking the time to write up the install procedure. I was able to follow it on my end and it seems to be working. What commands do you use to set the three services to start up automatically at boot up? Right now if I reboot and run upsc apc@localhost it throws an error until I manually do:

      upsdrvctl start
      systemctl start nut-server.service
      systemctl start nut-monitor.service
      
      posted in XCP-ng
      K
      Kajetan321
    • RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

      Looking at Git, it doesn't seem like it, so I guess that answers my question.

      posted in Backup
      K
      Kajetan321
    • RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

      @christopher-petzel Hello. Has the fix been merged yet? I'm on commit 03865 and I'm still getting this problem.

      posted in Backup
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      It looks like "yum remove nut" does the trick.

      posted in XCP-ng
      K
      Kajetan321
    • RE: [SOLVED] Just FYI: current update seams to break NUT dependancies

      I'm having the same problem. I could never get NUT to work properly anyways. What's the best way to uinstal it?

      posted in XCP-ng
      K
      Kajetan321
    • RE: Deteching Host is Failing with Error

      @MajorP93 OK I tried disconnecting the pool first but now I'm getting:

      server.disable
      {}
      {
        "code": 10,
        "data": {
          "errors": [
            {
              "instancePath": "",
              "schemaPath": "#/required",
              "keyword": "required",
              "params": {
                "missingProperty": "id"
              },
              "message": "must have required property 'id'"
            }
          ]
        },
        "message": "invalid parameters",
        "name": "XoError",
        "stack": "XoError: invalid parameters
          at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202602261435/packages/xo-common/api-errors.js:26:11)
          at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202602261435/packages/xo-server/src/xo-mixins/api.mjs:121:22)
          at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202602261435/packages/xo-server/src/xo-mixins/api.mjs:409:19)"
      }
      

      I guess I will just power down the host and that will be it, as Olivier recommends.

      posted in Management
      K
      Kajetan321
    • Deteching Host is Failing with Error

      Hello, I’m trying to decommission a host. It is the only host in its pool. There are no VMs on this host. When I go to Home > Hosts > select host > Advanced > Detach I get:

      host.detach
      {
        "host": "69c0c257-a547-4d49-8270-b49eafe35c2c"
      }
      {
        "code": "INTERNAL_ERROR",
        "params": [
          "Xapi_pool.Cannot_eject_master"
        ],
        "call": {
          "duration": 4,
          "method": "pool.eject",
          "params": [
            "* session id *",
            "OpaqueRef:a845b495-af26-4fd0-8b82-813167b3f2ca"
          ]
        },
        "message": "INTERNAL_ERROR(Xapi_pool.Cannot_eject_master)",
        "name": "XapiError",
        "stack": "XapiError: INTERNAL_ERROR(Xapi_pool.Cannot_eject_master)
          at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202602261435/packages/xen-api/_XapiError.mjs:16:12)
          at file:///opt/xo/xo-builds/xen-orchestra-202602261435/packages/xen-api/transports/json-rpc.mjs:38:21
          at runNextTicks (node:internal/process/task_queues:65:5)
          at processImmediate (node:internal/timers:472:9)
          at process.callbackTrampoline (node:internal/async_hooks:130:17)"
      }
      
      

      Any ideas? I’m running Xen Orchestra commit 32220 from source. I tried rebooting the host and updating XO but this changed nothing, still getting the same error. The error seems to imply that one cannot eject a pool master but how do I decommission the host that is its own pool master?

      posted in Management
      K
      Kajetan321
    • RE: Pass Through of USB Storage Adapters Not Working

      @olivierlambert The enclosure works fine on an old computer with only USB 2. I'm not sure I understand what you mean.

      posted in Hardware
      K
      Kajetan321
    • RE: Pass Through of USB Storage Adapters Not Working

      It looks like I'm not the only one with this issue. Someone on Reddit is having the same problem.

      https://www.reddit.com/r/xcpng/comments/1getxr8/xcpng_83_cant_add_usb_drive_to_vm/

      Just for fun, I tried passing through my devices in VMware, it seems to work there.

      posted in Hardware
      K
      Kajetan321
    • RE: Pass Through of USB Storage Adapters Not Working

      @DustinB Sure, here we go:

      USB Mass Storage Device 	VLI Manufacture String-VLI Product String-ABCDEFA74602	VIA Labs, Inc. [0x2109]	VL817 SATA Adaptor [0x0715]	Super Speed - USB 3.0 [5Gb/s], Port: 1, Address: 4, Revision: 0x0000	USB\VID_2109&PID_0715\ABCDEFA74602
      USB Mass Storage Device 	F:\ - VLI Manufacture String-VLI Product String-ABCDEFA74566	VIA Labs, Inc. [0x2109]	VL817 SATA Adaptor [0x0715]	Super Speed - USB 3.0 [5Gb/s], Port: 1, Address: 4, Revision: 0x0148	USB\VID_2109&PID_0715\ABCDEFA74566
      USB Mass Storage Device 	F:\ - JMicron-External USB 3.0-201703310007F	JMicron Technology [0x152D]	External Disk 3.0 [0x0578]	Super Speed - USB 3.0 [5Gb/s], Port: 1, Address: 4, Revision: 0x0204	USB\VID_152D&PID_0578\201703310007F
      USB Mass Storage Device 	F:\ - General-USB to SATA/PCIe Bridge-0123456789ABCDEF	JMicron Technology [0x152D]	0x0581	Super Speed - USB 3.0 [5Gb/s], Port: 1, Address: 4, Revision: 0x4204	USB\VID_152D&PID_0581\0123456789ABCDEF
      
      posted in Hardware
      K
      Kajetan321
    • RE: Pass Through of USB Storage Adapters Not Working

      @DustinB

      USB 3.0 to 2.5-Inch SATA Adapter
      EC-SSHD
      https://sabrent.com/products/ec-sshd?srsltid=AfmBOorOY1TDHQ8ZTa6qt2w2b-yWNkj3sa10l1AomEChZ1wSecDe1iNJ

      Fideco M.2 SATA External SSD Enclosure
      Similar to this
      https://www.ebay.ca/itm/394615203827

      ORICO 2.5 Inch SATA to USB Transparent HDD Enclosure
      https://oricotechs.com/products/orico-2-5-inch-sata-to-usb-transparent-hdd-enclosure

      RIITOP NVMe to USB Docking Station, M.2 SSD Enclosure for Both NVMe and (B+M Key SATA) SSD
      https://www.riitop.com/en-ca/collections/msata-ssd-adapter/products/nvme-to-usb-docking-station-riitop-m-2-ssd-enclosure-for-both-nvme-and-b-m-key-sata-ssd

      posted in Hardware
      K
      Kajetan321
    • Pass Through of USB Storage Adapters Not Working

      I’m able to pass through USB thumb drives and external hard drives no problem. However then I try to pass through a USB hard drive enclosure or adapter the guest OS doesn’t seem to see the deice. I have tried two enclosures and two USB storage adapters so far and none of them seem to work. I’m using the GUI in XO to do the pass through. I’m running Xen Orchestra, commit 83a69, XCP-ng 8.3 and Windows 11 as guest OS. Is this a known issue or am I doing something wrong?

      posted in Hardware
      K
      Kajetan321
    • RE: Unable to migrate VM: HANDLE_INVALID(SR, OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394)

      Update: I was able to move the VM to a different host that is also xcp-ng 8.2. When I tried moving the VM back to where it came from now I'm getting: NO_HOSTS_AVAILABLE()

      vm.migrate
      {
        "mapVdisSrs": {
          "f4d88025-9e26-44a1-8028-4d5d9c11c994
      
      ": "18850841-5eb8-6b28-73ba-cae1c40af157"
        },
        "mapVifsNetworks": {
          "b56126a8-85ab-80de-9db8-4864ec5618e5
      
      ": "99b40169-8dab-6e9d-db96-23277b405b4a
      
      "
        },
        "migrationNetwork": "99b40169-8dab-6e9d-db96-23277b405b4a
      
      ",
        "sr": "18850841-5eb8-6b28-73ba-cae1c40af157",
        "targetHost": "69c0c257-a547-4d49-8270-b49eafe35c2c",
        "vm": "78938c32-eb52-491f-1fbf-3ad5d2e374f0"
      }
      {
        "code": "NO_HOSTS_AVAILABLE",
        "params": [],
        "task": {
          "uuid": "4eb56a28-ffa7-cee6-31e1-87209af8de75
      
      ",
          "name_label": "Async.VM.migrate_send",
          "name_description": "",
          "allowed_operations": [],
          "current_operations": {},
          "created": "20250131T20:51:54Z",
          "finished": "20250131T20:51:54Z",
          "status": "failure",
          "resident_on": "OpaqueRef:72cbec6b-d489-49ca-a8a8-e623e3c5f4e4",
          "progress": 1,
          "type": "<none/>",
          "result": "",
          "error_info": [
            "NO_HOSTS_AVAILABLE"
          ],
          "other_config": {},
          "subtask_of": "OpaqueRef:NULL",
          "subtasks": [],
          "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_placement.ml)(line 104))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1199))((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/helpers.ml)(line 1356))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1191))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2279))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 205))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 95)))"
        },
        "message": "NO_HOSTS_AVAILABLE()",
        "name": "XapiError",
        "stack": "XapiError: NO_HOSTS_AVAILABLE()
          at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/_XapiError.mjs:16:12)
          at default (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/_getTaskResult.mjs:13:29)
          at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1068:24)
          at file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1102:14
          at Array.forEach (<anonymous>)
          at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1092:12)
          at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1265:14)"
      }
      

      I rebooted XO and tried moving the VM to the xcp-ng 8.3 machine again. It looks like the task started but now it's hung at "Connection to VM console (on xcp-m83) 0%" and I can't "Cancel" or "Destroy" the task 😞

      posted in Management
      K
      Kajetan321
    • Unable to migrate VM: HANDLE_INVALID(SR, OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394)

      I'm trying to migrate a powered off VM from one host to another and when I try to migrate I get the error below:

      The source host is xcp-ng 8.2 and the destination host is xcp-ng 8.3

      vm.migrate
      {
        "vm": "78938c32-eb52-491f-1fbf-3ad5d2e374f0",
        "mapVifsNetworks": {
          "b56126a8-85ab-80de-9db8-4864ec5618e5
      
      ": "99b40169-8dab-6e9d-db96-23277b405b4a
      
      "
        },
        "migrationNetwork": "99b40169-8dab-6e9d-db96-23277b405b4a
      
      ",
        "sr": "18850841-5eb8-6b28-73ba-cae1c40af157",
        "targetHost": "69c0c257-a547-4d49-8270-b49eafe35c2c"
      }
      {
        "code": "HANDLE_INVALID",
        "params": [
          "SR",
          "OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394
      
      "
        ],
        "task": {
          "uuid": "b0365bf6-8275-0194-fa8d-463cd966463c
      
      ",
          "name_label": "Async.VM.migrate_send",
          "name_description": "",
          "allowed_operations": [],
          "current_operations": {},
          "created": "20250131T19:17:57Z",
          "finished": "20250131T19:17:58Z",
          "status": "failure",
          "resident_on": "OpaqueRef:e3f0dcf1-42a7-4ed2-afed-1d387e305657",
          "progress": 1,
          "type": "<none/>",
          "result": "",
          "error_info": [
            "HANDLE_INVALID",
            "SR",
            "OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394
      
      "
          ],
          "other_config": {},
          "subtask_of": "OpaqueRef:NULL",
          "subtasks": [],
          "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 1573))((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/message_forwarding.ml)(line 131))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1228))((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/message_forwarding.ml)(line 2298))((process xapi)(filename lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/xapi/rbac.ml)(line 205))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 95)))"
        },
        "message": "HANDLE_INVALID(SR, OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394
      
      )",
        "name": "XapiError",
        "stack": "XapiError: HANDLE_INVALID(SR, OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394
      
      )
          at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/_XapiError.mjs:16:12)
          at default (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/_getTaskResult.mjs:13:29)
          at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1068:24)
          at file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1102:14
          at Array.forEach (<anonymous>)
          at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1092:12)
          at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202501311655/packages/xen-api/index.mjs:1265:14)"
      }
      

      I tried to move the VM between hosts using XCP-ng Center and also got an error:

      Migrating VM 'IPM-ova on 'xcp-m90t'' to 'xcp-m83 in 'xcp-m83''
      Object has been deleted.SR:OpaqueRef:e8fd26cd-3470-4ef8-9738-8c056e034394
      Time: 00:00:01	xcp-m83	Jan 31, 2025 2:35 PM	Dismiss
      

      I'm able to move other VMs around just fine.

      posted in Management
      K
      Kajetan321
    • What OS is XCP-ng 8.3 based on?

      Is XCP-ng 8.3 based on CentOS 8.5 or something else? I'm having problems getting NUT to work and I'd like to try to get it working on the "parent" OS first.

      posted in Development
      K
      Kajetan321