[00:05] <statim> ion:  holy crap amazing… that is a pretty crazy script! did the trick
[16:18] <amites> Any ideas why I would be able to start a process via upstart - have it show up in ps aux - but be unknown when running stop/restart commands?? Error log showing: unlink() "/var/run/nginx.pid" failed (2: No such file or directory)
[16:20] <jhunt> amites: you may have mis-specified the expect stanza. See http://upstart.ubuntu.com/cookbook/#expect
[16:20] <jhunt> amites: you'll probably find that "status <job>" is incorrect.
[16:21] <amites> jhunt: thank you - reading
[16:23] <amites> I'm fairly new to upstart and don't see anything about how to correct the behavior?
[16:23] <jhunt> amites: http://upstart.ubuntu.com/cookbook/#recovery-on-misspecification-of-expect
[16:24] <amites> As a side note the nginx server (problem process) doesn't connect to a port either -- probably related
[16:26] <amites> jhunt: kill: No such process
[16:28] <amites> I should mention that this behavior is new - it was working until there was a port conflict with apache -- corrected port conflict and been this way since
[16:39] <jhunt> amites: can you show us your .conf file?
[16:39] <amites> moment
[16:40] <amites> http://pastie.org/2934063
[16:41] <jhunt> so, nginx doesn't fork at all?
[16:42] <amites> I have it set to use 9 workers in the config
[16:42] <amites> that's the default init/nginx.conf that came from apt-get install
[16:45] <jhunt> amites: http://wiki.nginx.org/NginxMainModule#daemon suggests it daemonizes, so you'd need "expect daemon", but please work through the expect link section. Also, remove that "respawn" until you are fully convinced you've specified the expect stanza correctly.
=== Md_ is now known as Md