# Ping & playbook runs failing for some boxes

**URL:** <https://forum.ansible.com/t/ping-playbook-runs-failing-for-some-boxes/21902>\
**Category:** Ansible Project\
**Tags:** ubuntu, aws\
**Created:** [June 30, 2016, 3:34pm UTC](https://forum.ansible.com/t/ping-playbook-runs-failing-for-some-boxes/21902 "2016-06-30T15:34:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sivabalan\_N](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@Sivabalan\_N](https://forum.ansible.com/u/Sivabalan_N)\
**Post date:** [June 30, 2016, 3:34pm UTC](https://forum.ansible.com/t/ping-playbook-runs-failing-for-some-boxes/21902/1 "2016-06-30T15:34:05Z")

</div>

Team,

I’m using ansible to deploy in my AWS production environment. I’m using dynamic inventory and ping & running playbook based on the host tag name. If I run ping for specific tag, 2 out of 5 servers are failing to ping. Similarly I’ve same issues for multiple AWS tags.

**root@ip-172-16-0-93:~# ansible --version**  
**ansible 2.1.0.0**  
**config file = /etc/ansible/ansible.cfg**  
**configured module search path = Default w/o overrides**

Config File:

[defaults]  
inventory = /etc/ansible/hosts  
remote\_tmp = $HOME/.ansible/tmp  
local\_tmp = $HOME/.ansible/tmp  
forks = 5  
poll\_interval = 15  
sudo\_user = ubuntu  
transport = smart  
remote\_port = 22  
module\_lang = C

gathering = implicit

# change this for alternative sudo implementations

sudo\_exe = sudo

# SSH timeout

timeout = 60  
remote\_user = ubuntu

log\_path = /var/log/ansible.log

private\_key\_file = /var/lib/rundeck/.ssh/id\_rsa

ansible\_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}

# set plugin path directories here, separate with colons

action\_plugins = /usr/share/ansible/plugins/action  
callback\_plugins = /usr/share/ansible/plugins/callback  
connection\_plugins = /usr/share/ansible/plugins/connection  
lookup\_plugins = /usr/share/ansible/plugins/lookup  
vars\_plugins = /usr/share/ansible/plugins/vars  
filter\_plugins = /usr/share/ansible/plugins/filter  
test\_plugins = /usr/share/ansible/plugins/test  
strategy\_plugins = /usr/share/ansible/plugins/strategy

fact\_caching = memory

[ssh\_connection]

ssh\_args = -o ControlMaster=auto -o ControlPersist=60s

control\_path = /var/lib/rundeck/.ansible/cp/ansible-ssh-%%h-%%p-%%r

pipelining = True

**Error:**

root@ip-172-16-0-93:~# ansible tag\_Ansible\_Worker -m ping  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | UNREACHABLE! =\> {  
“changed”: false,  
“msg”: “SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh”,  
“unreachable”: true  
}  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | UNREACHABLE! =\> {  
“changed”: false,  
“msg”: “SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh”,  
“unreachable”: true  
}  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | SUCCESS =\> {  
“changed”: false,  
“ping”: “pong”  
}  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | SUCCESS =\> {  
“changed”: false,  
“ping”: “pong”  
}  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | SUCCESS =\> {  
“changed”: false,  
“ping”: “pong”  
}  
ec2-_-_-_-_.ap-southeast-1.compute.amazonaws.com | SUCCESS =\> {  
“changed”: false,  
“ping”: “pong”  
}

Thanks in Advance,

Siva.

---

<div class="post-metadata">

**Author:** ![jtanner](https://avatars.discourse-cdn.com/v4/letter/j/6bbea6/32.png) [@jtanner](https://forum.ansible.com/u/jtanner)\
**Post date:** [July 1, 2016, 4:52pm UTC](https://forum.ansible.com/t/ping-playbook-runs-failing-for-some-boxes/21902/2 "2016-07-01T16:52:45Z")

</div>

Add -vvvv to the ansible command so that you can see the ssh arguments in use.