Hi,
I do have some problems using Ansible with Windows.
For many of my servers it works, but for some I’m receiving “HTTPConnectionPool(host=‘10.10.193.180’, port=5985): Read timed out” even if the WinRM configuration is correct. (it’s the same as several others)
More over, if I run a Enter-PSSession myhost.domain.com from another Windows server, it works and after that command also ansible win_ping is responding.
Below my test case
Anything in the event log on the affected machines?
Do the affected machines run IIS? I recall a problem where the remoting didn’t work fully when some domain account mapping configuration was in place (unfortunately I don’t now remember the name of the domain user mapping mechanism, so can’t search for it).
Is there anything else different about the affected machines? Load? Network proximity?
Hope this helps,
Jon
The only time I’ve ever seen that behavior is on the first request to a brand-new Windows AWS instance. For some reason, the shell creation can take up to 30s, much longer than our default operation timeout of ~5s.
You can try increasing the operation and read timeouts by adjusting the ansible_winrm_operation_timeout_sec and ansible_winrm_read_timeout_sec inventory vars (the read timeout must be > than operation timeout). They’re set to relatively low values to minimize the “dead host” detection interval, and this doesn’t typically cause problems in normal operation.
-Matt
Hi Matt,
thanks for the suggestion. I’ve added
|
ansible_winrm_operation_timeout_sec: 100 and |
|
ansible_winrm_read_timeout_sec: 120
to my settings and now it works!!
Mike