# ec2\_facts hung

**URL:** <https://forum.ansible.com/t/ec2-facts-hung/16154>\
**Category:** Ansible Project\
**Created:** [September 9, 2014, 12:35am UTC](https://forum.ansible.com/t/ec2-facts-hung/16154 "2014-09-09T00:35:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steven\_Truong](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@Steven\_Truong](https://forum.ansible.com/u/Steven_Truong)\
**Post date:** [September 9, 2014, 12:35am UTC](https://forum.ansible.com/t/ec2-facts-hung/16154/1 "2014-09-09T00:35:12Z")

</div>

Hi all,

The subject is misleading but I would like to get some helps on how to troubleshoot this or figure out what can be done.

I have about 70 instances with tag kafkaproducer=yes and I want to do rolling updates to them but my playbook went nowhere with ec2\_facts.

I ran the module ec2\_facts on the command line and at around 37 instances, the thing just stood there for eternity.  
ansible tag\_kafkaproducer\_yes -i ec2.py -m ec2\_facts -vvvv -f 10

…

\<ec2-…compute-1.amazonaws.com\> EXEC [‘ssh’, ‘-C’, ‘-tt’, ‘-vvv’, ‘-o’, ‘ControlMaster=auto’, ‘-o’, ‘ControlPersist=60s’, ‘-o’, ‘ControlPath=/home/steven/.ansible/cp/ansible-ssh-%h-%p-%r’, ‘-o’, ‘IdentityFile=“/home/steven/.ssh/key-ec2”’, ‘-o’, ‘KbdInteractiveAuthentication=no’, ‘-o’, ‘PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey’, ‘-o’, ‘PasswordAuthentication=no’, ‘-o’, ‘User=ec2-user’, ‘-o’, ‘ConnectTimeout=10’, u’ec2…compute-1.amazonaws.com’, u’/bin/sh -c 'su root -c “/bin/sh -c '”'“'echo SUDO-SUCCESS-zfbckatzfxprscqyvqbrpepuokyhmtnn; LANG=en\_US.UTF-8 LC\_CTYPE=en\_US.UTF-8 /usr/bin/python /home/ec2-user/.ansible/tmp/ansible-tmp-1410222363.53-10317830534118/ec2\_facts; rm -rf /home/ec2-user/.ansible/tmp/ansible-tmp-1410222363.53-10317830534118/ \>/dev/null 2\>&1'”'“'”'']

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [September 9, 2014, 4:43pm UTC](https://forum.ansible.com/t/ec2-facts-hung/16154/2 "2014-09-09T16:43:08Z")

</div>

Hmm, that’s interesting.

This may not help, but what version of Ansible are you on and is this the first task in your playbook? (Also, is gather\_facts enabled? If it gathers facts, this is the 2nd task and my question is not relevant).

---

<div class="post-metadata">

**Author:** ![Steven\_Truong](https://avatars.discourse-cdn.com/v4/letter/s/df705f/32.png) [@Steven\_Truong](https://forum.ansible.com/u/Steven_Truong)\
**Post date:** [September 9, 2014, 5:22pm UTC](https://forum.ansible.com/t/ec2-facts-hung/16154/3 "2014-09-09T17:22:44Z")

</div>

Hi Michael,

I am using 1.7.1 and gather\_facts was enabled by default.

And just this morning, I tried again then things are working just fine. At this point, it is not an issue but it did happen for me.

Sorry for wasting your times, Michael.

Thanks for your helps,  
Steven.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [September 9, 2014, 7:14pm UTC](https://forum.ansible.com/t/ec2-facts-hung/16154/4 "2014-09-09T19:14:37Z")

</div>

Nah, it’s ok.

I’m wondering if the EC2 metadata service had a glitch and was just giving you a very long timeout?