Restart the toolstack on each server.

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.

The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.

Click the person icon below the Sign Out option to access the settings for the currently logged in user.

Look under the configuration for the backup-reports plugin, which can be found under Settings > Plugins.

This sounds like the same issue discussed here. If you are using XOA (the prebuilt appliance), then you should either contact support for the fix or wait until the next release (tomorrow?) and then retest using the latest release channel.

@DCT said in Cannot Delete a VM Template through CLI or XE:

xe template-param-clear uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30 param-name=is-a-template

Try this instead --

xe template-param-set is-a-template=false uuid=39bf95ba-1f92-4a54-1c14-d9d800ceca30

Then try to access the VM in XO and disable the Protect from accidental deletion option. Hopefully you will be able to delete it once that's done.

@julien-f Technically, it is possible with post processing as I mentioned above. Here's an example using jq and awk --

 xo-cli --list-objects type=VM-snapshot | jq '.[]."$snapshot_of"' | sort | uniq -c | awk -F " " '{print "{\"uuid\":" $2 ",\"count\":" $1"}"}'| jq ' select( .count > 1)'

Output looks like this --

{
  "uuid": "07604606-e937-5147-2dac-c1b4280df234",
  "count": 2
}
{
  "uuid": "0f11c701-c5e5-b09b-4c5f-00cf38153783",
  "count": 2
}
{
  "uuid": "83139da5-48d5-33f6-79f9-79ea91a7163c",
  "count": 2
}
{
  "uuid": "fb4703e4-bfd6-47b8-3fd1-f1f52f9ed234",
  "count": 2
}
{
  "uuid": "ff8b29e3-4445-5b22-e475-450270f2a7f3",
  "count": 2
}

Note: I am not proficient with these linux utilities so there may be better ways to accomplish this.

There was a recent change that resulted in the launched module being renamed. You need to redo your service so that it loads ./dist/cli.mjs instead of ./bin/xo-server

You're running out of memory. Allocate more memory to the VM. I believe the current build requirement is 3GB.

Click the person icon below the Sign Out option to access the settings for the currently logged in user.

Hi... It appears that you are using XO built from the sources. When did you last update?

You should always reboot the master first. I think your only option is to reboot xcp-ng-03.

IDK. Usually HA requires a minimum of 3 hosts. Hopefully someone else will respond with some ideas for you.

Did you upgrade the pool master first?

You may want to provide some further details about your situation to avoid some confusion, ie --

• What do you mean by cluster?
• What was the exact error message received in XO?
• etc.

Sounds like a rights issue.

How old was your XO install? Have you reviewed this thread?

Check the IP address under Setttings > Servers to make sure it points to the current pool master.

Also would be good to make sure that you don't have another device on the network using the same IP address.

32GB is the absolute minimum for storage space. Try bumping this to something like 50-60GB to see if that helps.

@Chmura There's a pending fix for a problem with the zenbleed patch. You may want to test it out to see if it resolves your rebooting issue. See here for more details.