-
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
Error: Credentials cache I/O operation failed - on remote login to multiple windows hosts using same credentials #75
Comments
We are seeing similar issue. In running Rundeck 4.7 (Community version) on Oracle Linux 7; we are seeing where the python winrm plugin is returning the following errors when connecting to windows targets:
We have tried using the latest python winrm plugin (py-winrm-plugin-2.1.2); but the above error still happens randomly. For example of we run on 20+ windows servers; target server 10 and 15 might fail. Then if we re-run the same job; target server 8 and 12 might fail. Our pip3 installation list contains: certifi (2020.12.5) |
Hello, We're experiencing a similar problem with our rundeck jobs. Rundeck is installed in version 5.4.0 on a Debian 10 server. We use the py-winrm-plugin-2.1.3 python module to target machines running Windows. When executing a job, we randomly get this execution error. When we rerun the job on the same host, sometimes the job works, sometimes it doesn't, and we don't know why. This is the error we get: kerberos.GSSError: (('Invalid credential was supplied', 655360), ('No credentials cache found (filename: /tmp/krb5cc_112) Do you have any idea of the cause of the error and how to resolve it? Thank you for your help, Kevin Pemonon |
Hello - We have a requirement where we want to login to multiple (4+) windows hosts to deploy our application code. We are using Rundeck PyWinRM plugin to do the same. Everything works well when we try to log onto a single node or two nodes. When we increase the nodes to more than 3 to run our deploy script, we are running into what we believe is a concurrency issue. We are able to easily reproduce this error even with a simple script that just tries to login and do a pwd. It happens with both NodeFirst strategy as well as Parallel execution strategy.
Here's an excerpt from the error that's thrown on execution.
Any help is appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: