Xen Orchestra - Community Edition - Installing with Yarn

DustinB3403

@shwetkprabhat I'm sending you a Private message.

geek-baba

@DustinB3403 thanks for helping out and resolving the issue! I cant thank you enough for the time you spent (remote-ing into the machine yesterday and helping all day today via private messages).

For the larger community it looks like if you create a new config.yaml file, XO will register that as config source and any changes after that is not taken into the account, you should use the default config file created by the script (i.e. /opt/xo-server/.xo-server.yaml) to start with or update the installation using the update script and then manually update the default config file.

DustinB3403

@shwetkprabhat glad we were able to sort it out for you.

Texkonc

Yarn? I knew Xen was full of duct tape and bubble gum.

DustinB3403

@Texkonc . . .

Texkonc

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

@Texkonc . . .

Friiiiiday!

DustinB3403

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

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

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Texkonc

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

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

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

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Tomato, Tomato

DustinB3403

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

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

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

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

@Texkonc . . .

Friiiiiday!

The issue is this is XO. . . not Xen. . .

Tomato, Tomato

Not even close.

Tomato / Car tire. . .

hobbit666

So created a new VM installed Ubuntu 16.04 and tried 17.04.
Ran sudo apt-get update and upgrade to update the system.

Then ran

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

but I get nothing on http://serverip or https://serverip.

What steps am I missing

p.s. Also ran the

sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

commands to update it

DustinB3403

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

So created a new VM installed Ubuntu 16.04 and tried 17.04.
Ran sudo apt-get update and upgrade to update the system.

Then ran

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

but I get nothing on http://serverip or https://serverip.

What steps am I missing

p.s. Also ran the

sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

commands to update it

Check the status of the service with systemctl status xo-server.service

hobbit666

@dustinb3403

xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Tue 2017-07-18 14:20:10 BST; 1 day 20h ago
  Process: 1230 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=1/FAILURE)
 Main PID: 1230 (code=exited, status=1/FAILURE)

>Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at Function.Module.runMain (module.js:605:10)
Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at startup (bootstrap_node.js:158:16)
Jul 18 14:20:10 WYN-XENORCH xo-server[1230]:     at bootstrap_node.js:575:3
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Unit entered failed state.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: Stopped XO Server.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: xo-server.service: Start request repeated too quickly.
Jul 18 14:20:10 WYN-XENORCH systemd[1]: Failed to start XO Server.

DustinB3403

@hobbit666 can you format that as code for easier reading ...

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.