Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

travisdh1

Where the problem lies is that npm does not appear to store the PID anywhere on its own. Could we had that manually to the cron job? Of course, but that would not be universal by any stretch and we'd be left with a script that only worked with that specific means of starting.

This sounds like one of those "It would be really easy to do with an init/systemd script", that nobody has the time to spend working on currently. (If I did, I'd write one.)

Danp

This appears to work:

 kill $(ps aux | grep "node bin/xo-server" | grep -v grep | cut -d' ' -f8)

scottalanmiller

That is exactly what is needed. If this was the old init style, I know it pretty well. Have made a lot of those. Don't know how it works on Ubuntu 15.10.

Although we'd need to package this all up, but that's not that hard.

We are getting closer and closer to making an RPM here.

scottalanmiller

@Danp said:

This appears to work:

 kill $(ps aux | grep "node bin/xo-server" | grep -v grep | cut -d' ' -f8)

Interesting. Good call.

DustinB3403

@Danp said:

This appears to work:

 kill $(ps aux | grep "node bin/xo-server" | grep -v grep | cut -d' ' -f8)

Confirmed.

DustinB3403

So this script should work.

Going to update my script and test.

DustinB3403

I'm going to modify the update script to reboot immediately when done updating, 2 minutes just feels way to long.

dafyre

Or better yet... now that we know how...

Stop the XO server... do the updates... start the XO Server... no reboot required.

DustinB3403

Reboots are kind of critical to know if anything is broken.....

dafyre

@DustinB3403 said:

Reboots are kind of critical to know if anything is broken.....

Only in Windows, lol.

DustinB3403

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.

scottalanmiller

@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.

http://www.smbitjournal.com/2011/02/why-we-reboot-servers/

Danp

Can't seem to get the startup script working with cron. Entered the command:

chmod +x xo-start.sh

What did I miss?

coliver

@Danp Did you run it with sudo?

DustinB3403

@Danp said:

Can't seem to get the startup script working with cron. Entered the command:
chmod +x xo-start.sh
What did I miss?

That just makes the script executable.

dafyre

Try it from /etc/rc.local ?

Danp

@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.

DustinB3403

@Danp where did you put the xo-start.sh script? It should be in /etc

DustinB3403

and what is in

/etc/crontab

?

And this should be what is in "my" /etc/crontab

Danp

Everything looks the same to me. <shrug>

Tried running grep CRON /var/log/syslog but don't see anything useful.