• xoa kernel update crash the VM ! linux-image-6.1.0-55

    Management
    3
    1 Votes
    3 Posts
    19 Views
    P
    @probain same, fsck on boot disk was clean. but backups were making the XOA crashing in loop... we had to search the culprit, and the kernel update it was... [image: image.jpeg] .56 is releasing on some xo proxies
  • 9 Votes
    59 Posts
    18k Views
    B
    that horizontal scroll bar was also enabled
  • Full backup failure when upgrading XOce

    Unsolved Backup
    10
    0 Votes
    10 Posts
    170 Views
    P
    @florent { "data": { "mode": "full", "reportWhen": "failure" }, "id": "1794881400002", "jobId": "0ffa03e5-e750-43ad-b66c-0495405fe068", "jobName": "BCK_Running", "message": "backup", "scheduleId": "0c8bba34-e5f1-4f58-9c38-11b514358383", "start": 1794881400002, "status": "interrupted", "tasks": [ { "id": "0mwk21luf-5zyntw173ie", "start": 1794881402583, "status": "success", "tasks": [ { "id": "0mwk21mr0-y3gazw087kf", "start": 1794881403757, "status": "success", "end": 1794881405281, "result": "459e3a05-f508-e85d-5cc4-387155dc304b", "message": "snapshot" }, { "id": "0mwk21nyt-imr121bpgle", "start": 1794881405333, "status": "success", "tasks": [ { "id": "0mwk21nzt-bqf4lzdvlkt", "start": 1794881405369, "status": "success", "end": 1794881441678, "result": { "size": 3268086272 }, "message": "transfer", "data": { "progress": 0 } } ], "end": 1794881441822, "message": "export", "data": { "id": "0927f4dc-4476-4ac3-959a-bc37e85956df", "type": "remote", "isFull": true } }, { "id": "0mwk22gs1-zazmiofst3r", "start": 1794881442673, "status": "success", "tasks": [ { "id": "0mwk22h6r-uo87g3emm6", "start": 1794881443203, "status": "success", "end": 1794881499852, "result": { "size": 3268086272, "id": "8d6704b6-e005-f300-47e7-be2e9ea21a5c", "liveMounts": [] }, "message": "transfer", "data": { "progress": 100 } }, { "id": "0mwk23owd-9ik1ccu4ln", "start": 1794881499853, "status": "success", "end": 1794881504936, "message": "vmstart" } ], "end": 1794881507491, "message": "health check", "data": { "progress": 0 } }, { "id": "0mwk23ut6-ah9rc68q15o", "start": 1794881507514, "status": "success", "end": 1794881507850, "result": { "removedFiles": [], "changedFiles": [], "merge": false, "size": 0 }, "message": "clean-vm" } ], "end": 1794881507852, "message": "backup VM", "data": { "id": "a6cc5035-c18c-8f35-e197-b7e55c9cab8a", "type": "VM", "name_label": "1-pihole", "progress": 0 } }, { "id": "0mwk23v2t-gatlyfjkc7l", "start": 1794881507861, "status": "pending", "tasks": [ { "id": "0mwk23v9q-d160t2rhy9k", "start": 1794881508110, "status": "success", "end": 1794881510136, "result": "e3625624-81ba-5913-4e69-cca7f5bb5016", "message": "snapshot" }, { "id": "0mwk23wx8-x8bm3je4ztt", "start": 1794881510252, "status": "success", "tasks": [ { "id": "0mwk23wyy-cfs4vlwf58q", "start": 1794881510315, "status": "success", "end": 1794881836648, "result": { "size": 31518195712 }, "message": "transfer", "data": { "progress": 0 } } ], "end": 1794881836755, "message": "export", "data": { "id": "0927f4dc-4476-4ac3-959a-bc37e85956df", "type": "remote", "isFull": true } }, { "id": "0mwk2axif-lzd7nijq25i", "start": 1794881837607, "status": "pending", "tasks": [ { "id": "0mwk2ayix-bhm2oqxo1zc", "start": 1794881838922, "status": "pending", "message": "transfer", "data": { "progress": 62 } } ], "message": "health check", "data": { "progress": 0 } } ], "message": "backup VM", "data": { "id": "8b921e1c-5cb2-a3d8-6c13-eb9dcf73f993", "type": "VM", "name_label": "1-Romy", "progress": 0 } } ], "infos": [ { "data": { "vms": [ "a6cc5035-c18c-8f35-e197-b7e55c9cab8a", "8b921e1c-5cb2-a3d8-6c13-eb9dcf73f993", "235d2a6a-89a5-845d-9310-11938e65a95e", "6f5c2553-2150-bd34-db9e-2830820247f1" ] }, "message": "vms" } ] } Here are the 3 VMs that ran, the fourth one is XOce that did not run. [image: image.jpeg] I'l test the backups to see if they are OK, then I'l try with node 24.
  • 0 Votes
    18 Posts
    806 Views
    acebmxerA
    @poddingue added my info as well.
  • MFA for console access

    Unsolved XCP-ng
    2
    0 Votes
    2 Posts
    129 Views
    poddingueP
    I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
  • 7 Votes
    327 Posts
    226k Views
    poddingueP
    @coolsport00 not in XO 6 yet as far as I can tell. For now it's still done from XO 5: Home > Pools, open the pool, then "Add Hosts" at the top right, once the new host has been added as a server (docs). I believe the XO team already has it on their list for the pool dashboard. If you want to push it, there's a close Feeder request you could vote on, which also asks for a proper add-host form: https://feedback.vates.tech/posts/75/permit-to-add-host-to-pool-with-a-real-form @Greg_E thanks for the screenshot. It looks like the parent task keeps reporting 1% once the metadata backups underneath it are done. I think that one is known too, but I'll let the XO team confirm.
  • 0 Votes
    5 Posts
    280 Views
    poddingueP
    If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
  • Backup failures after VHD to QCOW2 conversion

    Unsolved Backup
    8
    0 Votes
    8 Posts
    422 Views
    poddingueP
    Thanks for sharing those. I can't read SMlogs well enough to add anything useful myself, so this is really one for @Team-Storage. One thing though: if I read the link right, it expires on 23 November, so it would be good if someone grabbed the files before then.
  • New Tools 9.2.445 update failure

    Unsolved Management
    3
    1
    0 Votes
    3 Posts
    98 Views
    olivierlambertO
    Pinging @dinhngtu
  • XCP-ng Windows PV tools announcements

    Moved News
    120
    0 Votes
    120 Posts
    66k Views
    F
    Running into an installation issue with this new version. I created a separate thread here about the issue: https://xcp-ng.org/forum/topic/12580/new-tools-9.2.445-update-failure
  • 1 Votes
    4 Posts
    212 Views
    Bastien NolletB
    Here's the fix, which should be merged in the following days/weeks, and should be in the next XO release: https://github.com/vatesfr/xen-orchestra/pull/10809
  • New 9.2.445 XCP Windows tools Roll Back

    Management
    3
    0 Votes
    3 Posts
    201 Views
    B
    Looks like the tools installation had an issue with Windows Update packages, the windows event log started throwing error relating to the cryptsvc service and C:\Windows\System32\catroot2 at the time I ran XenClean before trying to install 9.2445. Rebuilding Catroot resolved the issue and tools installed fine. net stop cryptsvc ren C:\Windows\System32\catroot2 catroot2.old net start cryptsvc Reboot Appears to be isolated to this single VM
  • 0 Votes
    12 Posts
    6k Views
    olivierlambertO
    Hi @odmsys It's on the roadmap and it won't wait for SMAPIv3. I truly hope we can bring something in a matter of few months, at least to have it to test
  • Native Ceph RBD SM driver for XCP-ng

    Development
    43
    3 Votes
    43 Posts
    12k Views
    A
    @dicode-nl Thank you for the code. I'm in testing now with ceph 20.2.5 and so far I haven't had any issues.
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    802
    1 Votes
    802 Posts
    1m Views
    R
    Thank you, @stormi , I'm happy to know that xcp-ng.repo is not touched. These three hosts haven't been rebuilt or restored recently, no hosts have been added, and I did have to make the above modification on each one of them to get them to work. I suppose it's possible I missed the step to remove "mirrors.xcp-ng.org" from xcp-ng.repo during the initial pool build about a year ago and it's just somehow been working with our outbound Internet proxy. In any event, having "mirrors.xcp-ng.org" in our xcp-ng.repo file has definitely caused us problems in the past with our proxy setup. TGIF/DMCV!
  • Disk import not happens

    Unsolved Management
    5
    0 Votes
    5 Posts
    233 Views
    Tristis OrisT
    error via reverse proxy. Uncaught Error: Body is not a JSON, original message is : <html> <title>500 Internal Server Error</title> <style>html{color-scheme:light dark;}</style> </head> <body> <center><h1>500 Internal Server Error</h1></center> <hr><center>Angie</center> </body> </html> pr index.js:2564 me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 be index.js:4029 be index.js:4029 dr index.js:2531 importDisks index.js:2575 Lodash 2 importDisks index.js:2574 e index.js:113 P index.js:22 i index.js:22 R index.js:22 R index.js:22 import index.js:121 t factory.js:307 o factory.js:331 e action-button.js:93 m action-button.js:10 i action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 v action-button.js:140 componentDidMount action-button.js:147 React 14 componentWillUnmount factory.js:125 f factory.js:31 _dispatch factory.js:158 t factory.js:322 promise callback*t factory.js:313 o factory.js:331 value index.js:206 promise callback*value index.js:174 React 5
  • Booting Homeassistant (HAOS) Image breaks VM

    Unsolved Compute
    5
    0 Votes
    5 Posts
    412 Views
    C
    @IgorGlock What do you mean by "okay"? Backing up the VM with Commvault or...?
  • Rolling pool update

    Xen Orchestra
    13
    0 Votes
    13 Posts
    642 Views
    J
    @tjkreidl said: @john.c Note that a two-host pool running HA can run into the split-brain issue if one of the hosts fails; it's highly recommended to have at least three hosts in an HA pool (or look into HA-Lizard if running a pool with two hosts and HA). Right but also considering the in development Twinstor for when it goes stable and in production!
  • 4 Votes
    3 Posts
    982 Views
    J
    @vmpr Popping it behind an instance of BunkerWeb (https://www.bunkerweb.io/) or similar, with Xen Orchestra on a new IP address would help. As BunkerWeb is what’s known as a Web Application Firewall. It will help to protect your instance of Xen Orchestra, especially if you change the IP address of the appliance, and only give that friend the one that goes through BunkerWeb. As always don’t expose Xen Orchestra to the Internet, but if it’s absolutely necessary always use something like BunkerWeb (with BunkerNET) and only provide the BunkerWeb based IP address! Also run a check on all of your hosts and may be best to roll them a fresh (in case there’s an Advanced Persistent Threat). As well as a fresh instance of Xen Orchestra, and maybe encourage your friend while also doing yourself to start using hardware security keys, preferably ones that support biometrics and PINs. Alternatively other secure enclaves with cryptographic credentials held there. Additionally opt into the new encrypted datastore for Xen Orchestra on the new fresh Xen Orchestra and XCP-ng. Also make sure it’s completely up to date! Also if the hosts support it ensure that Intel TME or similar is enabled on the fresh installs of XCP-ng. Finally rotate all passwords associated with that system, including your Vates account password, especially if it’s linked to the Xen Orchestra instance hit.
  • 0 Votes
    20 Posts
    2k Views
    nathanael-hN
    @jr-m4 I did not took time to test Podman yet. But we expect this to work. You'd have to expose a socket, like the docker daemon does. Probably systemctl enable --now podman.socket would be enough. More in this page https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/using-the-container-tools-api and this one https://docs.podman.io/en/latest/markdown/podman-system-service.1.html