So, this means there is no good answer for cleaning up / ad-hoc debugging or was it just the question which was unclear? It happens regularly that ansible gets stuck on some machine (doing apt upgrades) and I don’t see any practical way of finding out even where it got stuck and why.
Cheers /rike Am Montag, 10. März 2014 11:56:08 UTC+1 schrieb Rike-Benjamin Schuppner: > > Hi, > > sometimes, ansible fails on a machine and leaves back running but possibly > blocking and frozen processes such as > > /usr/bin/python > /root/.ansible/tmp/ansible-tmp-1394441713.94-63420941773266/apt > > Is there a way to clean up those processes? > > Also related: Ansible sometimes apparently freezes or halts when running > on a client (or at least it does not return in time). Is there a way to at > the very least tell which host is affected without having to CTRL-C > everything and restart with -vvvv? Sometimes it would be really nice to get > back some live status information without having to wait for the process to > return correctly (which may not even happen at all if the process is > waiting for user input). > > Cheers > /rike > > -- 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/3d644ae2-0fc8-4c17-8bed-5ca5f880d9a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
