-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pywinrm node executor times out at 8 hour mark #55
Comments
Have you set your timeout properly in winrs at the target server? winrm get winrm/config look at the winrs sub-section |
Hi @oj43085 , thanks for the inputs. Yes, I checked winrm config which I am sharing in this post If I set WinRM as default node executor, then the job runs successfully for more than 8 hours (next attached image), but if I set Pywinrm as default executor then the job fails exactly after 8 hours. I am not sure but when using Pywinrm plugin, looks like there is some sort of hardcoded timeout |
I can't reproduce the issue in my local environments using Rundeck in a Linux server connecting to windows 10 machine. the project configuration
this is the job definition
and, this is my PowerShell configuration |
ref: diyan/pywinrm#325 same issue on base pywinrm project |
Reproduced on 3.3.9 |
I don't think it's pywinrm that's timing out... whatever you've set the max shell runtime to is ignored since WinRm 2.0 "WinRM 2.0: The MaxShellRunTime setting is set to read-only. Changing the value for MaxShellRunTime will have no effect on the remote shells." I suspect if you had winrm 1,0 installed and changed the setting, when upgrading to v2 or v3, this hasn't reset the default so is using the modified value - whereas newer installs will default to 8hrs |
When using "WinRM Node Executor Python" and executing long running job against a remote node, the job fails exactly at the 8 hour mark. It looks like pywinrm has some sort of timeout (8 hours).
The workaround was to use the default ssh as node executor and the pywinrm as file copier
Steps to reproduce
Create a project, set pywinrm as node executor and default file copier, and create a job that runs a long running batch script in a windows remote node.
Inline script on Rundeck server (RPM Installation- 3.1.2)
Batch script to execute on remote Windows node
Sample execution screenshots for reference
The text was updated successfully, but these errors were encountered: