[01:46] I'm having problems debugging an issue where upstart hangs indefinitely when I try to start a job (rsyslog). how can I troubleshoot this? [01:46] the debugging page on the wiki seems to be all about debugging boot time issues [01:51] it almost seems like upstart hangs when sending the command over dbus [03:36] checkers: Ubuntu uses rsyslog, so you might want to compare your job configuration for it with that in Ubuntu [03:55] JanC: actually I am using ubuntu's rsyslog and just messed with its internal configuration, trying to figure out what's with the hanging [04:44] * checkers pokes JanC [04:45] sorry, just totally stuck on this issue. I can start rsyslogd by hand using the same user/commandline as the upstart job, and upstart works for all other services just fine... completely weird. it seems to hang even start from a fresh ubuntu configuration now === Md_ is now known as Md [12:50] hi guys i have an upstart script that works on 12.04 but fails on 10.04 :/ [12:51] its just a basic run as different user [12:51] exec start-stop-daemon --start -c dev --exec /opt/dev/test.sh [12:51] any ideas ? [13:01] don't use start-stop-daemon in an upstart script. [13:01] well upstart job. [13:03] isnt that the recommended way to do it ? [13:04] http://upstart.ubuntu.com/cookbook/#changing-user [13:04] the cookbook says so [13:07] but it looks like my script doesnt even get executed as root [13:08] start on startup [13:08] exec /opt/dev/test.sh [13:08] caleress: presumably the "dev" user exists on your 10.04 system? [13:09] stop on runlevel [016] [13:09] yes ofc [13:09] same script runs on 12.04 [13:09] caleress: are you *sure* you want it to start that early? there isn't even a writeable disk at that point. [13:09] caleress: 'start on runlevel [2345]' is much more conventional. [13:09] ok [13:09] i use it to start jboss [13:09] caleress: you are starting the job too early then. [13:10] caleress: See http://upstart.ubuntu.com/cookbook/#normal-start. [13:11] ok i changed it [13:12] but the script still doesnt run :p [13:12] "sudo start script" and nothing happens [13:13] caleress: run "sudo start foo" where foo is /etc/init/foo.conf [13:13] caleress: ah - sorry. when you say "nothing" you mean no output or it hangs? [13:14] no ouput basically and jboss doesnt start [13:14] i tried "sudo start jboss" [13:15] caleress: Look at http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in, http://upstart.ubuntu.com/cookbook/#checking-how-a-service-might-react-when-run-as-a-job, http://upstart.ubuntu.com/cookbook/#determining-why-your-service-fails-to-start [13:16] caleress: have you looked at the jboss logs? [13:17] yeah its like it never started [13:19] PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin' [13:19] well this look like java is missing from the path [13:20] any ideas how to set this ? :) [13:21] caleress: everything is in the cookbook :) [13:21] haha i can imagine :p [13:21] caleress: 'env PATH=/foo:/bar:/baz' [13:22] so i set it basically the same as with export [13:29] yeah still doesnt start :/ [13:31] caleress: have you read and tried the checks in the 3 links above ? [13:32] checking env now [13:32] procenv: command not found [13:32] ridicilious [13:33] caleress: procenv isn't in the 10.04 archive - you should be able to download and build it easily enough though - it's only a single C file. But for speed, just use "set" or "env". [13:34] http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in [13:35] i tried set and env, the environment looks ok, its got java and everything [13:38] think for the time being i'll have to give it up as i have other stuff to do, but thank you very much for your help and for the startup tip ! [13:39] thank you very much === jodh changed the topic of #upstart to: Upstart 1.10 | http://upstart.ubuntu.com/cookbook/ | Post to mailing list if no response here: http://bit.ly/ooeNVv [15:57] Yo guys - I'm having trouble finding doc on running periodic scripts ( i.e. replace cron ) [15:58] The cookbook doesn't seem to be aware that temporal events were built in: https://launchpad.net/upstart/+spec/replace-cron [16:00] FunnyLookinHat: that's just a spec. Temporal events are not released in upstart. Use normal cron/anacron facilities, or make a cron job that does $ initctl emit-event my-event [16:00] FunnyLookinHat: or e.g. $ initctl start mytask [16:00] Oh still not done [16:01] Ah ok - thanks xnox [16:01] It looked like it was done: https://code.launchpad.net/~daniel-sonck/upstart/cron-replacement [16:01] My bad