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. . . 
- 
 @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 
- 
 @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. . . 
- 
 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 | bashbut 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 -- -fcommands to update it 
- 
 @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 | bashbut 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 -- -fcommands to update it Check the status of the service with systemctl status xo-server.service
- 
 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.
- 
 @hobbit666 can you format that as code for easier reading ... 
- 
 @hobbit666 Try restarting the service with sudo systemctl restart xo-server.serviceand then post the output fromjournalctl -u xo-server -f -n 50
- 
 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.
- 
 @hobbit666 That's not good. Any errors logged when you installed XO? 
- 
 @danp No everything seemed to go straight through no issues. 
- 
 @hobbit666 What version of Ubuntu was this, 17.10? 
- 
 I'm testing currently, give me a bit to get back to this topic once I'm setup 
- 
 @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 bashand thensudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bashI'm at a login prompt now. 
- 
 @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. 
- 
 Have I downloaded the wrong Ubuntu 17.10 Image maybe? @DustinB3403 @Danp Yeah going to try new fresh install tomorrow. 
- 
 @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. 
- 
 @hobbit666 Any update? 
- 
 @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: 
- 
 @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. 



