@techjeff Correct, I am an active user of the forums

@peo said in Backups started to fail again (overall status: failure, but both snapshot and transfer returns success):

@olivierlambert Thanks, will update every machine and XO involved in the backup process, and possibly even the individual machines that fails. First failure on vm-cleanup was 15 July, that's a few days before I patched the hosts (as a part of troubleshooting and preventing further failures). Still these backups will (probably) be fully restorable (as I have tested out with the always-failing Docker vm)

So you patch your host, but not the administrative tools for the hosts?

Seems a little cart before the horse there, no?

@HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

I didn't mean that I want to go to 6.0 now, but when 6.0 becomes "Stable LTS", get that automatically with your script ?

Assuming there aren't any major changes to the upgrading processing using the existing script should work, but that has to be determined once a general release is created.

@HH Just follow the documented steps in the updater github, since 6.0 hasn't been fully released yet there isn't anything special to it.

@HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

udo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -n stable

correct, this will put you on the "stable" release of XO from Source.

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash

Would work for a properly running instance, but you may have changed at some point to "next-release"

@HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

@DustinB said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

journalctl -u xo-server -f -n 50

Weisst du was das bedeutet:
Jul 22 08:45:47 as-xoce xo-server[887]: at process.callbackTrampoline (node:internal/async_hooks:130:17)
Jul 22 08:45:47 as-xoce xo-server[887]: }
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-ldap
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-github
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-google
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-saml
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-oidc
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register netbox
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-icinga2
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register test-plugin
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-nagios
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-slack
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register backup-reports
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register load-balancer
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-email
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register audit
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register perf-alert
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register transport-xmpp
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register web-hooks
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.749Z xo:plugin INFO successfully register usage-report
Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.861Z xo:plugin INFO successfully register sdn-controller
Jul 22 09:03:45 as-xoce xo-server[887]: (node:887) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
Jul 22 09:03:45 as-xoce xo-server[887]: (Use node --trace-deprecation ... to show where the warning was created)
Jul 22 09:03:45 as-xoce xo-server[887]: 2025-07-22T09:03:45.700Z xo:xo-server WARN Node warning {
Jul 22 09:03:45 as-xoce xo-server[887]: error: DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
Jul 22 09:03:45 as-xoce xo-server[887]: at IncomingMessage.flash (/opt/xen-orchestra/node_modules/connect-flash/lib/flash.js:67:16)
Jul 22 09:03:45 as-xoce xo-server[887]: at file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:322:11
Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
Jul 22 09:03:45 as-xoce xo-server[887]: at Xo._handleHttpRequest (file:///opt/xen-orchestra/packages/xo-server/src/xo.mjs:173:7)
Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
Jul 22 09:03:45 as-xoce xo-server[887]: at initialize (/opt/xen-orchestra/node_modules/passport/lib/middleware/initialize.js:98:5)
Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
Jul 22 09:03:45 as-xoce xo-server[887]: at urlencodedParser (/opt/xen-orchestra/node_modules/body-parser/lib/types/urlencoded.js:94:7)
Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13) {
Jul 22 09:03:45 as-xoce xo-server[887]: code: 'DEP0044'
Jul 22 09:03:45 as-xoce xo-server[887]: }
Jul 22 09:03:45 as-xoce xo-server[887]: }

Nothing appears to be wrong here

@HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

Current commit a9789ba6301f60ab839b2329bcd95c15d1989649 2025-07-22 10:09:54 +0200
Switching to branch 'next-release'...
No stash entries found.

I'm assuming you're using the "Stable" branch, but maybe not. Take a look at my github on how to check what channel to be on.

@HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

Is this really due to my server?

Possibly....

@HH It might be worth checking the logs, journalctl -u xo-server -f -n 50

If nothing stands out still, you can always export your configuration file for XOCE, build a new installation on a new VM and import the configuration.

For what it's worth, I don't see anything standing out with what has been provided.

For what it's worth, I just updated my XOCE installation and everything is working without issue.

Try updating with sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

@HH I am Jarli01

@HH My scripts by default pull the current version that is available from the Vates repo.

The issue you're encountering should've been reported to my repo first

The likely issue is that that webserver version hasn't been updated and that you are "current". Give the update a try again in another day or two, nothing is broken.

@Danp said in Advanced VM settings Logs:

Hi Dustin,

Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it.

Dan

Perfect, thanks!

Under a given VM, the Advanced tab has a ton of options, without getting into the "why do I have users who can make changes here" because believe me I wouldn't if I had the option and I likely can address this with permission changes.

Is there a log of changes and by whom, IE "Bob enabled "Prevent Migration" on uuid=<VM-UUID>"

I personally want the ability to see these types of changes so I can go and ask.

Is this a thing?

@Danp said in XO Community edition backups dont work as of build 6b263:

@wf said in XO Community edition backups dont work as of build 6b263:

How do I roll back to a previous commit?

git checkout <target commit>

Then rebuild with yarn; yarn build

@marcoi use the above to roll back to a specific commit.

@bishoptf I would be very interested to read the T&C's on that agreement, cause it's sus AF.

@bishoptf said in XO and XCP-ng pricing:

@DustinB Nope that was a fully supported license including support...I could open tickets and maybe the response would have been slow but it was a fully supported instance.

Were you using version 4 of the software? Like, there is no way VMWare ever sold a license with support for $45/year within the past 15 years....

I've worked with some very large non-profits and their pricing was higher than that for modern versions of ESXi.

@bishoptf said in XO and XCP-ng pricing:

Yup for essentials my pricing was like $45/year, lol.

You were paying $45 a year to use the software.... literally nothing else, you got zero support with that $45 a year...

You can and many people do use XCP-ng and XOCE for $0/year forever and have saved that much money, and have been given access to the community for free, where the developers will respond if they have time.

@bishoptf said in XO and XCP-ng pricing:

Veeam starts to officially support it.

Veeam works inside of the VM as well, if you wanted a toolless backup solution you'd just use Xen Orchestra. . . I don't understand this fundamental lack of understanding that is happening in this topic....

@bishoptf said in XO and XCP-ng pricing:

compile from source it's not a easy path for a lot of folks

You aren't compiling anything, you're downloading an ISO and installing that to hardware, and in the case of XOCE, you're running a single line command on a Ubuntu Server.

All of it comes with community provided support.... provided at zero cost to you, which means you get to reap even more benefit (value).

@JeffBerntsen said in XO and XCP-ng pricing:

@bishoptf Something else to consider is the quality of support you get for what you pay. It's possible, not always possible, but possible, even likely, that you can download and use XCP-ng for free, build XO from source, giving you that for free, and still get better support here in the forums than the paid support you get from VMware (or from Citrix for XenServer for that matter).

Exactly, and on the flip side of that, there is nothing in the lowest tiers of support agreements from Broadcom that offers anything remotely close to an SLA or assurance, they may offer you the bare minimum of saying, "Thumbs up from us" and then tell you to upgrade to the latest version of the software.

Another way to look at this is Vates is saying that they simply won't sell you access to support for less than X dollars year (support, not the software the software is free).

You're saying that you only want to pay less than X dollars per year, and Vates is telling you that it isn't worth the business risk to sell to customers who are so small and is recommending you use the opensource software and community support for free.

If your customers told you that they wanted to pay you only a 10th per year what you're charging them now, would you accept that, or would you recommend that they find an alternative answer?