Xen Orchestra - Community Edition - Installing with Yarn

DustinB3403

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

Yes, I do have a backup... not that recent, but it will do.

Any idea what went wrong?

No way to know without the logs, did you identify yourself to git as that can cause issues (mostly you won't be able to update).

noelweston

Yes, as above - the first run I got the git "who are you" warning, so I ran the git configs and re-ran the updates.
Which logs do you mean - are there any others I can look at, or do they disappear on a reboot?

DustinB3403

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

Yes, as above - the first run I got the git "who are you" warning, so I ran the git configs and re-ran the updates.
Which logs do you mean - are there any others I can look at, or do they disappear on a reboot?

the journal logs provide the "best" information as to what went wrong. If you have the update logs (what went by on the screen as you updated) that could provide some insight as well.

noelweston

Ah, OK - no, not any more - again, they went in one of the reboots.
I'll restore the backup (figured that one out), take a snapshot and try again.

black3dynamite

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

And next dumb question - how do I restore a Xen Orchestra .xva backup into Xen without Xen Orchestra?

You can import it using XenCenter.
Or via command line.
https://david.pryke.us/2016/02/17/import-xen-vm-from-xva-file-via-cmd-line-or-gui/

noelweston

OK, with a backup restored and snapshotted, I re-did the git config and tried the updater again, and it's failed / borked again.

Relevant lines from the log:

Jun 26 10:26:48 xoa systemd[1]: Stopping XO Server...
Jun 26 10:26:48 xoa xo-server[1013]: Tue, 26 Jun 2018 09:26:48 GMT xo:main SIGTERM caught, closing…
Jun 26 10:26:48 xoa xo-server[1013]: Tue, 26 Jun 2018 09:26:48 GMT xo:main bye :-)
Jun 26 10:26:48 xoa systemd[1]: Stopped XO Server.
Jun 26 10:38:06 xoa systemd[1]: Started XO Server.
Jun 26 10:38:06 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 26 10:38:06 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 26 10:38:06 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 26 10:38:06 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 26 10:38:06 xoa systemd[1]: Stopped XO Server.

Which is the same as yesterday.

I do have the full build process captured - it's nearly 1200 lines, so it didn't seem like a good plan to upload it straight away. There are no errors that I can see, and the only warning is back to node versions:

warning You are using Node "7.6.0" which is not supported and may encounter bugs or unexpected behavior. Yarn supports the following semver range: "^4.8.0 || ^5.7.0 || ^6.2.2 || >=8.0.0"

Any further thoughts?

Thanks for the help, by the way - much appreciated.

Noel

noelweston

Another update - reverted to the snapshot and ran the updater with -n stable, and got a different set of errors but still a non-starting service...

First error shown is
error /opt/xen-orchestra/node_modules/level-party/node_modules/leveldown: Command failed.

Followed by

/home/serverbackup/.node-gyp/10.4.1/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
     __attribute__((deprecated(message))) declarator
                                          ^
leveldown.target.mk:113: recipe for target 'Release/obj.target/leveldown/src/batch.o' failed
make: Leaving directory '/opt/xen-orchestra/node_modules/level-party/node_modules/leveldown/build'
make: *** [Release/obj.target/leveldown/src/batch.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/opt/xen-orchestra/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Linux 4.4.0-128-generic
gyp ERR! command "/usr/local/bin/node" "/opt/xen-orchestra/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /opt/xen-orchestra/node_modules/level-party/node_modules/leveldown

Any further thoughts?

Noel

DustinB3403

Node version 7 is depreciated, v 6 is their LTS and 8 is current (8 wasn't working a while ago)

DustinB3403

@noelweston based on the logs, you have a bad version of node. Downgrade to their LTS release.

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?