Thanks! I did read your second paragraph but, I was not clear on what are 'normal' prompts.
I will try the timeout feature. Thank you very much for your help and advice. Have a great weekend Bee On Fri, Apr 26, 2013 at 2:51 PM, Jeff Forcier <[email protected]> wrote: > Not sure if you read my 2nd paragraph - your prompt is not a normal > login or sudo prompt, and thus Fabric is not capable of understanding > & responding to it. > > You may want to try setting a command timeout instead - at least that > way your Fabric runs won't sit around forever but should eventually > abort with the timeout. Check the docs for env.command_timeout, it's > new but I think that is the setting. > > On Fri, Apr 26, 2013 at 11:37 AM, Worker Bee <[email protected]> > wrote: > > Hello there! I do appreciate your assistance! > > > > When running against a group of hosts, in parallel mode, if a host is > > encountered that has an expired password, fabric does not abort.. > > > > [dev06 Executing task 'inventory' > > [dev06] sudo: rm /tmp/inventory /tmp/inventory.txt 2>/dev/null || : > > [dev05] sudo: rm /tmp/inventory /tmp/inventory.txt 2>/dev/null || : > > [dev06] out: WARNING: Your password has expired. > > [dev06]: You must change your password now and login again! > > [dev06 out: Changing password for user beeworker > > [dev06] out: Changing password for beeworker. > > [dev05] out: sudo password: > > [dev05] out: > > [dev05] put: inventory -> /tmp/inventory > > [dev05] sudo: /tmp/inventory -o /tmp/inventory.txt && rm -f > /tmp/inventory & > > > > In this case, it never aborts on dev06 even though a prompt is > encountered. > > > > > > I have these variables set in my fabfile > > > > env.skip_bad_hosts = True > > env.abort_on_prompts = True > > > > > > So, I am not sure what I am doing wrong here. Thanks in advance! I > really > > need to get this working as we depend heavily on Fabric for automation! > > > > Bee > > > > > > On Fri, Apr 26, 2013 at 2:23 PM, Jeff Forcier <[email protected]> > wrote: > >> > >> You're not posting an actual example of what you're talking about, > >> which makes it quite hard to actually offer advice :) The feature is > >> working for most folks as far as I've seen. > >> > >> Note that the feature only works for actual prompts Fabric itself > >> handles: sudo and login prompts. Other interactive prompts will still > >> cause Fabric to "hang" waiting for a user, because we cannot reliably > >> detect them. > >> > >> On Fri, Apr 26, 2013 at 11:17 AM, Worker Bee <[email protected]> > >> wrote: > >> > Hi All; > >> > > >> > When I attempt to use --abort-on-prompts and parallel execution, > fabric > >> > still hangs on hosts with expired passwords (waiting for user input). > I > >> > have tried using: > >> > > >> > env.abort_on_prompts = True > >> > > >> > @with_settings(abort_on_prompts=True) > >> > > >> > and via the command line: > >> > > >> > # fab -P --abort-on-prompts > >> > > >> > None of these work; if a host is encountered that prompts for input, > >> > fabric > >> > does not abort. > >> > > >> > I am running fabric 1.6 and paramiko 1.10. > >> > > >> > Has anyone else had this issue? Any ideas would be appreciated! > >> > > >> > Thanks in advance. > >> > Bee > >> > > >> > _______________________________________________ > >> > Fab-user mailing list > >> > [email protected] > >> > https://lists.nongnu.org/mailman/listinfo/fab-user > >> > > >> > >> > >> > >> -- > >> Jeff Forcier > >> Unix sysadmin; Python/Ruby engineer > >> http://bitprophet.org > > > > > > > > -- > Jeff Forcier > Unix sysadmin; Python/Ruby engineer > http://bitprophet.org >
_______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
