Ansible Playbook running for longtime/indefinitely for windows 2012 R2 Ansible Playbook

60 views
Skip to first unread message

Namasivayam C

unread,
Mar 8, 2018, 2:32:51 AM3/8/18
to Ansible Project


I am new to Ansible and I'm trying to configure windows 2012 R2 from RHEL 7 Ansible Node. I'm able to establish connection between them using Winrm Credssp. Below is /etc/ansible/group_vars/windows.yml file


COMPONENT NAME
urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320


ANSIBLE VERSION
ansible 2.3.1.0

python version = 2.7.5


ansible_user: admin
ansible_password: XXXXXXX
ansible_winrm_scheme: https
ansible_winrm_transport: credssp
ansible_port: 5986
ansible_connection: winrm
ansible_winrm_server_cert_validation: ignore
validate_certs: false

When I execute win_ping module for testing connection from Ansible node to Windows 2012 R2 server it was successful.

[root@Ansible-Server playbooks]# ansible windows -m win_ping
XX.XX.XX.XX | SUCCESS => {
"changed": false,
"ping": "pong"
}

But When I have tried executing Windows 2012 R2 playbook file, after submitting ansible-playbook playbook.yml command, it is continuously waiting for indefinite time, as It is not completing.

Below is the log that is constantly displaying same. Waiting continuously. /var/log/ansible/log

2018-03-07 19:34:14,255 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:34:34,256 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:34:54,256 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:35:14,258 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:35:34,257 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:35:54,272 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:36:14,272 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:36:34,273 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:36:54,273 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:37:14,273 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:37:34,273 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:37:54,274 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:38:14,274 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:38:34,274 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320
2018-03-07 19:38:54,274 urllib3.connectionpool https://192.168.2.211:5986 "POST /wsman HTTP/1.1" 500 1320

above log continues/updates same for every 20 sec.

Could you please any one suggest where it' got stuck and how i can identify and troubleshoot .



Jordan Borean

unread,
Mar 8, 2018, 2:41:15 PM3/8/18
to Ansible Project
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 the server if there is no output so we try again until the command is complete.

Thanks

Jordan

Tony Chia

unread,
Mar 8, 2018, 3:50:59 PM3/8/18
to Ansible Project
Here are two things you can try
Try putting the win_ping module in a task in a playbook and run it.
Try adding -vvvvv (5 v for winrm connection debug info) to ansible-playbook

Ramanjaneyulu S

unread,
Apr 12, 2018, 11:01:08 AM4/12/18
to Ansible Project
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

Namasivayam C

unread,
Apr 13, 2018, 12:47:52 PM4/13/18
to ansible...@googlegroups.com
Hi 

We have rebooted the Ansible server issues got fixed

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/drzmhWiLvew/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b3088ba8-e074-4592-a919-3d6c9a497ff5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ramanjaneyulu S

unread,
Apr 16, 2018, 2:12:28 PM4/16/18
to Ansible Project
Thanks for replying. Unfortunately, rebooting did not worked for me.

J Hawkesworth

unread,
Apr 17, 2018, 4:33:08 AM4/17/18
to Ansible Project
Please share your playbook so others can understand what ansible is attempting to do.
Reply all
Reply to author
Forward
0 new messages