Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    263 Topics
    2k Posts
    DustyArmstrongD

    I'm getting tons of Mdadm errors from Xen Orchestra, but not really sure why.

    host.getMdadmHealth { "id": "d2de9e76-ffbf-4640-9d68-43178c7c4006" } { "code": "-1", "params": [ "Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1", "", "Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 101, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/raid.py\", line 21, in check_raid_pool result = run_command(['mdadm', '--detail', device]) File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 70, in run_command raise subprocess.CalledProcessError(process.returncode, command, None) CalledProcessError: Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1 " ], "task": { "uuid": "34429da6-56ee-9b5c-c465-b0493920b3f4", "name_label": "Async.host.call_plugin", "name_description": "", "allowed_operations": [], "current_operations": {}, "created": "20250117T09:42:09Z", "finished": "20250117T09:42:09Z", "status": "failure", "resident_on": "OpaqueRef:f0015d71-0ac1-4a79-bf0d-3700f79ba394", "progress": 1, "type": "<none/>", "result": "", "error_info": [ "-1", "Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1", "", "Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 101, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/raid.py\", line 21, in check_raid_pool result = run_command(['mdadm', '--detail', device]) File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 70, in run_command raise subprocess.CalledProcessError(process.returncode, command, None) CalledProcessError: Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1 " ], "other_config": {}, "subtask_of": "OpaqueRef:NULL", "subtasks": [], "backtrace": "(((process xapi)(filename ocaml/xapi-client/client.ml)(line 7))((process xapi)(filename ocaml/xapi-client/client.ml)(line 19))((process xapi)(filename ocaml/xapi-client/client.ml)(line 8780))((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": "-1(Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1, , Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 101, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/raid.py\", line 21, in check_raid_pool result = run_command(['mdadm', '--detail', device]) File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 70, in run_command raise subprocess.CalledProcessError(process.returncode, command, None) CalledProcessError: Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1 )", "name": "XapiError", "stack": "XapiError: -1(Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1, , Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 101, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/raid.py\", line 21, in check_raid_pool result = run_command(['mdadm', '--detail', device]) File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 70, in run_command raise subprocess.CalledProcessError(process.returncode, command, None) CalledProcessError: Command '['mdadm', '--detail', '/dev/md127']' returned non-zero exit status 1 ) at Function.wrap (file:///home/node/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12) at default (file:///home/node/xen-orchestra/packages/xen-api/_getTaskResult.mjs:13:29) at Xapi._addRecordToCache (file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1068:24) at file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1102:14 at Array.forEach (<anonymous>) at Xapi._processEvents (file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1092:12) at Xapi._watchEvents (file:///home/node/xen-orchestra/packages/xen-api/index.mjs:1265:14)" }

    Neither host with ID 2de9e76-ffbf-4640-9d68-43178c7c4006 or f0015d71-0ac1-4a79-bf0d-3700f79ba394 are using a software RAID. It may be because I haven't updated the hosts in quite some time. There is no output on either host for cat /proc/mdstat.

    Is there a way I can just turn off this check?

  • ACLs, Self-service, Cloud-init, Load balancing...

    75 Topics
    657 Posts
    olivierlambertO

    @pdonias is working on it (among many other things), I don't know the timeline, but either this or the next release.

  • All XO backup features: full and incremental, replication, mirrors...

    285 Topics
    3k Posts
    Tristis OrisT

    Can confirm [NOSNAP] [NOBAK] works with xen 8.2, xo 3a212.
    Well NOSNAP can't technicaly work, but it don't break anything.

  • Everything related to Xen Orchestra's REST API

    43 Topics
    314 Posts
    S

    @pxn said in Java SDK, XmlRpcClientException: Failed to parse server's response: Duplicate name: restrict_vtpm:

    If you still encounter this issue - I found the way to bypass it.
    You can create your own mapper by extending on RecursiveTypeParserImpl and just copy-paste logic from MapParser (package org.apache.xmlrpc.parser;), except that logic of checking duplication, then you can inject custom parser to your custom factory (Extend TypeFactoryImpl and override getParser method). And inject this Factory to your client

    new XmlRpcClient().setTypeFactory(new CustomFactory(client));

    This works fine for me, I hope this could help you.

    Alex

  • Terraform, Packer or any tool to do IaC

    22 Topics
    199 Posts
    nathanael-hN

    @wezke Hello, can you switch to this latest version of the provider, ensure that your configuration is still valid or fix what would be needed, and report how it behaves?

    https://registry.terraform.io/providers/vatesfr/xenorchestra/latest

  • new smb remote fails

    4
    0 Votes
    4 Posts
    113 Views
    G

    @gonzametal I modified sudoers and could create the folder in the terminar but the error still there (I think because the syscall). I will install as root again to avoid this kind of issues in the future

  • VDI migration

    8
    0 Votes
    8 Posts
    206 Views
    DanpD

    @sb2014 I've encountered this particular issue once before, and these were the steps we used to correct it --

    Shutdown the VM Export the snapshot's VDI from the SR's DIsks tab using XVA file format Forget the snapshot Import the XVA file created in the earlier step Attach the newly imported disk to the target VM Start the VM to verify that it boots correctly

    Regards,
    Dan

  • Changing the VM Advanced setting "Viridian" doesn't stick

    2
    0 Votes
    2 Posts
    103 Views
    DanpD

    I confirm this behavior. Checking with the dev team to see if this is by design.

  • Active directory authentication

    12
    0 Votes
    12 Posts
    251 Views
    G

    @dinhngtu LDP is using SSL, and no firewall between, so I think there be a ldaps misconfiguration

  • Deleting a VM template?

    Solved
    3
    0 Votes
    3 Posts
    72 Views
    W

    @Danp Thanks. My fault, I didn't notice the 2nd page of templates where it was.

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • xo-server-auth-saml

    2
    0 Votes
    2 Posts
    55 Views
    olivierlambertO

    Hi,

    You should use the UI to config the plugin, but I suppose you are asking to pass extra parameters that aren't displayed/existing?

  • Change the network device for remotes throws "mount.nfs: Connection timed out"

    Solved
    5
    0 Votes
    5 Posts
    88 Views
    R

    @olivierlambert Oh my... I totally forgot to change the network interface on XO after the change. That was my mistake. Sorry.

    But thanks a million for pointing it out.

  • Tag management for Storage not able to choose from existing tags

    3
    0 Votes
    3 Posts
    88 Views
    MathieuRAM

    Hi
    Indeed. We will see how we can fix this bug.
    Thanks

  • Intermediate cert xen orchestra

    Solved
    4
    0 Votes
    4 Posts
    104 Views
    A

    I bundled the cert and it is working as expected now.

    Thanks!

  • Sum of actuall provisioned SR space compared to used space

    2
    0 Votes
    2 Posts
    64 Views
    ForzaF

    I haven't seen it in XOA, but in XCP-ng Center, this information is available:

    f7ec1a2b-1d23-4258-93e4-a29f5ba00a48-image.png

  • Commit Number Not Updating?

    5
    0 Votes
    5 Posts
    88 Views
    A

    @Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.

  • "Xenserver 8" with PVS Accelerator showing Full Orphan VDIs

    Solved
    7
    0 Votes
    7 Posts
    308 Views
    M

    Hi @infecticide, the fix for this issue has been been merged and will be available in the next release (5.100.1)

  • xoa not show host patch?

    1
    0 Votes
    1 Posts
    44 Views
    No one has replied
  • Storage Bar Graph Misinformation

    Unsolved
    9
    0 Votes
    9 Posts
    249 Views
    T

    I have another weird one. The numeric representative is correct, but the bar graph is unintuitive.

    aa347240-cb22-4cde-acb0-ac741e44151a-image.png

  • Encrypt Server Passwords

    13
    0 Votes
    13 Posts
    818 Views
    J

    @olivierlambert said in Encrypt Server Passwords:

    I'm not saying it's not possible, I'm saying this will be at the huge expense of usability.

    One such software implementation of a KMIP protocol server, which is in software form is an open source fork of HashiCorp Vault. This open source fork is called OpenBao (https://openbao.org/).

  • XOA / XCP-ng NTP?

    4
    0 Votes
    4 Posts
    184 Views
    olivierlambertO

    I think on recent XOA we even switched to systemd-timesyncd. Pinging @thomas-dkmt so he can update the doc to fix it (only the new doc directly! oh and you can ask @julien-f for details if needed, thanks!).

  • Is it possible to do this with VM list filters?

    Solved
    6
    0 Votes
    6 Posts
    88 Views
    J

    @Danp You're right, I missed the question mark on it when I tried it before. With the question mark, it works. Thank you for your help.

  • Logs Partition Full

    59
    0 Votes
    59 Posts
    23k Views
    X

    How can I determine which VM is causing this problem?

    Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830066:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830198:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830311:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830458:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830605:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830712:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830797:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830885:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831006:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831094:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831185:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831260:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831333:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831407:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831478:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831551:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884264:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884519:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884615:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884721:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.923891:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924054:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924207:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924319:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924505:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924675:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924803:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924913:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927026:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927185:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927303:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927436:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927657:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927772:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927903:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927993:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928136:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928255:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928396:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928479:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932786:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932906:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017)
  • Bug?? Tree view XO v6

    Solved
    3
    0 Votes
    3 Posts
    86 Views
    P

    @Danp
    Yes of course You are correct
    I moved it to local storage a few weeks ago
    My bad