| checkers | 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 |
|---|---|---|
| checkers | the debugging page on the wiki seems to be all about debugging boot time issues | 01:46 |
| checkers | it almost seems like upstart hangs when sending the command over dbus | 01:51 |
| JanC | checkers: Ubuntu uses rsyslog, so you might want to compare your job configuration for it with that in Ubuntu | 03:36 |
| checkers | JanC: actually I am using ubuntu's rsyslog and just messed with its internal configuration, trying to figure out what's with the hanging | 03:55 |
| * checkers pokes JanC | 04:44 | |
| checkers | 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 | 04:45 |
| === Md_ is now known as Md | ||
| caleress | hi guys i have an upstart script that works on 12.04 but fails on 10.04 :/ | 12:50 |
| caleress | its just a basic run as different user | 12:51 |
| caleress | exec start-stop-daemon --start -c dev --exec /opt/dev/test.sh | 12:51 |
| caleress | any ideas ? | 12:51 |
| xnox | don't use start-stop-daemon in an upstart script. | 13:01 |
| xnox | well upstart job. | 13:01 |
| caleress | isnt that the recommended way to do it ? | 13:03 |
| caleress | http://upstart.ubuntu.com/cookbook/#changing-user | 13:04 |
| caleress | the cookbook says so | 13:04 |
| caleress | but it looks like my script doesnt even get executed as root | 13:07 |
| caleress | start on startup | 13:08 |
| caleress | exec /opt/dev/test.sh | 13:08 |
| jodh | caleress: presumably the "dev" user exists on your 10.04 system? | 13:08 |
| caleress | stop on runlevel [016] | 13:09 |
| caleress | yes ofc | 13:09 |
| caleress | same script runs on 12.04 | 13:09 |
| jodh | caleress: are you *sure* you want it to start that early? there isn't even a writeable disk at that point. | 13:09 |
| jodh | caleress: 'start on runlevel [2345]' is much more conventional. | 13:09 |
| caleress | ok | 13:09 |
| caleress | i use it to start jboss | 13:09 |
| jodh | caleress: you are starting the job too early then. | 13:09 |
| jodh | caleress: See http://upstart.ubuntu.com/cookbook/#normal-start. | 13:10 |
| caleress | ok i changed it | 13:11 |
| caleress | but the script still doesnt run :p | 13:12 |
| caleress | "sudo start script" and nothing happens | 13:12 |
| jodh | caleress: run "sudo start foo" where foo is /etc/init/foo.conf | 13:13 |
| jodh | caleress: ah - sorry. when you say "nothing" you mean no output or it hangs? | 13:13 |
| caleress | no ouput basically and jboss doesnt start | 13:14 |
| caleress | i tried "sudo start jboss" | 13:14 |
| jodh | 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:15 |
| jodh | caleress: have you looked at the jboss logs? | 13:16 |
| caleress | yeah its like it never started | 13:17 |
| caleress | PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin' | 13:19 |
| caleress | well this look like java is missing from the path | 13:19 |
| caleress | any ideas how to set this ? :) | 13:20 |
| jodh | caleress: everything is in the cookbook :) | 13:21 |
| caleress | haha i can imagine :p | 13:21 |
| jodh | caleress: 'env PATH=/foo:/bar:/baz' | 13:21 |
| caleress | so i set it basically the same as with export | 13:22 |
| caleress | yeah still doesnt start :/ | 13:29 |
| jodh | caleress: have you read and tried the checks in the 3 links above ? | 13:31 |
| caleress | checking env now | 13:32 |
| caleress | procenv: command not found | 13:32 |
| caleress | ridicilious | 13:32 |
| jodh | 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:33 |
| jodh | http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in | 13:34 |
| caleress | i tried set and env, the environment looks ok, its got java and everything | 13:35 |
| caleress | 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:38 |
| caleress | thank you very much | 13:39 |
| === 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 | ||
| FunnyLookinHat | Yo guys - I'm having trouble finding doc on running periodic scripts ( i.e. replace cron ) | 15:57 |
| FunnyLookinHat | The cookbook doesn't seem to be aware that temporal events were built in: https://launchpad.net/upstart/+spec/replace-cron | 15:58 |
| xnox | 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 |
| xnox | FunnyLookinHat: or e.g. $ initctl start mytask | 16:00 |
| FunnyLookinHat | Oh still not done | 16:00 |
| FunnyLookinHat | Ah ok - thanks xnox | 16:01 |
| FunnyLookinHat | It looked like it was done: https://code.launchpad.net/~daniel-sonck/upstart/cron-replacement | 16:01 |
| FunnyLookinHat | My bad | 16:01 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!