Actually I was wrong. Forgot to tear town my control sockets when swapping server versions.
This is entirely the fault of the ConsoleKit patch, at least for Ubuntu 14.04 https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/ On Thursday, July 2, 2015 at 6:04:54 AM UTC-7, Nathan Brown wrote: > > I ran into this today and played around with different server and client > versions of OpenSSH. My environment consists of servers running Ubuntu > 14.04 and clients running OSX. > > If you run OSX, this problem will go away if you `brew install openssh`. > > On the server I tested these openssh versions: > - Default: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 > - Latest: OpenSSH_6.9p1, OpenSSL 1.0.1f 6 Jan 2014 > > On the client I tested these openssh clients: > - Default: OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 > - Latest (brew): OpenSSH_6.8p1, OpenSSL 1.0.2a 19 Mar 2015 > > > On Monday, June 15, 2015 at 6:22:55 AM UTC-7, Shay Rojansky wrote: >> >> FYI, after working with paramiko for a while I still have issues when >> delegating multiple tasks to the same host, this time with the error "Error >> reading SSH protocol banner". >> >> On Wed, Jun 10, 2015 at 7:31 PM, Shay Rojansky <[email protected]> wrote: >> >>> Great to hear, thanks! >>> >>> On Wed, Jun 10, 2015 at 5:11 PM, Brian Coca <[email protected]> wrote: >>> >>>> the issue is that under normal operation you are hitting different >>>> hosts, when delegating you may have several forks hitting the same >>>> host, which when you factor in control master ssh sockets, it can get >>>> complicated. paramiko avoids this by not having a shared resource. >>>> >>>> in 2.0 we've added some code that does a better job of dealing with >>>> this multiconcurrency when using ssh. >>>> >>>> On Wed, Jun 10, 2015 at 5:39 AM, Shay Rojansky <[email protected]> wrote: >>>> > I can confirm that switching to paramiko appears to solve the problem >>>> in my >>>> > case. This seems like a bit of a shame openssh is the recommended way >>>> to go >>>> > (more features). >>>> > >>>> > On Mon, Jun 8, 2015 at 8:05 PM, Shay Rojansky <[email protected]> wrote: >>>> >> >>>> >> I was just looking into that, is that a reliable workaround? >>>> >> >>>> >> Will try soon and report the results. >>>> >> >>>> >> On Mon, Jun 8, 2015 at 8:02 PM, Brian Coca <[email protected]> >>>> wrote: >>>> >>> >>>> >>> have you tried switching to paramiko as your connection? >>>> >>> >>>> >>> On Mon, Jun 8, 2015 at 1:00 PM, Shay Rojansky <[email protected]> >>>> wrote: >>>> >>> > I have this issue as well: running a play which delegates some >>>> action >>>> >>> > to the >>>> >>> > same host pretty consistently fails with the above error. >>>> Findings are >>>> >>> > exactly the same as below, including the -f 1 behavior. >>>> >>> > >>>> >>> > Any ideas on workarounds? >>>> >>> > >>>> >>> > >>>> >>> > On Friday, May 29, 2015 at 3:36:33 PM UTC+3, Christian Rusa wrote: >>>> >>> >> >>>> >>> >> I can confirm this problem. >>>> >>> >> >>>> >>> >> In my case it is a playbook which creates a configuration file >>>> for the >>>> >>> >> server on the backupserver. >>>> >>> >> >>>> >>> >> If I run this playbook against 1 host it works. >>>> >>> >> If I run it against a group of hosts it fails. >>>> >>> >> If I run it against a group of host using -f 1 as parameter it >>>> works. >>>> >>> >> >>>> >>> >> Error is always the SSH Error: Shared connection to xxxxx closed. >>>> >>> >> >>>> >>> >> Ansible version is 1.9-0.git201503262158~unstable >>>> >>> >> >>>> >>> >> >>>> >>> >> >>>> >>> >> >>>> >>> >> On Monday, May 11, 2015 at 4:47:14 PM UTC+2, Cory Wagner wrote: >>>> >>> >>> >>>> >>> >>> I didn't try with serial, but I have not had an issue when >>>> running >>>> >>> >>> the >>>> >>> >>> same playbook against one or two delegates. >>>> >>> >>> >>>> >>> >>> On Thursday, April 30, 2015 at 9:35:57 AM UTC-5, Brian Coca >>>> wrote: >>>> >>> >>>> >>>> >>> >>>> this sounds like a probably race condition with the per host >>>> forks >>>> >>> >>>> interfering with each other, try setting serial: 1 to confirm. >>>> >>> >>>> >>>> >>> >>>> >>>> >>> >>>> >>>> >>> >>>> -- >>>> >>> >>>> Brian Coca >>>> >>> > >>>> >>> > -- >>>> >>> > 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/e459b939-0395-4d33-acc9-224ee29f0fe9%40googlegroups.com >>>> . >>>> >>> > >>>> >>> > For more options, visit https://groups.google.com/d/optout. >>>> >>> >>>> >>> >>>> >>> >>>> >>> -- >>>> >>> Brian Coca >>>> >>> >>>> >>> -- >>>> >>> You received this message because you are subscribed to a topic in >>>> the >>>> >>> Google Groups "Ansible Project" group. >>>> >>> To unsubscribe from this topic, visit >>>> >>> >>>> https://groups.google.com/d/topic/ansible-project/wMRlm3JtDeo/unsubscribe >>>> . >>>> >>> To unsubscribe from this group and all its topics, 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/CAJ5XC8k9R6zc6B6nRK8pHFdDiFHUJ7_BnR_BhFpv%3D376csn%3Dyw%40mail.gmail.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/CADT4RqAYdqmv633nCYs4%3DMc_feHPz%2B43cs4xtBikPqnRqPNOjA%40mail.gmail.com >>>> . >>>> > >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> >>>> -- >>>> Brian Coca >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Ansible Project" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/ansible-project/wMRlm3JtDeo/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, 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/CAJ5XC8mry7LmNL%2BqY9ioczVYXVaBqDDAsXkk63TESkoPNMd1EQ%40mail.gmail.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/93c66033-6401-475b-bb71-d69ff5b1ad42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
