Re: [ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

Please share your playbook so others can understand what ansible is attempting to do. On Monday, April 16, 2018 at 7:12:28 PM UTC+1, Ramanjaneyulu S wrote: > > Thanks for replying. Unfortunately, rebooting did not worked for me. > > On Friday, 13 April 2018 12:47:52 UTC-4, Namasivayam C wrote:

Re: [ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

Thanks for replying. Unfortunately, rebooting did not worked for me. On Friday, 13 April 2018 12:47:52 UTC-4, Namasivayam C wrote: > > Hi > > We have rebooted the Ansible server issues got fixed > > On Thu 12 Apr, 2018, 8:31 PM Ramanjaneyulu S, > wrote: > >> I have the same

Re: [ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

Hi We have rebooted the Ansible server issues got fixed On Thu 12 Apr, 2018, 8:31 PM Ramanjaneyulu S, wrote: > I have the same issue while using win_packageto install applications on > remote windows servers. in the log ansible is giving status code 200 thrice > and then

[ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

I have the same issue while using win_packageto install applications on remote windows servers. in the log ansible is giving status code 200 thrice and then status code 500 consistently. let me know, if you got any workaround. Thank you On Thursday, 8 March 2018 02:32:51 UTC-5, Namasivayam C

[ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

Here are two things you can try Try putting the win_ping module in a task in a playbook and run it. Try adding -v (5 v for winrm connection debug info) to ansible-playbook On Wednesday, March 7, 2018 at 11:32:51 PM UTC-8, Namasivayam C wrote: > > > I am new to Ansible and I'm trying to

[ansible-project] Re: Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

We would probably need to see the playbook file and the output you are getting until it freezes so we can narrow down what task is taking forever. As for the HTTP 500 responses I don't think they are an issue, part of WinRM is to poll for command outputs and you get constant 500 responses from