It's not a bug so much as a setting you need to change in ansible.cfg because there's very little we can do about it.
See: http://docs.ansible.com/intro_configuration.html#control-path On Wed, Jun 11, 2014 at 4:10 PM, Zaven <[email protected]> wrote: > We have been experiencing this bug consistently for some time. Is there a > ticket to track this, Ansiblers? > > fatal: [ec2-54-xxx-yyy-zz.us-west-2.compute.amazonaws.com] => failed to > transfer file to > /home/ubuntu/.ansible/tmp/ansible-tmp-1402514262.96-23740295147290/source: > > Warning: Permanently added ' > ec2-54-xxx-yyy-zz.us-west-2.compute.amazonaws.com,54.xxx.yyy.zz' (RSA) to > the list of known hosts. > ControlPath > "/Users/zaven/.ansible/cp/ansible-ssh-ec2-54-xxx-yyy-xx.us-west-2.compute.amazonaws.com-22-ubuntu.pIvKZuLKKh2LEqwd" > too long for Unix domain socket > Write failed: Broken pipe > Connection closed > > > > On Wednesday, March 26, 2014 6:45:11 AM UTC-7, Marko Lisica wrote: >> >> Let me add few more thins and answer to my question. >> >> I have run this on three machines. >> >> Ubuntu 13.04 - Ansible 1.5.3 error was: >> >> PUT /tmp/tmpxFGcNu TO /tmp/ansible/ansible-tmp- >>> 1395837087.32-71225947296118/setup >>> >> ec2-xx-xx-xx-xx.compute-1.amazonaws.com | FAILED => failed to transfer >>> file to /tmp/ansible/ansible-tmp- >> >> 1395837087.32-71225947296118/setup: >> >> >>> >> Couldn't read packet: Connection reset by peer >>> >> >> Mac OSX - Ansible 1.4.4: >> >> | FAILED => failed to transfer file to >> /home/admin/.ansible/tmp/ansible-1395838813.75-19289519445016/setup: >>> >>> ControlPath >>> "/Users/marko/.ansible/cp/ansible-ssh-ec2-54-236-227-155.compute-1.amazonaws.com-22-admin.MEUoiLFZkgoecYzU" >>> too long for Unix domain socket >>> subsystem request failed on channel 0 >>> Connection closed >>> >>> >> >> >> And Debian 7.1 - Ansible 1.6: >> >> >> failed to open a SFTP connection (Channel closed.) >>> >> >> I have enable scp_if_ssh = True >> and all went well. >> >> Is it only version issue woth dofferent error messages? >> >> >> On Wednesday, March 26, 2014 1:39:35 PM UTC+1, Marko Lisica wrote: >>> >>> Hi, >>> >>> I've ran to a problem provisioning one host. >>> >>> I have playbook that successfully provisions vagrant box, but running >>> that on amazon host I get this >>> >>> PUT /tmp/tmpxFGcNu TO /tmp/ansible/ansible-tmp- >>>> 1395837087.32-71225947296118/setup >>>> >>> ec2-xx-xx-xx-xx.compute-1.amazonaws.com | FAILED => failed to transfer >>>> file to /tmp/ansible/ansible-tmp-1395837087.32-71225947296118/setup: >>>> >>> >>> >>>> Couldn't read packet: Connection reset by peer >>>> >>> >>> When I check out tmp dir on remote host I see directiories are created >>> by ansible but no file inside. >>> >>> Here is complete output: >>> >>> >>> ansible all -i provision/staging -m setup --private-key=staging-micro.cer >>>> -vvvvvv >>>> <ec2-xx-xx-xx-xx.compute-1.amazonaws.com> ESTABLISH CONNECTION FOR >>>> USER: admin >>>> <ec2-xx-xx-xx-xx.compute-1.amazonaws.com> REMOTE_MODULE setup >>>> <ec2-xx-xx-xx-xx.compute-1.amazonaws.com> EXEC ['ssh', '-C', '-tt', >>>> '-vvv', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', >>>> 'ControlPath=/home/marko/.ansible/cp/ansible-ssh-%h-%p-%r', '-o', >>>> 'Port=22', '-o', 'IdentityFile=staging-micro.cer', '-o', >>>> 'KbdInteractiveAuthentication=no', '-o', 'PreferredAuthentications= >>>> gssapi-with-mic,gssapi-keyex,hostbased,publickey', '-o', >>>> 'PasswordAuthentication=no', '-o', 'User=admin', '-o', 'ConnectTimeout=10', >>>> 'ec2-xx-xx-xx-xx.compute-1.amazonaws.com', "/bin/sh -c 'mkdir -p >>>> /tmp/ansible/ansible-tmp-1395837087.32-71225947296118 && chmod a+rx >>>> /tmp/ansible/ansible-tmp-1395837087.32-71225947296118 && echo >>>> /tmp/ansible/ansible-tmp-1395837087.32-71225947296118'"] >>>> <ec2-xx-xx-xx-xx.compute-1.amazonaws.com> PUT /tmp/tmpxFGcNu TO >>>> /tmp/ansible/ansible-tmp-1395837087.32-71225947296118/setup >>>> ec2-xx-xx-xx-xx.compute-1.amazonaws.com | FAILED => failed to transfer >>>> file to /tmp/ansible/ansible-tmp-1395837087.32-71225947296118/setup: >>>> >>>> Couldn't read packet: Connection reset by peer >>>> >>> >>> -- > 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/19f540a8-68f1-48fa-bfec-bacd96cd9e72%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/19f540a8-68f1-48fa-bfec-bacd96cd9e72%40googlegroups.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%2BnsWgy0u%3DghMfwnDAQ3kU_D%2Bafg4X%3DKv-93r0T0faXDi8LQqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
