hudson.AbortException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • I updated to 1.480.3 (from 1.480.2) so i also updated all plugins -> so ssh-slaves was updated from 0.22 to 0.23 The upgrade process seems to have created all needed entries for the ssh-credentials plugin. But they are not working (keyfile + pwd type)! [TRACE] The same effect appears when i create the new entry manually. Which does NOT work when: - using "Enter directly" - using "From a file on Jenkins master " with relative or absolute path - using "From the Jenkins master ~/.ssh" - using not the keyfile password but the password of the user There also no changes in the error message when typing in a wrong username, or a wrong password. It only works when loging in with username password combination. So i would say the keyfile authentication is completely broken. PS: via plain ssh i can login with that keyfile. TRACE: [03/26/13 16:51:01] [SSH] Opening SSH connection to 192.168.0.24:22. [03/26/13 16:51:01] [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:224) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [03/26/13 16:51:01] [SSH] Connection closed.
    via by Rainer Weinhold,
  • I updated to 1.480.3 (from 1.480.2) so i also updated all plugins -> so ssh-slaves was updated from 0.22 to 0.23 The upgrade process seems to have created all needed entries for the ssh-credentials plugin. But they are not working (keyfile + pwd type)! [TRACE] The same effect appears when i create the new entry manually. Which does NOT work when: - using "Enter directly" - using "From a file on Jenkins master " with relative or absolute path - using "From the Jenkins master ~/.ssh" - using not the keyfile password but the password of the user There also no changes in the error message when typing in a wrong username, or a wrong password. It only works when loging in with username password combination. So i would say the keyfile authentication is completely broken. PS: via plain ssh i can login with that keyfile. TRACE: [03/26/13 16:51:01] [SSH] Opening SSH connection to 192.168.0.24:22. [03/26/13 16:51:01] [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:224) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [03/26/13 16:51:01] [SSH] Connection closed.
    via by Rainer Weinhold,
  • Upgrade and Slave Nodes fail to start
    via by Jared Griffith,
  • can't start slaves anymore, ssh auth failing
    via by Haszlakiewicz, Eric,
  • After updating SSH Slaves plugin to 0.23 we get this when slave is starting: {noformat} [03/27/13 10:07:14] [SSH] Checking java version of /home/hudson/JDK_HOME_1_6_0/bin/java [03/27/13 10:07:15] [SSH] /home/hudson/JDK_HOME_1_6_0/bin/java -version returned 1.6.0_16. [03/27/13 10:07:15] [SSH] Starting sftp client. [03/27/13 10:07:15] [SSH] Copying latest slave.jar... [03/27/13 10:07:15] [SSH] Copied 278,201 bytes. ERROR: Failed to expand buffer size java.lang.NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int) at java.lang.Class.getMethod(Class.java:1622) at hudson.plugins.sshslaves.SSHLauncher.expandChannelBufferSize(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:661) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:472) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [03/27/13 10:07:15] [SSH] Starting slave process: cd '/home/hudson/HUDSON_HOME' && /home/hudson/JDK_HOME_1_6_0/bin/java -Xmx1024m -XX:HeapDumpPath=/home/hudson/HUDSON_HOME/_dumps/ -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.17 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Slave successfully connected and online {noformat} We had to downgrade to SSH Slaves plugin to 0.22, which resolved the problem: {noformat} [03/27/13 10:16:32] [SSH] Checking java version of /home/hudson/JDK_HOME_1_6_0/bin/java [03/27/13 10:16:33] [SSH] /home/hudson/JDK_HOME_1_6_0/bin/java -version returned 1.6.0_16. [03/27/13 10:16:33] [SSH] Starting sftp client. [03/27/13 10:16:33] [SSH] Copying latest slave.jar... [03/27/13 10:16:33] [SSH] Copied 278,201 bytes. [03/27/13 10:16:33] [SSH] Starting slave process: cd '/home/hudson/HUDSON_HOME' && /home/hudson/JDK_HOME_1_6_0/bin/java -Xmx1024m -XX:HeapDumpPath=/home/hudson/HUDSON_HOME/_dumps/ -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.17 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Slave successfully connected and online {noformat} BTW, during this upgrade\-...\-downgrade process SSH slave credentials somehow got reset: {noformat} [03/27/13 10:14:02] [SSH] Opening SSH connection to jenkins-l64b.ourcompany.com:22. [03/27/13 10:14:02] [SSH] Authenticating as jenkins/******. [03/27/13 10:14:02] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:753) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:278) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [03/27/13 10:14:02] [SSH] Connection closed. {noformat} We've been using hudson/jenkins for many years and had to switch to LTS since so called "normal" version would get broken in 95%+ of all plugin/Jenkins updates. And now we observe similar problem with LTS. I guess many Jenkins users would agree with me that this is not OK and something has to be done in this respect. The first thing that comes into my mind is introducing "Community ratings" for plugins too (helped us many times to avoid upgrading to unusable new version of "normal" Jenkins branch).
    via by pancake,
  • I updated Jenkins to 1.514 using Jenkins SSH Slaves plugin 0.25 and all the connected nodes error with: <code> [05/02/13 11:26:09] [SSH] Opening SSH connection to x:22. ERROR: Failed to authenticate as x with credential=x-x-x-x-x java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:264) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:445) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:92) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:262) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:282) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:918) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:479) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.IOException: Invalid PEM structure, '-----BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:173) ... 12 more [05/02/13 11:26:09] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:923) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:479) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) [05/02/13 11:26:09] [SSH] Connection closed. </code> The keys haven't changed and they worked fine before the upgrade...
    via by bootstraponline,
  • After updating SSH Slaves plugin to 0.23 we get this when slave is starting: {noformat} [03/27/13 10:07:14] [SSH] Checking java version of /home/hudson/JDK_HOME_1_6_0/bin/java [03/27/13 10:07:15] [SSH] /home/hudson/JDK_HOME_1_6_0/bin/java -version returned 1.6.0_16. [03/27/13 10:07:15] [SSH] Starting sftp client. [03/27/13 10:07:15] [SSH] Copying latest slave.jar... [03/27/13 10:07:15] [SSH] Copied 278,201 bytes. ERROR: Failed to expand buffer size java.lang.NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int) at java.lang.Class.getMethod(Class.java:1622) at hudson.plugins.sshslaves.SSHLauncher.expandChannelBufferSize(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:661) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:472) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [03/27/13 10:07:15] [SSH] Starting slave process: cd '/home/hudson/HUDSON_HOME' && /home/hudson/JDK_HOME_1_6_0/bin/java -Xmx1024m -XX:HeapDumpPath=/home/hudson/HUDSON_HOME/_dumps/ -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.17 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Slave successfully connected and online {noformat} We had to downgrade to SSH Slaves plugin to 0.22, which resolved the problem: {noformat} [03/27/13 10:16:32] [SSH] Checking java version of /home/hudson/JDK_HOME_1_6_0/bin/java [03/27/13 10:16:33] [SSH] /home/hudson/JDK_HOME_1_6_0/bin/java -version returned 1.6.0_16. [03/27/13 10:16:33] [SSH] Starting sftp client. [03/27/13 10:16:33] [SSH] Copying latest slave.jar... [03/27/13 10:16:33] [SSH] Copied 278,201 bytes. [03/27/13 10:16:33] [SSH] Starting slave process: cd '/home/hudson/HUDSON_HOME' && /home/hudson/JDK_HOME_1_6_0/bin/java -Xmx1024m -XX:HeapDumpPath=/home/hudson/HUDSON_HOME/_dumps/ -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.17 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Slave successfully connected and online {noformat} BTW, during this upgrade\-...\-downgrade process SSH slave credentials somehow got reset: {noformat} [03/27/13 10:14:02] [SSH] Opening SSH connection to jenkins-l64b.ourcompany.com:22. [03/27/13 10:14:02] [SSH] Authenticating as jenkins/******. [03/27/13 10:14:02] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:753) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:278) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [03/27/13 10:14:02] [SSH] Connection closed. {noformat} We've been using hudson/jenkins for many years and had to switch to LTS since so called "normal" version would get broken in 95%+ of all plugin/Jenkins updates. And now we observe similar problem with LTS. I guess many Jenkins users would agree with me that this is not OK and something has to be done in this respect. The first thing that comes into my mind is introducing "Community ratings" for plugins too (helped us many times to avoid upgrading to unusable new version of "normal" Jenkins branch).
    via by pancake,
    • 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:224) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,