[15:12] <steffen_b3> hi
[15:13] <steffen_b3> can it be that wait-for-state job in ubuntu is broken ?
[16:27] <jMCg> Hello happy people o/~
[16:28] <jMCg> What do I do when start/stop $jobname causes the thing not to return? Just hanging in there?
[16:28] <jMCg> ctrl+c -> status $jobname says killed (pid)
[16:29] <steffen_b3> try to find whats blocking and kill that 
[16:29] <jMCg> steffen_b3: how do I do that?
[16:29] <steffen_b3> ps -ef 
[16:29] <steffen_b3> check what you can relate to that job
[16:30] <jMCg> i.galic@panic /var/bwlog % ps -ef | grep -w logstas[h]
[16:30] <jMCg> root      7300  3648  0 16:27 pts/0    00:00:00 restart logstash
[16:30] <jMCg> i.galic@panic /var/bwlog % ps -cafe | grep -w 364[8]
[16:30] <jMCg> root      3648  3647 TS   19 16:15 pts/0    00:00:00 -zsh
[16:30] <jMCg> root      7300  3648 TS   19 16:27 pts/0    00:00:00 restart logstash
[16:31] <jMCg> "nothing"
[16:31] <jMCg> Syslog is also rather silent.
[16:32] <steffen_b3> what commands are in logstash upstart job 
[16:32] <steffen_b3> is something of that in ps -ef
[16:33] <steffen_b3> note i'm also just user like you (just to manage expectations) - this is how i get normally back if i did stupid things in my upstart jobs ;)
[16:35] <jMCg> steffen_b3: /etc/init/logstash.conf  http://sprunge.us/BHZX
[16:40] <steffen_b3> no clue then 
[16:44] <jMCg> How do I reinitialize upstart again?
[16:45] <jMCg> wow.
[16:45] <jMCg> The new Ubuntu has a *new* upstart.
[16:55] <steffen_b3> 1.5 i believe