Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@Danp said:
Got rid of the crontab entry and created the file /etc/systemd/system/xo-server.service containing the following:
# systemd service for XO-Server. [Unit] Description= XO Server After=network-online.target [Service] WorkingDirectory=/opt/xo-server/ ExecStart=/usr/local/bin/node ./bin/xo-server Restart=always SyslogIdentifier=xo-server [Install] WantedBy=multi-user.target
Seems to be working fine with the added bonus that you can now do things like
journalctl -u xo-server -f -n 50
.Nice. I tried to do that one day but I was stuck at getting the process to run from the directory (it was late and I didn't try very hard).
-
This time around the install script ran successfully for me! Once it got towards the end it was left running and seeing as I didn't ssh into a screen session once I exited XO stopped. I added the service script thinking that would get it going as a service after a reboot but no luck, it's not running. What gives?
gett@servervm-001-xo:~$ ll /etc/systemd/system/xo* -rwxrwxrwx 1 root root 262 Feb 23 23:58 /etc/systemd/system/xo-server.service*
I had to log back in, run screen then detach after running
sudo bash cd /opt/xo-server; /usr/local/bin/npm start
-
To enable the service at startup, issue the command
sudo systemctl enable xo-server.service
. You can also check the service status withsudo systemctl status xo-server.service
and manually start the service withsudo systemctl start xo-server.service
HTH, Dan
-
New version of XO is out. Haven't tried updating my VM yet.
@DustinB3403 -- In further testing, I didn't find the line
sudo kill $(ps aux | grep "node bin/xo-server" | grep -v grep | cut -d' ' -f8)
to be reliable (IIRC when the pid was a large number).Would be good to update your script so that it will optionally use
systemctl
. -
It's up and running but I'm seeing that the xoa-updater isn't installed. Any idea why that might be?
gett@servervm-001-xo:~$ xoa-update xoa-update: command not found
-
@larsen161 said:
It's up and running but I'm seeing that the xoa-updater isn't installed. Any idea why that might be?
gett@servervm-001-xo:~$ xoa-update xoa-update: command not found
The open source version doesn't have an updater. You have to update manually by pulling from the Git repo.
-
@Danp said:
Got rid of the crontab entry and created the file /etc/systemd/system/xo-server.service containing the following:
# systemd service for XO-Server. [Unit] Description= XO Server After=network-online.target [Service] WorkingDirectory=/opt/xo-server/ ExecStart=/usr/local/bin/node ./bin/xo-server Restart=always SyslogIdentifier=xo-server [Install] WantedBy=multi-user.target
Seems to be working fine with the added bonus that you can now do things like
journalctl -u xo-server -f -n 50
.This is awesome. I've been playing with slices, and I wanted to do this but I never got the time to figure it out. Thanks again!
-
Why are there three old versions listed here? can I delete these?
-
Those are xs tool iso's you have on your XS system.
Likely for different patches or Windows 10 for example.
You can remove them without any issue, but what harm are they causing?
-
And backups to NFS are still broken.....
-
@johnhooks said:
And backups to NFS are still broken.....
Which issue are you referring too? I have my "working system" but I'm having issues when attempting to connect other XS systems to my NFS server.
-
@DustinB3403 said:
@johnhooks said:
And backups to NFS are still broken.....
Which issue are you referring too? I have my "working system" but I'm having issues when attempting to connect other XS systems to my NFS server.
If I add an NFS server in remote store for backups it won't mount. It's not even showing the first slash after the colon. I have to manually mount it through the cli.
I also can't add an NFS VDI SR. It just says unknown error from the peer.
-
What process are you using to add it through the CLI, I wonder if the same thing is happening when I attempt to setup the newer Xo installations that I've tried.
-
@DustinB3403 said:
What process are you using to add it through the CLI, I wonder if the same thing is happening when I attempt to setup the newer Xo installations that I've tried.
Just mounting it normally. I just go to /tmp/xo-server/mounts and do
mount -t nfs server:/volume/path remote-#
Then click attach in the interface and it attaches.
If I unattach the mount and remount it even through the cli, it won't mount in XO.
Weird, that's not true. It mounted again, but then I noticed it was unmounted (I was running a test backup).
-
@johnhooks hrm I believe I've tried to mount the share like this, but was befumbled by the system complaining that it wasn't in fstab.
As for the dismount / remount issue, it likely has something that is using the connection which is why it doesn't reconnect.
-
A reboot likely corrects the issue.
-
rebooted and still the same issue.
There wasn't anything using NFS at the time. I ran a backup, it completed, I unmounted it, and then clicked it again and nothing. Rebooted and still won't connect. But if I mount through cli, it will work again for a short while.
Also still can't add an NFS SR for VDI, same error.
-
I'm assuming you rebooted the XO installation, I wonder if you have to umount it first.
-
@DustinB3403 said:
I'm assuming you rebooted the XO installation, I wonder if you have to umount it first.
ya I'm too tired to mess with it tonight. I'm thinking about trying out ovirt anyway so it might not be worth it to mess with it much more.
-
Why destroy what you have built already? Just standup ovirt on a separate vm.