@stormi

I just realized your icon is from Keen4. I use to play that game when I was much younger.

Thanks again for all your help!

No luck, I've tried building from source, using the script, etc.

Following along with Google Gemini I even managed to get walked into the process of damaging the Xapi to the point of losing access to the server from Xen Orchestra / XCP-ng Center (unfortunately for me it was the Pool Master).

Thankfully I had backups on my NAS and experienced minimal loses through the process of having to reinstall the operating system.

At this point, I'm guessing my pool that dates back to version 8.1 is screwed up in some way beyond human or AI understanding.

I have 2 Servers & 3 NAS units (2 TrueNas Scale) + 1 Synology that all work with the old version of Xen Orchestra but I can't get it to work with anything else. Manually putting the same info in or importing the configuration.

One of the servers was rebuilt today and added back to the pool. Is it possible that reinstalling the OS on the other server could fix everything?

I'm confused because the backups aren't failing from the old Xen Orchestra.

Old:

New:

Any help and / or ideas would be greatly appreciated.

Thanks!

@olivierlambert

Good morning Olivier! I believe the issue is with the Xen Orchestrator Installer Updater script no longer adding all of the required services.

I had to do some finagling last night to get the service to even start and become active. By default there were errors everywhere and it wasn't even pointing to the correct location to access the files, yarn, etc.

I'm going to try compiling the application with the documentation you and the team provided manually. I'm sure that was the issue. I'll report back shortly.

Thank you everyone for taking a look and providing guidance!

This is extremely strange.

Using a new install (not using the config) I created a link to the Remote NFS Server.

The test works and shows the correct amount of data and a read/write speed so I do believe its connecting properly.

Unfortunately when I run the backup job it fails and the log is showing that the connection failed to reach 127.0.0.1 which isn't the correct address or referenced in the configuration. Does anyone have an idea as to why this is happening to a brand new install of xen orchestra?

@Andrew

I tried Debian 11 and it failed during the installation process so I also tried Ubuntu 24.04. It installed successfully but I've received the same error as the one I experienced on Debian 12.

The one things that is really strange is when I export the Xen Orchestra Configuration from my working Ubuntu 18.04 instance into a newly installed instance or Xen Orchestra running on any other version of Linux it adds old remotes at different IP Addresses then what is showing on the working instance of Ubuntu.

It seems that Xen Orchestra is pulling from a database on my pool with incorrect information. Any idea where I can look to find and fix this issue?

I'm out of ideas and the my normal helpers (AI Chatbots seem to be out of them too).

I've been a long time XCP-ng user and have an instance of Xen Orchestra built from sources that's been and still runs on Ubuntu 18. Every time I try to update it or my instance of Xen Orchestra is seems to break. With the holiday weekend here, I decided to give it another try and have once again run out of ideas on how to get this working.

On a fresh install of Debian 12, I am trying to get a backup to my remote (TrueNAS Scale) to accept the backups. From my very old Ubuntu 18, the backup jobs work to both TrueNAS and Synology NAS targets. From the fresh install of Debian I can't get of the remotes working. The error I get is:

backupNg.runJob
{
  "id": "4345ad59-46b6-4e19-9d0d-2bab9b75745a",
  "schedule": "8e6198de-8f95-4768-8e39-d17ce8336fcc"
}
{
  "call": {
    "duration": 34,
    "method": "session.login_with_password",
    "params": "* obfuscated *"
  }
}

Does anyone know what might be causing this? I've tried using the same exact config, no config, making a new dataset on the target. Nothing seems to be working. I'd be grateful for any guidance.

I'm sure I missed some things please let me know if I can provide any additional useful information.

If you know of any useful documentation or youtube videos please send them my way. I'm having a hard time understanding why it works on the older version of Ubuntu vs a more modern OS. I'm sure its increased security somewhere.

Thanks for reading, hope someone has seen this before.

@adzmedia

One thing to try is the boot mode when creating the VM. The template for Windows defaults to UEFI as the boot mode.

I believe if you use BIOS Boot it will allow you to load the ISO.

Hope that helps!!!

@techjeff

Thanks TechJeff!

Yes I have 5 different instances of Xen Orchestra sleeping across my pool. I updated my Primary & Secondary to the latest Xen Orchestra and that's when they stopped working.

Jobs that Xen Orchestra was coordinating for me included booting, backups, and shutdown's.
They all started failing on the new version:

XO-Server 5.83.0 / XO-Web 5.89.0 / Ubuntu 20

The older version running on Ubuntu 18 is XO-Server 5.78.2 / XO-Web 5.80.0 is back to being Primary and works flawlessly so far.

So I'll follow your advice and live on the old version until the issue is resolved.

This is still great software, sometimes it takes these issues to fully appreciate how useful & reliable this application is.

Big Thanks to you super smart people who keep these things working for us!!!

I recently needed to rebuild my instance of Xen Orchestra as part of an upgrade.

For some reason when using the Job that triggers host.start it returns with an invalid parameter error.

Any idea on what I could try to resolve this issue?

Error Details:

host.start
{
  "id": [
    "efa4ef5e...."
  ]
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "code": null,
        "reason": "type",
        "message": "must be string, but is array",
        "property": "@.id"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-common/src/api-errors.js:21:32)
    at Object.call (file:///opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-server/src/xo-mixins/api.mjs:73:18)
    at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202111080620/packages/xo-server/src/xo-mixins/api.mjs:300:19)"
}

@PC_123
For anyone who has this issue in the future.

The command stormi provided did fix the problem on a running machine. Unfortunately it did not persist following a reboot.

The command: iptables -F

Seems to be a better long term solution.

Thanks again to @stormi for isolating the issue.

@stormi

I just realized your icon is from Keen4. I use to play that game when I was much younger.

Thanks again for all your help!