[15:42] <N3sh108> hello, I am trying to use upstart for my nodejs server but I just get 'stop/waiting'
[15:42] <N3sh108> the upstart script should be correct though
[15:44] <N3sh108> is that a normal behaviour?
[16:14] <JanC> you get stop/waiting but your nodejs server is still running?
[16:17] <JanC> in that case the upstart job config is not correct
[16:18] <N3sh108> JanC: I went through it and fixed some problems. Now I get: start/running, process XXX
[16:18] <N3sh108> but the server doesn't work
[16:20] <N3sh108> any idea JanC?
[16:20] <JanC> is the nodejs server actually running?
[16:21] <N3sh108> nope
[16:22] <JanC> seems like the nodejs server doesn't start then?
[16:22] <JanC> or starts and immediately exits or crashes?
[16:22] <N3sh108> let me check
[16:23] <JanC> (I've never used nodejs, so no idea what might go wrong)
[16:23] <N3sh108> ok
[16:23] <N3sh108> if I run my exec command myself
[16:23] <N3sh108> it works
[16:24] <N3sh108> but now when I either start it manually (start <program>) or when I reboot the machine
[16:25] <N3sh108> I don't get why
[16:26] <N3sh108> arggg
[16:26] <N3sh108> wasting so much time 
[16:28] <JanC> a web search gave me this: https://github.com/cvee/node-upstart  (not sure if it's useful for you?)
[16:30] <JanC> there are some other articles to be found too, which do things somewhat differently
[16:32] <N3sh108> still nothing
[16:32] <N3sh108> fuck this shit
[16:32] <N3sh108> 1 hour wasted for nothing
[16:35] <JanC> BTW: when it works when you run it from the command line, but not from an upstart job, then usually the problem is something in the "environment" that is different (e.g. environment variables, working directory, application expects a tty, etc.)
[16:35] <JanC> also, permissions
[17:48] <N3sh108> thanks, it magically fixed itself :D
[18:54] <JanC> possibly it was still confused by a previous test without rebooting?