# Random Parsing Problems in EC2?

**URL:** <https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [October 20, 2014, 4:04pm UTC](https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558 "2014-10-20T16:04:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jon\_Forrest](https://avatars.discourse-cdn.com/v4/letter/j/a698b9/32.png) [@Jon\_Forrest](https://forum.ansible.com/u/Jon_Forrest)\
**Post date:** [October 20, 2014, 4:04pm UTC](https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558/1 "2014-10-20T16:04:58Z")

</div>

This isn't a problem in Ansible (I pretty sure) but I'm curious  
whether other people have seen this. (This is with Ansible  
1.7.2, but I don't think it matters).

I have a playbook containing a bunch of tasks. No big deal.  
I run the playbook on my desktop machine to control a machine  
running in AWS. What happens is that various tasks fail with  
a message like:

failed: [ec2-XX-XXX-XX-XXX.compute-1.amazonaws.com] =\> {"failed": true, "parsed": false}

What's strange is that if I rerun the playbook right away, without  
making \*any\* changes, I get the same error, except in a different  
task. \*Update\* This morning when I came in, I again ran the same  
playbook. It finished without any problems!

One such task is that failed is the following:

- name: Enable hstore

> command: psql -d template1 -c 'create extension if not exists hstore;'

&nbsp;&nbsp;&nbsp;sudo: yes  
&nbsp;&nbsp;&nbsp;sudo\_user: postgres

It doesn't get much simpler than that.

I'm guessing that this is some kind of problem at AWS but  
I don't know what it could be. Has anyone else seen this?

Cordially,  
Jon Forrest

---

<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:** [October 20, 2014, 8:57pm UTC](https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558/2 "2014-10-20T20:57:10Z")

</div>

When you get a message like this there should be a “msg” below it that says what the error/response was.

Did you get this?

---

<div class="post-metadata">

**Author:** ![Jon\_Forrest](https://avatars.discourse-cdn.com/v4/letter/j/a698b9/32.png) [@Jon\_Forrest](https://forum.ansible.com/u/Jon_Forrest)\
**Post date:** [October 20, 2014, 10:27pm UTC](https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558/3 "2014-10-20T22:27:40Z")

</div>

No. I checked all three examples of different tasks failing.  
They all said the same thing, which was exactly (copying and  
pasting, except the host name)

failed: [ec2-XX-XX-XX-XX.compute-1.amazonaws.com] =\> {"failed": true, "parsed": false}

FATAL: all hosts have already failed -- aborting

This is why I don't think it was Ansible that was failing.  
I suspect something lower level.

Jon Forrest

---

<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:** [October 22, 2014, 3:46am UTC](https://forum.ansible.com/t/random-parsing-problems-in-ec2/16558/4 "2014-10-22T03:46:05Z")

</div>

Hmm, odd, at least in recent versions you should get some output back.

No output back would be very unusual.