j4m3s_ | i have an upstart script that doesn't appear to be setting the limit stack size, i have a pre-start script that sets the limits but my startup script throws a warning when the limit isn't set properly | 01:53 |
---|---|---|
SpamapS | j4m3s_: pre-start does not share process space/group w/ the main process | 01:53 |
SpamapS | j4m3s_: you can just put that in script/end script with the main process | 01:53 |
j4m3s_ | SpamapS: http://pastie.org/private/nhapxgtg2qzzxzpjkjptg | 01:56 |
SpamapS | ahh limit stanza | 01:59 |
SpamapS | j4m3s_: http://pastie.org/4751117 | 02:00 |
SpamapS | j4m3s_: forgot to make it private.. but.. that might work | 02:01 |
j4m3s_ | i tried that too | 02:01 |
j4m3s_ | SpamapS: just confirmed still getting the same error | 02:02 |
SpamapS | j4m3s_: what version of upstart is this btw? 1.4 and later will log stdout/stderr to /var/log/upstart/$jobname.log | 02:03 |
SpamapS | j4m3s_: hm, with the numeric value, you need the soft and the hard | 02:03 |
j4m3s_ | 0.9 | 02:03 |
j4m3s_ | SpamapS: i tried changing it to 999999 999999, still getting same warning | 02:05 |
SpamapS | j4m3s_: just to be sure, are you doing a full 'stop' then 'start' or just 'restart' ? | 02:11 |
j4m3s_ | restart | 02:11 |
SpamapS | j4m3s_: ok, stop/start are needed to reload the job file | 02:11 |
j4m3s_ | SpamapS: start freeswitch start: Unknown job: freeswitch | 02:12 |
SpamapS | j4m3s_: check syslog, its probably got a syntax error | 02:15 |
SpamapS | j4m3s_: if you have init-checkconf you can use that too | 02:15 |
j4m3s_ | SpamapS: http://pastie.org/private/knrpjsuz6nl84cojzx4tng | 02:27 |
SpamapS | j4m3s_: thats after you fixed whatever was causing the "unknown job" ? | 02:29 |
SpamapS | j4m3s_: KILL is sent 5 seconds after TERM when you stop a job | 02:29 |
j4m3s_ | i forgot the expect daemon | 02:29 |
j4m3s_ | sorry | 02:29 |
SpamapS | still weird htt it would say KILL | 02:30 |
SpamapS | usually it would just say that it exitted with status 1 or 0 or something | 02:30 |
j4m3s_ | SpamapS: it's still not working, it says it's running but it's not running | 02:33 |
j4m3s_ | SpamapS: it appears that upstart loses it whenever i put the limit stanza with the exec, if i put it in pre-start it tracks it fine and everything starts up fine | 02:49 |
j4m3s_ | SpamapS: the only way it succeeds is if the limit lines are commented out or in pre-start | 02:51 |
j4m3s_ | SpamapS: got it to work ;) | 02:54 |
SpamapS | j4m3s_: perhaps your daemon only forks once, so 'expect fork' is more appropriate? | 03:08 |
SpamapS | j4m3s_: what was the trick? | 03:08 |
tohava | If I want to have shell code run SYNCHRONOUSLY before a service, should I put it in pre-start? | 09:44 |
jodh | tohava: yes, that is guaranteed to be run before that jobs main ('exec' or 'script') stanza. | 09:56 |
tohava | jodh, thanks | 09:57 |
jodh | tohava: this is covered in the Upstart Cookbook here: http://upstart.ubuntu.com/cookbook/#job-lifecycle and is also in upstart-events(7) after all the tables :) | 09:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!