Intermittent Hanging of 'Gather Facts' on Local Host in Ansible

Get Help
1

We’ve observed intermittent instances where the first step of the Ansible playbook, which gathers facts, hangs for certain VMs. Excerpts of the playbook has been given below and from this, the debug statement that prints all the environment variables passed to the playbook doesn’t get printed ie msg: “{{ env }}”. After killing the hung processes and retrying the operation, it goes through successfully.

Any pointers for debugging this issue would be appreciated, as it is causing serious concerns with the predictability of operations. Thank you inadvance.

  • name: Test
    hosts: 127.0.0.1
    tasks:
    - debug:
    msg: “{{ env }}”
2

Hi. You can disable fact gathering if you don’t need it:

---
- name: Test
  hosts: 127.0.0.1
  gather_facts: false
...
3

Thanks for the quick response. We have disabled the fact gathering now but would like to know what could be the issue.

4

It’s hard to tell what’s wrong based on the information you have provided here.
The “{{ env }}” variable you are referring to is not an ansible fact.

5

This is one of the funDF2014:Fun - Dwarf Fortress Wiki issues that often appear with fact gathering. Most of the time this has to do with an issue with some hardware device, probably a mount or network issue.

To debug fact gathering i would suggest using gather_subset to eliminate possible culprits, also set a gather_timeout (which is for mount facts). This should narrow down possible culprits.

Ohter options are to strace/dtrace the process on the target machine while it is stuck, see what it is stuck on and try to derive the problem source from there.

6

(post deleted by author)

7

Thank you Jorn for taking the time to respond to this. Yes, {{ env }} is not related to Ansible facts, but the issue I was highlighting is that the control never reached that point because it got stuck during the gathering facts step.

8

This is a great suggestion, Brian. Let me try this out. Thank you so much for the pointers