Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
Had to be the way that I originally created the crontab entry with nano. It all started working correctly once I used your method.
-
Has anyone else tried migrating the XO VM between servers using XO? When I tried this, the VM was successfully moved, but it appeared to lock up and I had to force a reboot.
Also, what config (VCPUs / ram) are you using for XO? Currently, I'm running 2 VCPUs and 2 GB ram.
-
@Danp said:
Has anyone else tried migrating the XO VM between servers using XO? When I tried this, the VM was successfully moved, but it appeared to lock up and I had to force a reboot.
Also, what config (VCPUs / ram) are you using for XO? Currently, I'm running 2 VCPUs and 2 GB ram.
I have done this, and noticed it as well. It seems to take a while to actually complete.
My XO server is set up identically.
Edit: Calling @olivier who might be able to better explain the process.
-
@DustinB3403 said:
So this script should work.
Going to update my script and test.
Just updated to 4.13 using your script.
-
Just updated to 4.13 using your script.
Now the CR feature seems to be busted (appears to be doing a full export each time instead of a delta). If anyone is feeling like living on the edge, upgrade your copy of XO and see if you get the same behavior.
P.S. I took a snapshot of XO before updating, so I can always roll back to 4.12
-
Wondering if this issue is due to not rebuilding vhd-util. Rebuilt it, deleting all snapshots, and will then let the job run overnight to see if the deltas are working again.
-
The delta exports for Continuous Replenishment is still not working for me after updating to 4.13.
The snapshots are using a new naming mechanism, and the oldest one isn't being removed when each jobs finishes.
-
Investigating.
-
Can you fetch the last version and try again?
-
I'm glad the update script works for you.
Wasn't to much to put together.
-
@Danp Continuous replication is not using
vhd-utilfrom XO: the merge is done on XenServer side. -
Ok... I'm testing your latest fix now.
-
-
@olivier said:
Can you fetch the last version and try again?
I don't see an update on github what was updated to address the issue?
-
-
@scottalanmiller Can you add forever to this script?
-
Has anyone looked at XOA to see how they implemented logging?
-
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.targetSeems to be working fine with the added bonus that you can now do things like
journalctl -u xo-server -f -n 50. -
@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.targetSeems 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
