All admins would have faced some issue with Windows remote management starting from executing a long running command or fetching some data. When you start using different tools to execute the same over WinRM for better tracking purpose first time setup is always little hard. So here also we will discuss on how to correctly setup WinRM plugin over Rundeck so that you will not face much issue. Example, while executing jobs over winRM in a windows environment you would have faced 500 internal server error when the command is long running and takes plenty of time to finish. When we migrated all our WinRM scripts to RunDeck to make it more user friendly we faced the same “Unexpected HTTP response 500” error after each one minute of job run. On debugging we came to know its due to the default timeouts set on the overthere plugin used in rundeck winrm plugin. So to avoid this issue and allow users to run long running jobs over WinRM follow below steps to fix. How ever same steps mentioned in “WinRM settings in the remote host” can be followed in case you are not using RunDeck but facing the same issue while directly running commands via WinRM.
Errors Seen while executing the commands:
com.xebialabs.overthere.cifs.winrm.WinRmRuntimeIOException: Unexpected HTTP response on http://lap1.techpaste.com:5985/wsman: (500)
[overthere-winrm:lap1.techpaste.com] failed: Unexpected HTTP response on http://lap1.techpaste.com:5985/wsman: (500)
Failed: WinRMProtocolError: Unexpected HTTP response on http://lap1.techpaste.com:5985/wsman: (500)
Continue reading »