I don't think stop will remove it, probably better to yum remove it. For Openmetrics, check: https://docs.xen-orchestra.com/advanced#openmetrics--prometheus-integration I switched our own production to that, so far it looks promising.

@florent I'll send you a link in DM, hope it helps with something. If not, it wasn't too much of an effort, thanks for your time so far

@anthoineb have we found a possible explanation?

That's weird. Maybe @Team-XAPI-amp-Network could tell you the commands to check what's recorded in XAPI to see if it's a problem at XAPI or XO doing things weirdly.

@Mang0Musztarda said in Xen Orchestra OpenMetrics Plugin - Grafana Dashboard: @MajorP93 hi, how can i scrape openmetrics endpoint? i set up openmetrics plugin prometheus secret, enabled it, and ten tried to use curl like that: curl -H "Authorization: Bearer abc123" http://localhost:9004 but response i got was {"error":"Query authentication does not match server setting"} what am i doing wrong? Hey! I scrape it like so: root@prometheus01:~# cat /etc/prometheus/scrape_configs/xen-orchestra-openmetrics.yml scrape_configs: - job_name: xen-orchestra honor_labels: true scrape_interval: 30s scrape_timeout: 20s scheme: https tls_config: insecure_skip_verify: true bearer_token_file: /etc/prometheus/bearer.token metrics_path: /openmetrics/metrics static_configs: - targets: - xen-orchestra.domain.local /etc/prometheus/bearer.token file contains the bearer token as configured in openmetrics xen orchestra plugin. best regards

@jsajous26 sorry I misread. I don't know how ti setup this while using veeam

I recreate my ZFS pool. But next time or for other stuck with this kind of issue, I think you should start to rename your ZFS POOL. I think the old ZPOOL name stay in XO configuration shadow settings. To rename a ZFS pool, export it with zpool export [poolname] and then import it with the new name using zpool import [poolname] [newpoolname] And then recreate (sr-create) your STORAGE in XO

@Andrew That's exactly what I wanted to know, thanks! Can you confirm this process is correct: /opt/xensource/libexec/xen-cmdline --set-dom0 "video=efifb:off xen-pciback.hide=(0000:02:00.0)(0000:02:00.1)" In grub.cfg, are we replacing console=vga with console=ttyS0 under the multiboot2 line, or do we only need to simply use: /opt/xensource/libexec/xen-cmdline --set-dom0 "console=ttyS0" Do we need to do the same with --set-xen for the command above?

@ronan-a Thanks

Hi @jacob.becker, We identified the issue last weekend, and we're currently working on a solution. We plan to include a fix in the next XO release.

@olivierlambert Because Andriy did quite a bit of work before this merge, xcp-ng depends on xenserver releasing the package to the clients before we can integrate it into xcp-ng. I'd say we can release the package February at the earliest

@myles3 Hello Myles3. This post is over 20 days old. The issue was since been resolved by support. I dont remember the exact solution off the top of my head with out looking it up.

@Bastien-Nollet many thanks

Hello , we are on it actually , i'm trying to reproduce issue on my side

Yeah, it's not surprising. Ceph S3 implementation is known to be "average" and failure-prone in those cases.

@tsukraw There's no need to uninstall the old version, the upgrade is enough. The feature to disable time sync is also just a convenience shortcut for setting the TimeSyncMode value in HKLM\SYSTEM\CurrentControlSet\Services\xenagent to a DWORD of 0. You can set it manually or through Group Policy if you wish. (In fact, GPO might be a better solution on domain environments)