| kontinuity | hi all | 05:55 |
|---|---|---|
| kontinuity | can someone please explain to me what run level [23] means? I thought there were 6 | 05:55 |
| kontinuity | I see it in the cookbooks and all examples | 05:56 |
| pulz | whats the best way to find out why upstart report wrong status for my service (it says running but it has crashed) having trouble finding proper doc on this subject | 12:14 |
| pulz | im assuimg this is beacuse the process crashes before upstart gets a pid to track, but is there any workaround ? | 12:18 |
| yatesy | kontinuity: to answer your earlier question, i think it refers to level 2 OR 3 (rather than 23 which as you say doesn't exist) | 13:58 |
| kontinuity | yatesy: either 2 or 3 makes sense instead of 23 but what does 2 or 3 mean? when will it execute? | 13:59 |
| yatesy | kontinuity: if you have "start on runlevel [23]" then the job will be started when the system is in runlevel 2 OR 3 | 15:00 |
| yatesy | kontinuity: see http://upstart.ubuntu.com/cookbook/#runlevels | 15:01 |
| kontinuity | yatesy: thanks! | 15:10 |
| SpamapS | pulz: are you using 'expect fork' ? | 17:29 |
| SpamapS | pulz: it is very problematic if the process does not fork the way upstart expects it to | 17:30 |
| SpamapS | pulz: if status shows a pid that does not exist, then its possible that your process needs to use 'expect daemon', or perhaps shouldn't even use expect anything | 17:31 |
| pulz | SpamapS: im using expect fork, and im not getting an pid at startup either | 19:05 |
| pulz | so it dies to fast | 19:05 |
| pulz | expect daemon yields the same results | 19:33 |
| JanC | if you can run it without forking, that simplifies things | 19:40 |
| pulz | JanC: what are you thinking about ? | 19:46 |
| JanC | pulz: some applications have an option to not run in the background (so no fork), which might make it easier to debug | 19:49 |
| pulz | JanC: im telling it to daemonize | 19:50 |
| pulz | so im open for tips for how to debug it | 19:51 |
| JanC | try not to daemonize it | 19:51 |
| JanC | and remove any expect fork/daemon stanzas | 19:51 |
| pulz | that helped | 19:52 |
| pulz | now it gave me a pid | 19:52 |
| pulz | atleast | 19:52 |
| pulz | and its giving me the correct info | 19:52 |
| JanC | maybe using start-stop-daemon as a helper | 19:53 |
| JanC | but indeed, it should not lose track of the correct PID when doing that | 19:53 |
| pulz | hmm should it still use expect daemon ? | 19:55 |
| JanC | if it doesn't fork: no | 19:56 |
| JanC | expect daemon = expect double fork IIRC | 19:56 |
| pulz | ah | 19:56 |
| pulz | whats the best way to double check it ? | 19:57 |
| pulz | when using start-stop-daemon as helper and deamon values to the app seems to be working, but is it the correct way to work | 19:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!