# unabel to use pipelining on centos 6.6 -\> amazon linux

**URL:** <https://forum.ansible.com/t/unabel-to-use-pipelining-on-centos-6-6-amazon-linux/18754>\
**Category:** Ansible Project\
**Created:** [July 14, 2015, 10:55am UTC](https://forum.ansible.com/t/unabel-to-use-pipelining-on-centos-6-6-amazon-linux/18754 "2015-07-14T10:55:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Leonhardt](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@Alex\_Leonhardt](https://forum.ansible.com/u/Alex_Leonhardt)\
**Post date:** [July 14, 2015, 10:55am UTC](https://forum.ansible.com/t/unabel-to-use-pipelining-on-centos-6-6-amazon-linux/18754/1 "2015-07-14T10:55:26Z")

</div>

Hi guys,

I’ve been trying to use pipelining to make use of ControlPersist etc. - however - ansible is failing to run the play due to asking for the sudo password (?) which I already gave (I verified it works):

$ time ansible-playbook -i ./inventory --user ec2-user -b --ask-become-pass play.yml -vvvv

SUDO password:

PLAY [\*\*\*\*\*\*\*\*\*] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
\<\> ESTABLISH CONNECTION FOR USER: ec2-user  
\<_ **hostnamegoeshere** _\> REMOTE\_MODULE setup  
\<_ **hostnamegoeshere** _\> EXEC ssh -C -vvv -F ssh\_config -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=ec2-user -o ConnectTimeout=10 _ **hostnamegoeshere** _ /bin/sh -c ‘sudo -k && sudo -H -S -p “[sudo via ansible, key=kayjxhclpvxspztayzfyvgilpiefprue] password: " -u root /bin/sh -c '”’“‘echo BECOME-SUCCESS-kayjxhclpvxspztayzfyvgilpiefprue; LANG=en\_US.UTF-8 LC\_CTYPE=en\_US.UTF-8 /usr/bin/python’”‘"’’  
fatal: [_ **hostnamegoeshere** _] =\> ssh connection error while waiting for sudo password prompt

TASK: [debug msg=“hello there”] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
FATAL: no hosts matched or all hosts have already failed – aborting

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
to retry, use: --limit @/home/vagrant/play.retry

_ **hostnamegoeshere** _ : ok=0 changed=0 unreachable=1 failed=0

real 0m16.008s  
user 0m0.191s  
sys 0m0.661s

$ cat ansible.cfg  
[defaults]  
host\_key\_checking = False

[ssh\_connection]  
pipelining = True  
ssh\_args = -F ssh\_config  
#control\_path = %(directory)s/%%h-%%r

$ cat ~/.ssh/config  
Host \*  
ControlMaster auto  
ControlPath /tmp/.ssh-%r@%h:%p  
ControlPersist 60

$ ssh -V  
OpenSSH\_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013

$ rpm -qa | grep openssh  
openssh-clients-5.3p1-104.el6\_6.1.x86\_64  
openssh-server-5.3p1-104.el6\_6.1.x86\_64  
openssh-5.3p1-104.el6\_6.1.x86\_64

$cat play.yml

---

<div class="post-metadata">

**Author:** ![Alex\_Leonhardt](https://avatars.discourse-cdn.com/v4/letter/a/ec9cab/32.png) [@Alex\_Leonhardt](https://forum.ansible.com/u/Alex_Leonhardt)\
**Post date:** [July 14, 2015, 12:31pm UTC](https://forum.ansible.com/t/unabel-to-use-pipelining-on-centos-6-6-amazon-linux/18754/2 "2015-07-14T12:31:24Z")

</div>

So someone on irc pointed me at the Default !requiretty … done that too - same problem.

Alex