-
Bug
-
Resolution: Duplicate
-
Critical
-
Master is a Windows 64 Bit VM with 6 Linux slave Nodes
Slave nodes fail to start, Error Log shows,
[04/08/13 18:22:49] [SSH] Opening SSH connection to <Slave Hostname>:22.
[04/08/13 18:22:53] [SSH] Authentication failed.
hudson.AbortException: Authentication failed.
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907)
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:462)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
[04/08/13 18:22:53] [SSH] Connection closed.
- duplicates
-
-
- Closed
-
[JENKINS-17519] After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth
added a comment - The install tries to resolve your existing SSH credentials by making entries in in Manage Jenkins\Manage Credentials.
In my case it got it wrong by assuming I was using a Private Key.
So I deleted all the erroneous entries and added an authentication using user and password, I then selected this credential in the node and it worked.
Steve Haworth
added a comment - The install tries to resolve your existing SSH credentials by making entries in in Manage Jenkins\Manage Credentials.
In my case it got it wrong by assuming I was using a Private Key.
So I deleted all the erroneous entries and added an authentication using user and password, I then selected this credential in the node and it worked. It happens to me as well (master&slave CentOS). Problem is the private key with password. I think it does not use the password to unlock the key.
Herbert Vojčík
added a comment - - edited It happens to me as well (master&slave CentOS). Problem is the private key with password. I think it does not use the password to unlock the key. Herbert Vojčík
added a comment - Deleting all credentials and creating them anew solved. 
HemangLavana
added a comment - It is happening to me as well. I am unable to use private key for authentication, even on a completely fresh installation of jenkins/ssh-slaves plugin. I rolled back to 0.22 version of ssh slaves plugin and I was able to get it to work but I lost all the private key passphrase stored in all the slave nodes. I have to manually re-enter all of them and I had over 40 slave nodes. I hope this issue gets fixed soon.
HemangLavana
added a comment - It is happening to me as well. I am unable to use private key for authentication, even on a completely fresh installation of jenkins/ssh-slaves plugin. I rolled back to 0.22 version of ssh slaves plugin and I was able to get it to work but I lost all the private key passphrase stored in all the slave nodes. I have to manually re-enter all of them and I had over 40 slave nodes. I hope this issue gets fixed soon. I had the same issue and downgrade to 0.22 of the ssh-slaves plugin solved it for me as well. I needed to re-enter the credentials for all the nodes as well. Lucky me that I have only 6 nodes...
Herbert Vojčík
added a comment - @Yoram No need to downgrade for me. Just delete all credentials, restart Jenkins and set them back, and it works with 0.23.
Herbert Vojčík
added a comment - @Yoram No need to downgrade for me. Just delete all credentials, restart Jenkins and set them back, and it works with 0.23. HemangLavana
added a comment - @Herbert Do you use passphrase/private key or username/password for authentication? I suspect that 0.23 has some issues with private key auth.
In my setup, the jenkins server is run under a dedicated userid say "jenkins" but for certain tasks it needs to login to slave nodes with my userid. I enable this in jenkins by providing access to "jenkins" userid to my account via ssh private key method. I don't want to store my username/password in jenkins (since it is not secure). Instead the "jenkins" userid can access my account via passphase/private authentication which seems to be broken in 0.23.
HemangLavana
added a comment - @Herbert Do you use passphrase/private key or username/password for authentication? I suspect that 0.23 has some issues with private key auth.
In my setup, the jenkins server is run under a dedicated userid say "jenkins" but for certain tasks it needs to login to slave nodes with my userid. I enable this in jenkins by providing access to "jenkins" userid to my account via ssh private key method. I don't want to store my username/password in jenkins (since it is not secure). Instead the "jenkins" userid can access my account via passphase/private authentication which seems to be broken in 0.23. Herbert Vojčík
added a comment - @HemangL My setup is:
- no security
- connecting to slave with password-protected private key.
After delete, restart and create it worked fine (I should mention that backed up data, reinstalled whole jenkins (I have it under OpenVZ machine that is created and populated by script, so no big hassle for me) and returned data back, only then I did the delete-restart-recreate).
Herbert Vojčík
added a comment - @HemangL My setup is:
no security
connecting to slave with password-protected private key.
After delete, restart and create it worked fine (I should mention that backed up data, reinstalled whole jenkins (I have it under OpenVZ machine that is created and populated by script, so no big hassle for me) and returned data back, only then I did the delete-restart-recreate). 
Problem overcome using a workaround: setting user/password to a local server user instead of the default (leaving the user/password setting empty so it uses a special jenkins account) - seems something has been changed reguarding the jenkins local user.