Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
-
@DustinB3403 said:
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
Try adding the XO installation directory to the PATH statement in that crontab. I'm betting it doesn't know where to run things due to the limited environment the system crontabs run in.
-
@travisdh1 said:
@DustinB3403 said:
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
Try adding the XO installation directory to the PATH statement in that crontab. I'm betting it doesn't know where to run things due to the limited environment the system crontabs run in.
If it needs the PATH, then the command is wrong. It should not know where it is.
-
@scottalanmiller said:
@travisdh1 said:
@DustinB3403 said:
Can anyone else with XO running give the above steps a try and let us know if you're having the same issue?
@Danp sorry I'm just not sure what might be off without more details...
Try adding the XO installation directory to the PATH statement in that crontab. I'm betting it doesn't know where to run things due to the limited environment the system crontabs run in.
If it needs the PATH, then the command is wrong. It should not know where it is.
In my limited experimenting, npm isn't the best implementation of a program. Then we're also dealing with a crontab not running a script/program that we know runs outside of the crontab. At least to me, this just screams that something is missing from PATH at the point it's being run.
-
@Danp said:
Everything looks the same to me. <shrug>
Tried running
grep CRON /var/log/syslogbut don't see anything useful.Did you put it into root's crontab? That's where it needs to be.
-
@scottalanmiller I think so... command was
sudo nano /etc/crontab. -
@Danp said:
@scottalanmiller I think so... command was
sudo nano /etc/crontab.I normally have it in /var/spool/cron/crontabs/root, /etc is normally just settings.
-
@travisdh1 said:
@Danp said:
@scottalanmiller I think so... command was
sudo nano /etc/crontab.I normally have it in /var/spool/cron/crontabs/root, /etc is normally just settings.
Yup, that's where root's crontab is.
-
@Danp said:
@scottalanmiller I think so... command was
sudo nano /etc/crontab.You should "never" edit a crontab like that.
You should do sudo crontab -e
Crontabs are meant to be edited using the crontab tool.
-
Not only does it protect against typos, it protects against putting things in unknown locations
-
Thanks for the pointers. I've made the corrections and now it loaded correctly upon reboot.
-
Any guess which thing that it was?
This is all I have and it works fine....
@reboot cd /opt/xo-server; /usr/local/bin/npm start -
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.
