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