> > "In future runs, it will continue to refuse the accelerated port until > the hanging python daemon has been killed manually." > > This part seems more interesting and I haven't seen this. If you can > find a way to replicate the problem without an airplane that would be > helpful and we could take a look :) >
We've used to see this as well on occasion before we ditched accelerate for ssh_alt. Despite our best efforts we were unable to determine a way to reliably reproduce. The only solution was logging onto the box and killing python (or waiting for the timeout). I believe it had something to do with not have the key from the previous accelerate session and the previous session still waiting for tasks. -- Peter Gehres Site Reliability Engineer | AppDynamics, Inc. www.appdynamics.com | AS62897 -- 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/CABpn%2BqQwxYvuk1KEb%3DKRoGNdLmvf%3DU3n4RWP8wh%3DT7fyq_uAPQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
