Sometimes this can happen if the system isn't adding your host file to a host file ansible is looking for, so Ansible tightens down, executes a lock, and anticipates a question about whether you need to confirm adding a new host to your host file.
Try temporarily disabling host key checking to see if this makes it go away, and if it does, we can persue from there. Also be sure you are on Ansible 1.8.1 -- the latest release version -- as well, as we recently made some changes regarding reading more possible host file locations. On Sat, Nov 29, 2014 at 4:50 PM, Mirko Friedenhagen <[email protected] > wrote: > Hello Alex, > > I did run lsof -u $USER | grep ssh | grep TCP and saw number of forks > sockets. You could try to prepend your ssh command with strace to see > what's really going on (maybe you should only provision two or three hosts > at the same time then :-) ). > > Regards > Mirko > -- > Sent from my mobile > On Nov 29, 2014 8:24 PM, "Alex King" <[email protected]> wrote: > >> Indeed. The play is essentially apt update and upgrade. There are about >> 20 hosts being run, and they seem to complete in pairs, with long waits >> between groups completing. >> >> When I ssh to individual servers during the run, sometimes no apt command >> is running on the host when I would expect one to be, since that host >> hasn't completed yet. >> >> Other directives in ansible.cfg are taking effect, but I'm wondering if >> the forks directive is. Is there a way for a-p to dump its configuration, >> so I can see all the settings? >> >> During a run, is there a way to tell how many hosts are being run from ps >> output? Is there a way for a-p to display or log when it starts acting on >> individual hosts within a play? >> >> This all happens over a wan, it would be nice to brew able to get some >> timings/profiling for e.g. logging in, transfer of script, execution time. >> >> Cheers Alex >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/8cb00359-5c0c-4a34-9a08-c4a542985703%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAK8jvqyAYr4g-Kt0EvdQWsFTOgRwC7WavtzJo6wyE-gTo7gpeQ%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAK8jvqyAYr4g-Kt0EvdQWsFTOgRwC7WavtzJo6wyE-gTo7gpeQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgw6iKdRA3fE4ZaqmTi_2kezaEP8NpaCjEQKabQTP6%3DhiA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
