Xen Orchestra - Community Edition - Installing with Yarn
-
@Sid Yes, the following should do it. I would start with Ubuntu 17.10 though. I'm testing it out right now, about 3/4 of the way done. I'll let you know if there are any snags.
sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash -
Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.
-
@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:
Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.
At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.
Can you provide a link to the github of it and we can look into it. Also post any information in a code block.
-
@dustinb3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:
Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.
At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.
Can you provide a link to the github of it and we can look into it. Also post any information in a code block.
That would be great to add in.
-
@dustinb3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.
Looks like XCP-ng has already reached it's stretch goal for "bundled gluster support."
If their scheduling is accurate you could essentially have XO-SAN built into XCP-ng by the end of this year. -
@bnrstnr said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.
Looks like XCP-ng has already reached it's stretch goal for "bundled gluster support."
If their scheduling is accurate you could essentially have XO-SAN built into XCP-ng by the end of this year.That would not surprise me at all.
-
how can i update to 5.18 ?
the script for updating
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
stays on 5.17 -
Can't you update through the web gui?
-
@hobbit666 said in Xen Orchestra - Community Edition - Installing with Yarn:
Can't you update through the web gui?
Only if you are running the pre-built appliance (XOA). There isn't an updater available in the GUI when built from source.
-
@kju said in Xen Orchestra - Community Edition - Installing with Yarn:
how can i update to 5.18 ?
the script for updating
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
stays on 5.17Not enough details here to know how to help. You could post the output from the console window showing the results from running the above command.
Also, show us the contents of the
/opt
directory. -
@danp ah ok
-
Are you being prompted to identify yourself to git?
git config --global user.email "[email protected]" git config --global user.name "Your Name"
-
@dustinb3403 Good call... I had forgotten about that issue.
-
@dustinb3403 thx, this solved my problem :thumbs_up:
-
@kju said in Xen Orchestra - Community Edition - Installing with Yarn:
@dustinb3403 thx, this solved my problem :thumbs_up:
You're welcome.
-
@kju And welcome to the party.
-
This post is deleted! -
Hope someone can point me in the right direction - I thought it was a good idea to run the update today, and I now have a non-functioning Xen Orchestra instance.
I did get some warnings about node versions, so re-ran the updater with a node version change.
The only error I can identify at the moment is this one in syslog:
xo-server.service: Failed at step CHDIR spawning /usr/local/bin/node: No such file or directory
I've tried re-running the updater with -n stable and -n lts with no joy.
systemctl status xo-server.service shows:
xo-server.service - XO Server Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Mon 2018-06-25 13:11:32 BST; 4min 23s ago Process: 1141 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=200/CHDIR) Main PID: 1141 (code=exited, status=200/CHDIR)
Where do I start?
Thanks
Noel Weston
-
@noelweston Start by providing the output of
journalctl -u xo-server -f -n 50
-
-- Logs begin at Mon 2018-06-25 13:11:23 BST. -- Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:11:31 xoa systemd[1]: Stopped XO Server. Jun 25 13:11:31 xoa systemd[1]: Started XO Server. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:11:31 xoa systemd[1]: Stopped XO Server. Jun 25 13:11:31 xoa systemd[1]: Started XO Server. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:11:32 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:11:32 xoa systemd[1]: Stopped XO Server. Jun 25 13:11:32 xoa systemd[1]: xo-server.service: Start request repeated too quickly. Jun 25 13:11:32 xoa systemd[1]: Failed to start XO Server. Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:23 xoa systemd[1]: Started XO Server. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:23 xoa systemd[1]: Started XO Server. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:23 xoa systemd[1]: Started XO Server. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:23 xoa systemd[1]: Started XO Server. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:23 xoa systemd[1]: Started XO Server. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state. Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 25 13:16:24 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Jun 25 13:16:24 xoa systemd[1]: Stopped XO Server. Jun 25 13:16:24 xoa systemd[1]: xo-server.service: Start request repeated too quickly. Jun 25 13:16:24 xoa systemd[1]: Failed to start XO Server.