We're having a problem when accelerated mode unexpectedly disconnects for whatever reason. This happens often when running test playbooks from poor connections, e.g. in-flight wifi. It can also happen when running a big play book when you just hit the dropped connection lottery. In either case, the host fail out saying "unable to connect to port 5099". In future runs, it will continue to refuse the accelerated port until the hanging python daemon has been killed manually.
Thus far the only way I've found to kill the daemon is to killall python (I haven't discovered a way of definitely identifying it's PID). I can run something like ansible GROUP -m command -a "killall pyhon" but this has the unwanted side effect of killing all other python processes on the system. Advice? All the best, ~ Christopher -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/67a69b65-ea3d-47c9-97f6-9109621bf1d2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
