Xen Orchestra - Community Edition - Installing with Yarn

Danp

My memory could be faulty, but I seem to recall XO requiring a newer version of Node than 7.x. I'm currently at 8.11.1 and not having any issues.

Have you tried to follow the troubleshooting steps listed here?

DustinB3403

@danp the issue we had is that they depreciated a version as we were using version "8" and changed it to LTS. Which iirc they depreciated the number and made an older version their LTS.

Here is the GH issue.

bnrstnr

@danp Looks like I'm on 9.4.0 and not having any problems.

And @DustinB3403 is using an even newer version from the looks of that Github issue.

Though I think we already knew 9 was good lol I'm really good at providing useless information

Danp

@dustinb3403 right, but I seem to recall a separate issue where there was a dependency that required a higher node version. <shrug>

black3dynamite

@danp said in Xen Orchestra - Community Edition - Installing with Yarn:

@dustinb3403 right, but I seem to recall a separate issue where there was a dependency that required a higher node version. <shrug>

https://xen-orchestra.com/docs/from_the_sources.html#packages-and-pre-requisites

From the link, it's best to always use LTS version of Node.
Nodejs 8.x is the latest LTS.

noelweston

Thanks for the various replies. I did also try going back to the working snapshot and running the update script with "-n lts" - no different.

I have now tried removing the node_modules directory and rebuilding as in the link from Dan - again, no different.

Given that XO is the only thing on this machine, node must have been installed originally with Xen Orchestra. It could have been updated with regular OS updates, I guess, but Xen Orchestra is working at the snapshot point and only fails when I try to run the updater script.

System reports 7.6, and I was apparently able to change to lts. Running the updater again then - same results. So I'm back at my snapshot now, with XO running but unable to update...

Thanks again.

DustinB3403

@noelweston so the simple answer is export your configuration file from your current Orchestra installation build a new instance on a brand new VM and then import your configuration file.

DustinB3403

XO is designed to be disposalable

noelweston

OK, hadn't really thought of it that way.
I've built a fresh Ubuntu 18.04 VM and reinstalled, and all seems happy enough... just running my backup now to check.

Thanks for all the assistance.

Noel

momurda

I have tried this installer script at least half a dozen times over the last 2 years. Not once has it ever worked.
Today i try again and it doesnt work still.

bnrstnr

@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:

I have tried this installer script at least half a dozen times over the last 2 years. Not once has it ever worked.
Today i try again and it doesnt work still.

On Ubuntu 18.04?

DustinB3403

@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:

I have tried this installer script at least half a dozen times over the last 2 years. Not once has it ever worked.
Today i try again and it doesnt work still.

You're the first person to say that this hasn't worked for them, especially over such a length of time.

What distro are you trying this on?

Danp

@momurda "Doesn't work" isn't sufficient feedback for us to determine why you are having such issues with this script.

Perhaps you could show us the commands you used to perform the installation and the output from the SSH session.

momurda

I typed in the command on the github page. It says it completed successfully, but no xo.
Ill just use the virtual appliance since it works.

scottalanmiller

@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:

I typed in the command on the github page. It says it completed successfully, but no xo.
Ill just use the virtual appliance since it works.

What OS, though?

momurda

3 separate versions of ubuntu and even different minor versions of them. 16, 17 and 18 over the last two years. Never works, theres alwasys some package not found, some configuration not supported, something that keeps it from working, yet the output still says it works.

DustinB3403

@momurda are you using the mini iso by chance?

black3dynamite

@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:

3 separate versions of ubuntu and even different minor versions of them. 16, 17 and 18 over the last two years. Never works, theres alwasys some package not found, some configuration not supported, something that keeps it from working, yet the output still says it works.

For Ubuntu 18.04, are using the new installer or the old version?
If you are using KVM, are you deploying Ubuntu using virt-builder?

Danp

@momurda said in Xen Orchestra - Community Edition - Installing with Yarn:

I typed in the command on the github page. It says it completed successfully, but no xo.

You need to dig deeper to figure out why it isn't working correctly in your environment.

For instance, from an SSH session, you could issue the command sudo systemctrl status xo-server to check and see if the service successfully started and is actvie.

To view the logs, you can enter the command sudo journalctl -u xo-server -f -n 50

momurda

@danp I know how to check error logs. The point is the installer keeps on going after errors are encountered, then says everything is ok when it is done.
Like just now, "no package redis-server available" well that seems pretty important, why not err out there and tell me? Instead it goes through and says "Your xo is now ready, go to ip address and start using it"