=== Cidan is now known as zz_Cidan [15:54] <[diablo]> Good evening #upstart [15:55] <[diablo]> guys we're trying to write an upstart job to call a BASH script.. for RHEL6 [15:55] <[diablo]> we need to be sure that the networking is up, and that the file system is there [15:56] <[diablo]> http://pastie.org/10815230 [15:56] <[diablo]> syntax check works, but it does not run :-/ [15:56] <[diablo]> anyone advise whats up please? === zz_Cidan is now known as Cidan === Cidan is now known as zz_Cidan [19:21] pre-start process: unable to execute: Argument list too long [19:21] What could this error mean? [19:32] this is so odd, no matter what I do upstart is telling me job fails to start due to argument list being too long, yet there is no really long argument list, and it initially stated that for my pre-start stanza, which then I commented out the entire block and now its saying for my script stanza [20:06] CrazyTux[m]: any details? [20:07] chras, it looks like it was an issue with my #limit stack 240 480 line [20:07] I commented it out and it works now [20:07] but now I've one last issue [20:07] I'm trying to chown -R ${USER}:${GROUP} $DIR [20:08] for DIR in a b c [20:08] and this is error'ing out [20:08] inside script stanza [20:08] if I comment out the for loop all is well. [20:08] well its more like for FSDIR in "$A" "$B" "$C" [newline] do [newline] chown -R ${USER}:${GROUP} $FSDIR [newline] done [20:09] "done" seems to be highlighted in vim syntax though so not sure if its reserved or something in upstart [20:21] CrazyTux[m]: i havnt used the limit stuff before, but for your chown prob be useful to echo out your chown to see why its failing [20:21] then you could try running it by hand [20:21] my loop by hand is fine [20:21] whats the actual error when it errors out? [20:22] init: process-name pre-start process (24199) terminated with status 2 [20:23] so whats exiting with an exit of 2 [20:24] but didnt you say that [20:25] that your for FSDIR was in a script, or was it in pre-start ? [20:36] i've tried both [20:45] CrazyTux[m]: something in your pre-start is throwing an exit 2, which is causing your event to fail out [20:45] just need to isolate what that is [20:45] it could be your chown [20:46] tho im not sure what fail case in chown would exit with 2, instead of 1 [20:47] could you pastebin your event? [20:48] sure one moment. [20:50] chras, http://pastebin.com/ZXgEMTr1 [20:52] k sec [20:53] sure [20:54] and that all works without errors with the exception of your chown loop ? [20:54] hm, you said it above [20:54] but its not in the paste [20:55] your do part of your for [20:55] and that DOES throw an exit 2 [20:57] correct [20:57] let me try re adding it [20:57] but [20:57] I literally [20:57] tried 100 variations [20:57] so prob [20:58] just got dd'ed in vim [20:58] lol [20:58] testing now sec. [20:58] other then missing the do [20:58] it looks all sane [20:58] chras, what would cause the limit stack issue? [20:58] chras, that causes it to exit out too [20:59] chras, interesting that worked... [20:59] im not that familar with the limit stuff, i can try it here [20:59] so still error'd out? [20:59] chras, not sure how the slipped throug; however I do know for fact I did try it with a do in a one line form/fashion [20:59] chras, no that was a go [20:59] oh? good? [20:59] yes ty [20:59] fresh eyes [20:59] haha :) [20:59] lemme try limit here, sec [21:00] I literally tried putting it on one line, because typically when I write bash it is one liner's in console [21:00] for x in a b c; do echo x; done [21:00] I did that that haha [21:00] and it didn't like it :P [21:00] Sure. [21:01] Right now I've ulimit set in script block right before exec, would this even take affect or cause any adverse behavior? [21:01] when setup in this manner it seems ok [21:01] but I find it where that limit nofile works but not stack. [21:02] k i actually do get the same error as you with limit [21:03] thats what i do, just ulimit manually inside my script stanza [21:06] oh [21:06] i think. thats bytes [21:06] right, limit stack works for me, when i use it with bytes [21:07] with limit stack 240 240 , i got the same too many arguments error [21:07] with limit stack 8192 8192 i got a segv as expeted, and then i did 8k (8388608) and it worked fine [21:09] hmmmm [21:09] so its looking for limit stack 240k / [21:10] yup [21:10] worked here. [21:10] nice. [21:10] chras, thank you for your kind help. [21:10] hey no worries [21:10] chras, next time your in SoCal let me know, I'll buy you a few beers! [21:22] chras, interesting [21:22] chars, so 240k works on several systems but I've got one where it tells me... [21:22] [1730361.753244] init: /etc/init/freeswitch.conf:54: Illegal limit, expected 'unlimited' or integer [21:23] so I converted it to straight integers. [21:23] but still no cigar, very weird. [21:23] 1.12.1 upstart version [21:23] vs 1.11 [21:23] weird... [21:23] 1.11 works [21:24] but either way, no worries thanks for your help! [21:24] I can take it from here :P [21:29] chras, ok so yea I know Im not crazy lol, so beyond that stack issue between the two versions my for loop is again broken [21:30] i use 1.11 [21:31] when i said 8k, i meant i did limit stack 8388608 8388608 [21:31] Yea .1.12.1 is the "more" problematic one [21:31] chras, oh really? I did 240k [21:31] and it worked [21:31] i didnt try that, but seems reasonable [21:33] Yea [21:35] compiling latest stable.. will see what happens [21:35] on a dev box [21:41] yea no cigar, still does not like the for loop it seems on the later versions. [21:41] w/e ill deal with it for now ol [21:41] lol [21:42] #moving onto more important things will come back to this lol