Dear all,

doing my first steps with ansible I noticed, that on some clients executing playbooks completely hangs. The common problem on these hosts is, that they are either swapping (even very small amounts of swap used) or they have problems with hanging/not responding NFS filesystems. In all cases, these two problems appeared together. Therefore I cannot say, which is the problematic issue.

However all local filesystems are perfectly ok and responding and working. The system over-all is also working fine.

Running even the simplest playbooks on these hosts hangs completely, even though the playbooks don't access the problematic filesystems. Running the same commands as ad-hoc commands, works fine:

$ ansible buggyhost -m shell -a '/bin/ls' --key=id_rsa
buggyhost | SUCCESS | rc=0 >>
[... `/bin/ls` output here..]

$

... but ...

$ ansible-playbook ls.yml --extra-vars "target=buggyhost" --private-key=id_rsa

PLAY [buggyhost] ***************************************************************

TASK [setup] *******************************************************************
[...and here it hangs...]
^C
$

using -vvv doesn't really help:


$ ansible-playbook -vvv ls.yml --extra-vars "target=buggyhost" --private-key=id_rsa
Using /root/ansible-config/ansible.cfg as config file

PLAYBOOK: ls.yml ***************************************************************
1 plays in ls.yml

PLAY [buggyhost] ***************************************************************

TASK [setup] ******************************************************************* Using module file /root/ansible/ansible/lib/ansible/modules/core/system/setup.py
<buggyhost> ESTABLISH SSH CONNECTION FOR USER: None
<buggyhost> SSH: EXEC ssh -q -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r buggyhost '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534 `" && echo ansible-tmp-1471604358.1-265208088531534="` echo $HOME/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534 `" ) && sleep 0'"'"'' <buggyhost> PUT /tmp/tmp7cAXoN TO /root/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534/setup.py <buggyhost> SSH: EXEC sftp -b - -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r '[buggyhost]'
<buggyhost> ESTABLISH SSH CONNECTION FOR USER: None
<buggyhost> SSH: EXEC ssh -q -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r buggyhost '/bin/sh -c '"'"'chmod -R u+x /root/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534/ && sleep 0'"'"''
<buggyhost> ESTABLISH SSH CONNECTION FOR USER: None
<buggyhost> SSH: EXEC ssh -q -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r -tt buggyhost '/bin/sh -c '"'"'/usr/bin/python /root/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534/setup.py; rm -rf "/root/.ansible/tmp/ansible-tmp-1471604358.1-265208088531534/" > /dev/null 2>&1 && sleep 0'"'"''
^C
$

The playbook being

$ cat ls.yml
---
- hosts: '{{ target }}'
  tasks:
  - name:    Run ls
    shell:  /bin/ls
$


I am using asible 2.2.0 (devel 3afe50dfe2). Server and clients are running openSuSE 13.1.

Any idea, why playbooks hang in this situation?

Cheers
frank


--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a8bae753-08bb-4a4a-b775-3ba775624c26%40drosera.ch.
For more options, visit https://groups.google.com/d/optout.

Reply via email to