-
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
created issue -
Steve Haworth
added a comment - After much messing around, downgrading to SSH Plug-in to 0.22 and reverting to Jenkins 1.508 and then upgrading to 1.510 and then upgrading the plug-in separately. I have managed to get it working with a user and password defined in the credentials plugin.
Steve Haworth
added a comment - After much messing around, downgrading to SSH Plug-in to 0.22 and reverting to Jenkins 1.508 and then upgrading to 1.510 and then upgrading the plug-in separately. I have managed to get it working with a user and password defined in the credentials plugin. Steve Haworth
made changes -
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Happens to me as well (Master on Linux). No downgrade of SSH plugin or jenkins.war help in any way!
| Resolution | Original: Not A Defect [ 7 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
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.
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. | Priority | Original: Blocker [ 1 ] | New: Critical [ 2 ] |
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.
Note: Even rolling back the Windows VM to Jenkins v1.508 the nodes remain offline.