[08:39] <jscott1989> hey, I have an upstart script with "exec /home/astro/clyde/run-server.sh" (running that manually results in the server running) - when i run "service clyde start" or "service clyde stop" nothing gets returned and I have to CTRL+C to stop it - and after starting the service the server isn't accessible  - where would I start debugging this?
[08:41] <jodh> jscott1989: is this a system job in /etc/init/ ?
[08:41] <jscott1989> yeah
[08:41] <jodh> jscott1989: most likely cause then is that your server script is expecting variables like "$HOME" to be set - a system job is really designed for running daemons which only require a minimal environment.
[08:42] <jscott1989> http://pastebin.com/cdGQNv1K this is my run-server.sh
[08:42] <jscott1989> i don't think that expects anything?
[08:43] <jodh> jscott1989: I'm afraid I have no idea what your job requires.
[08:43] <jscott1989> is there any way to get upstart to tell me the errors or anything?
[08:43] <jscott1989> as right now when i type "service start clyde" it just hangs
[08:43] <jscott1989> service clyde start*
[08:43] <jodh> jscott1989: if you're running on a modern version of ubuntu, install the procenv package and run that in your normal loging environment and compare the output to when you run it from an upstart job to see the differences.
[08:44] <jodh> jscott1989: cat /var/log/upstart/your-job.log
[08:44] <jscott1989> thanks I'll do that
[08:44] <jodh> jscott1989: see http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in and http://upstart.ubuntu.com/cookbook/#checking-how-a-service-might-react-when-run-as-a-job.
[08:46] <jodh> jscott1989: when you install procenv, you can change your job to run "exec procenv --file=/tmp/procenv.log --exec -- /home/astro/clyde/run-server.sh"
[08:46] <jodh> jscott1989: which will run procenv and have it re-exec itself as your server
[08:47] <jscott1989> I'll try those suggestions, thanks jodh 
[08:59] <jscott1989> hmm, putting procenv in there doesn't even create the log file
[09:02] <jscott1989> okay that was really strange
[09:03] <jscott1989> i created a new file clyde2.conf and put "exec /home/astro/clyde/run-server.sh" and it worked fine :/ must be a permission problem on the first file i guess
[09:05] <jscott1989> hmm… if I remove clyde.conf and rename clyde2.conf to clyde.conf i have the same error… must be something to do with a log file or something??
[09:33] <jodh> jscott1989: does your upstart job specify 'expect'?
[09:33] <jscott1989> no