ansible win_ping "WINRM RESULT <Response code 0, out "", err "ConvertTo-Json : Une">"

418 views
Skip to first unread message

youmarva

unread,
Dec 15, 2014, 10:44:48 AM12/15/14
to ansible...@googlegroups.com
Hi,

I have configured my server Ansible and my windows machines to use the windows modules, the connection is going well for most of the machines tested except for a few where I have the following error when i execute ansible
#windows -m win_ping -vvvv
ansible windows
-m win_ping -vvvv
<172.16.0.80> ESTABLISH WINRM CONNECTION FOR USER: infra on PORT 5986 TO 172.16.0.80
<172.16.0.80> WINRM CONNECT: transport=plaintext endpoint=https://172.16.0.80:5986/wsman
<172.16.0.80> REMOTE_MODULE win_ping
<172.16.0.80> EXEC (New-Item -Type Directory -Path $env:temp -Name "ansible-tmp-1418653333.53-246551001925925").FullName | Write-Host -Separator '';
<172.16.0.80> WINRM EXEC 'PowerShell' ['-NoProfile', '-NonInteractive', '-EncodedCommand', 'KABOAGUAdwAtAEkAdABlAG0AIAAtAFQAeQBwAGUAIABEAGkAcgBlAGMAdABvAHIAeQAgAC0AUABhAHQAaAAgACQAZQBuAHYAOgB0AGUAbQBwACAALQBOAGEAbQBlACAAIgBhAG4AcwBpAGIAbABlAC0AdABtAHAALQAxADQAMQA4ADYANQAzADMAMwAzAC4ANQAzAC0AMgA0ADYANQA1ADEAMAAwADEAOQAyADUAOQAyADUAIgApAC4ARgB1AGwAbABOAGEAbQBlACAAfAAgAFcAcgBpAHQAZQAtAEgAbwBzAHQAIAAtAFMAZQBwAGEAcgBhAHQAbwByACAAJwAnADsA']
<172.16.0.80> WINRM RESULT <Response code 0, out "C:\Users\infra\AppDa", err "">
<172.16.0.80> PUT /tmp/tmpfe1MUN TO C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\win_ping
<172.16.0.80> WINRM PUT /tmp/tmpfe1MUN to C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\win_ping.ps1 (offset=0 size=2037)
<172.16.0.80> WINRM PUT /tmp/tmpfe1MUN to C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\win_ping.ps1 (offset=2037 size=2037)
<172.16.0.80> WINRM PUT /tmp/tmpfe1MUN to C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\win_ping.ps1 (offset=4074 size=1807)
<172.16.0.80> PUT /tmp/tmpMlMZ5d TO C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\arguments
<172.16.0.80> WINRM PUT /tmp/tmpMlMZ5d to C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\arguments (offset=0 size=2)
<172.16.0.80> EXEC PowerShell -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -File "C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\win_ping.ps1" "C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\\arguments"; Remove-Item "C:\Users\infra\AppData\Local\Temp\ansible-tmp-1418653333.53-246551001925925\" -Force -Recurse;
<172.16.0.80> WINRM EXEC 'PowerShell' ['-NoProfile', '-NonInteractive', '-EncodedCommand', 'UABvAHcAZQByAFMAaABlAGwAbAAgAC0ATgBvAFAAcgBvAGYAaQBsAGUAIAAtAE4AbwBuAEkAbgB0AGUAcgBhAGMAdABpAHYAZQAgAC0ARQB4AGUAYwB1AHQAaQBvAG4AUABvAGwAaQBjAHkAIABVAG4AcgBlAHMAdAByAGkAYwB0AGUAZAAgAC0ARgBpAGwAZQAgACIAQwA6AFwAVQBzAGUAcgBzAFwAaQBuAGYAcgBhAFwAQQBwAHAARABhAHQAYQBcAEwAbwBjAGEAbABcAFQAZQBtAHAAXABhAG4AcwBpAGIAbABlAC0AdABtAHAALQAxADQAMQA4ADYANQAzADMAMwAzAC4ANQAzAC0AMgA0ADYANQA1ADEAMAAwADEAOQAyADUAOQAyADUAXABcAHcAaQBuAF8AcABpAG4AZwAuAHAAcwAxACIAIAAiAEMAOgBcAFUAcwBlAHIAcwBcAGkAbgBmAHIAYQBcAEEAcABwAEQAYQB0AGEAXABMAG8AYwBhAGwAXABUAGUAbQBwAFwAYQBuAHMAaQBiAGwAZQAtAHQAbQBwAC0AMQA0ADEAOAA2ADUAMwAzADMAMwAuADUAMwAtADIANAA2ADUANQAxADAAMAAxADkAMgA1ADkAMgA1AFwAXABhAHIAZwB1AG0AZQBuAHQAcwAiADsAIABSAGUAbQBvAHYAZQAtAEkAdABlAG0AIAAiAEMAOgBcAFUAcwBlAHIAcwBcAGkAbgBmAHIAYQBcAEEAcABwAEQAYQB0AGEAXABMAG8AYwBhAGwAXABUAGUAbQBwAFwAYQBuAHMAaQBiAGwAZQAtAHQAbQBwAC0AMQA0ADEAOAA2ADUAMwAzADMAMwAuADUAMwAtADIANAA2ADUANQAxADAAMAAxADkAMgA1ADkAMgA1AFwAIgAgAC0ARgBvAHIAYwBlACAALQBSAGUAYwB1AHIAcwBlADsA']
<172.16.0.80> WINRM RESULT <Response code 0, out "", err "
ConvertTo-Json : ">
pc-bill | FAILED >> {
    "
failed": true,
    "
msg": "ConvertTo-Json : \r\n",
    "
parsed": false
}

or

<172.16.0.80> WINRM RESULT
<Response code 0, out "", err "ConvertTo-Json : Une">
pc-bill | FAILED => Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/__init__.py", line 579, in _executor
    exec_rc = self._executor_internal(host, new_stdin)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/__init__.py", line 752, in _executor_internal
    return self._executor_internal_inner(host, self.module_name, self.module_args, inject, port, complex_args=complex_args)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/__init__.py", line 985, in _executor_internal_inner
    result = handler.run(conn, tmp, module_name, module_args, inject, complex_args)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/action_plugins/normal.py", line 57, in run
    return self.runner._execute_module(conn, tmp, module_name, module_args, inject=inject, complex_args=complex_args)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/__init__.py", line 544, in _execute_module
    res = self._low_level_exec_command(conn, cmd, tmp, sudoable=sudoable, in_data=in_data)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/__init__.py", line 1133, in _low_level_exec_command
    in_data=in_data)
  File "/usr/local/lib/python2.7/dist-packages/ansible-1.8-py2.7.egg/ansible/runner/connection_plugins/winrm.py", line 153, in exec_command
    return (result.status_code, '', result.std_out.encode('utf-8'), result.std_err.encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x82 in position 56: ordinal not in range(128)

or

failed: [pc-riadh] => {"failed": true, "parsed": false}

Process is terminated due to StackOverflowException.


When researching this problem in the internet,
I found in the forum talking about a problem of memory dedicated in the target machine.
  But I haven't been able to diagnose the problem
If you can help me it will be very useful to me
.

thanks

Youmarva


J Hawkesworth

unread,
Dec 15, 2014, 11:35:17 AM12/15/14
to ansible...@googlegroups.com
I think I had this StackOverflowException  problem in the past with a windows server 2008 installation which had not received any windows updates.
I suggest you check you are up to date with windows updates.
Jon

youmarva

unread,
Dec 15, 2014, 11:51:59 AM12/15/14
to ansible...@googlegroups.com
Thanks Jon for your reply, I will try to update windows and I inform you of the result.

Chris Church

unread,
Dec 15, 2014, 1:40:03 PM12/15/14
to ansible...@googlegroups.com
This hotfix was previously mentioned on the list (https://groups.google.com/d/topic/ansible-project/nve1NRr2Vx4/discussion) as a fix for this problem:



--
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 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/593e5dee-bb88-4ef5-bb6d-2385ba8ca9f6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages