[00:46] meh. [00:47] sudo stop httpd-atkobe -- hangs, because I've started the httpd through start-stop-daemon. [02:02] Actually it hangs no matter what.. [02:05] http://pastebin.com/zKTBDvGZ [02:06] I’m almost the forking behavior of that main process doesn’t match “expect fork”. [02:06] almost sure [02:08] ion: it's an apache server. [02:09] Better to remove the “expect” stanza and make the main process not fork if you’re not 100 % sure of how it behaves. [02:09] s/not fork/not daemonize/ [02:10] https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/438313 [02:11] rather https://bugs.launchpad.net/upstart/+bug/406397 [02:14] ion: unsure. It starts on boot, but cannot be stopped/restarted later on. [02:15] Yeah, that’s a symptom of using incorrect “expect”. [02:16] New upstart user, simple 1-line script, having trouble understanding permissions... trying (just for now) to run as root [02:16] But I get "-su: line 0: exec: /var/node/golf/server.js: cannot execute: Permission denied" [02:17] oh - maybe I need to chmod +x the thing? [02:18] cheers =) [02:22] ion: removed expect, now it doesn't start :-/ [02:22] http://pastebin.com/cpeUsN0a [02:24] added expect daemon, and now upstart *thinks* it starts. [02:24] httpd-atkobe start/running, process 1421 [02:24] i.galic@kobweb /etc/init % ps -cafe | grep 142[1] [02:25] exec "$0" "$@"' [02:25] doesnt look right actually [02:25] hi [02:25] :) [02:29] steffen_b2: I think scott or ion showed me that [02:29] what does that do ? [02:29] /opt/bw/bin/httpd-worker -f /etc/bw/apache/vhosts [02:29] looks like this is what you want to execute [02:30] but i shut up [02:30] i dont know the problem [02:30] and need to get some sleep ;) [02:30] bye === steffen_b2 is now known as steffen_b|afk [02:33] * jMCg too needs to sleep ~_~ [10:59] what can be the reason of getting "unable to execute: Permission denied" when i try to start something with upstart that has 777 as mode ? [11:02] ah, never mind... damn.. need more coffee [14:39] the problem with this: su -s /bin/sh -c 'exec "$0" "$@"' komunalbedarf.at -- /opt/bw/bin/httpd-worker -f /etc/bw/apache/vhosts/komunalbedarf.at/httpd.conf -k start [14:39] Is that you cannot expect fork or expect daemon in upstart... Expect fork expects one, expect daemon two, but the above should result in three or four forks... [14:40] Indeed [14:40] So make it not daemonize. [14:40] Yeah. And tell it to expect daemon or what? [14:40] Drop the “expect” [14:42] ACK. [14:43] Anyway. One more important.. feature, or maybe I'm not aware of that. [14:43] SMF has different modes a service can be in. [14:44] One of them is "maintenance" meaning the start or restart didn't work. [14:44] SMF also comes with a log file for each service, so when a service is in maintenance you can see why that is. [14:46] I would be enormously useful if something like /var/log/upstart/service[:instance].log was automatically created for every service. [14:53] ion: this: http://pastebin.com/QWrtZ4Ei is pretty ugly. [14:54] exec su … [14:54] But at least I can start/stop it now. And scott said the next release will come with the feature I most need [14:56] What I don't quite get is how upstart can follow here - since httpd has a different session ID... oh... [14:58] In this case it works because the processes hang on each other, if I kill the shell, the daemon is a goner too, because it didn't detach, so got nothing todo with the session ID. [15:08] jMCg: such a feature is planned for the near future [15:08] jMCg: if you want the output of the job logged, | logger works. [21:13] I have an /etc/init/munin-node.conf, but "start munin-node" is saying that it's an unknown job [21:14] I'm not sure why this happened in the first place on my system, since I just installed the munin-node package, but I'm wondering if there's a way to get upstart to tell me what all known jobs are [21:16] ah, I found initctl list [21:17] aha, and reload-configuration fixed it === robbiew1 is now known as robbiew [23:35] radix: that shouldn't happen though [23:36] unless you disabled inotify in your kernels or something like that ;) [23:50] or are running in a chroot on natty, but.... yeah.