Xen Orchestra - Community Edition - Installing with Yarn

Danp

@hobbit666 Try restarting the service with sudo systemctl restart xo-server.service and then post the output from journalctl -u xo-server -f -n 50

hobbit666

root@WYN-XENORCH:~# sudo systemctl restart xo-server.service
root@WYN-XENORCH:~# journalctl -u xo-server -f -n 50
-- Logs begin at Tue 2017-07-18 14:20:01 BST. --
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Started XO Server.
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]: module.js:487
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     throw err;
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     ^
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]: Error: Cannot find module 'bluebird'
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._resolveFilename (module.js:485:15)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._load (module.js:437:25)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module.require (module.js:513:17)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at require (internal/module.js:11:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:12:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module._compile (module.js:569:30)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Object.Module._extensions..js (module.js:580:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Module.load (module.js:503:32)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at tryModuleLoad (module.js:466:12)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module._load (module.js:458:3)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at Function.Module.runMain (module.js:605:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at startup (bootstrap_node.js:158:16)
Jul 20 13:42:40 WYN-XENORCH xo-server[2759]:     at bootstrap_node.js:575:3
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Started XO Server.
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]: module.js:487
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     throw err;
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     ^
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]: Error: Cannot find module 'bluebird'
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._resolveFilename (module.js:485:15)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._load (module.js:437:25)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module.require (module.js:513:17)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at require (internal/module.js:11:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:12:18)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module._compile (module.js:569:30)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Object.Module._extensions..js (module.js:580:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Module.load (module.js:503:32)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at tryModuleLoad (module.js:466:12)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module._load (module.js:458:3)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at Function.Module.runMain (module.js:605:10)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at startup (bootstrap_node.js:158:16)
Jul 20 13:42:40 WYN-XENORCH xo-server[2768]:     at bootstrap_node.js:575:3
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: xo-server.service: Start request repeated too quickly.
Jul 20 13:42:40 WYN-XENORCH systemd[1]: Failed to start XO Server.

Danp

@hobbit666 That's not good. Any errors logged when you installed XO?

hobbit666

@danp No everything seemed to go straight through no issues.

DustinB3403

@hobbit666 What version of Ubuntu was this, 17.10?

DustinB3403

I'm testing currently, give me a bit to get back to this topic once I'm setup

DustinB3403

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

journalctl -u xo-server -f -n 50

@hobbit666 the installation worked just fine for me. I had to do nothing special either. . .

sudo bash and then sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

I'm at a login prompt now.

Danp

@hobbit666 Did you snapshot the VM before installing XO? If so, I would just revert to that point and then try again. Otherwise, I can only suggest that you start over with a new VM.

hobbit666

Have I downloaded the wrong Ubuntu 17.10 Image maybe?

@DustinB3403 @Danp Yeah going to try new fresh install tomorrow.

DustinB3403

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

Have I downloaded the wrong Ubuntu 17.10 Image maybe?

@DustinB3403 @Danp Yeah going to try new fresh install tomorrow.

Image? Just install Ubuntu, and then run the commands.

DustinB3403

@hobbit666 Any update?

scottalanmiller

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

Have I downloaded the wrong Ubuntu 17.10 Image maybe?

There is no right one. 17.10 doesn't release until October. Current is 17.04. Link is here:

https://www.ubuntu.com/download/server

hobbit666

@scottalanmiller that's what I meant 17.04 lol

Going to work on this when I get in. But I know before I left last night there was an error in the log.

hobbit666

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

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

Solved it.

So bloody simple to lol. Watched the install script running and saw an error when connecting to GITHUB with connection refused.

So changed the gateway of the VM to our FTTC connection and all went through so looks like our Firewall was blocking something.

DustinB3403

Carl Holzhauer if you're reading this, this is the "Community" edition, all features that we have access too, are enabled and free for you to use.

XOA is the paid appliance you would get from xen-orchestra.com and is simply, the professionally supported version. It kind of mimics ESXi's licensing model (sadly).

scottalanmiller

Hi Carl..... waves

Danp

Tried updating to the latest version of XO earlier today and ran into a few issues, such as the following warning --

[4/5] Linking dependencies...
warning "[email protected]" has incorrect peer dependency "eslint@>=3.19.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-import@>=2.2.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-node@>=4.2.2".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-promise@>=3.5.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-standard@>=3.0.0".

Reviewing the upgrade process, found the following error during apt-get update --

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Some index files failed to download. They have been ignored, or old ones used instead.

Turns out that the the Yarn public key was expiring soon and they've issued a new key as described here.

Haven't figured out the proper way to resolve this as part of the update script. However, I have tried both of the following with success --

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

This just manually issues the command from the script to add the correct key.

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E074D16EB6FF4DE3

This method works as well by retrieving the key directly from the key server.

Danp

After upgrading to Yarn 1.1.0, the majority of the warnings are gone. For me, all that remains is

[4/5] Linking dependencies...
warning "[email protected]" has unmet peer dependency "prop-types@^15.5.4".
warning The case-insensitive file /opt/xo-web/node_modules/react-bootstrap-4/node_modules shouldn't be copied twice in one bulk copy

and I haven't investigated those yet.

Danp

Updated the script earlier today to deal with a change in the yarn build process.

Sid

@dustinb3403 Hi, I'm new here and I want to try this XO community edition for my laboratory. these are the command i need to run on fresh install ubuntu server 17.04?