Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@DustinB3403 said:
Reboots are kind of critical to know if anything is broken.....
Only in Windows, lol.
-
And since we're using cron to start the job, it's more easily handled there.
Uptime of weeks or months is no good for any system.
Regardless of how awesome it is.
-
@dafyre said:
@DustinB3403 said:
Reboots are kind of critical to know if anything is broken.....
Only in Windows, lol.
Any system that is getting properly patched.
-
Can't seem to get the startup script working with cron. Entered the command:
chmod +x xo-start.shWhat did I miss?
-
@Danp Did you run it with sudo?
-
@Danp said:
Can't seem to get the startup script working with cron. Entered the command:
chmod +x xo-start.shWhat did I miss?
That just makes the script executable.
-
Try it from /etc/rc.local ?
-
@coliver said:
@Danp Did you run it with sudo?
Yes, current octal on the file is 0755 so it would appear that the executable flag is set for everyone.
@DustinB3403 said:
That just makes the script executable.
No kidding?!
I followed your earlier guide, but it isn't working for some reason.
-
@Danp where did you put the xo-start.sh script? It should be in /etc
-
and what is in
/etc/crontab?
And this should be what is in "my" /etc/crontab
-
Everything looks the same to me. <shrug>
Tried running
grep CRON /var/log/syslogbut don't see anything useful. -
Works as expected when I run
cd /etc && ./xo-start.shfrom the command line. -
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.
