java.io.IOException: Publickey authentication failed.

Jenkins JIRA | cosmo king | 3 years ago
  1. 0

    Using Ecualyptus slaves, it can take a while before the DNS name is populated with the correct IP is referenced by the name. Until then, euca-0-0-0-0.eucalyptus.eucadomain... is presented. Needless to say, if the ec2 plugin tries to connect to that name, it fails. The mitigation would seem to be to allow a wait before connect option, or a retry option which re-checks dns on retry. I edited the plugin myself to add a dumb fixed 60s delay and that did fix the issue, however this should be fixed properly. Stack trace follows. Connecting to euca-0-0-0-0.eucalyptus.eucadomain.sc.local on port 22. Connected via SSH. bootstrap() Getting keypair... Using key: jenkins cc:05:1a:f4:95:e0:0d:99:b9:ea:56:fd:6c:90:a1:d0:85:8d:74:5e -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAn/addoIs+dTHJlhb6D+mex0m/hdXbQz5UWBDIKnU5g2cPWFW L4n0HaoJ8nHMSviDmzFfZ+Mdutn+aEzSz/lvmHK1VS4tJ+W5adFc6CcohFU2u6w Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc ERROR: Publickey authentication failed. 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 hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:187) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:77) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:80) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.io.IOException: The connection is closed. at com.trilead.ssh2.auth.AuthenticationManager.deQueue(AuthenticationManager.java:79) at com.trilead.ssh2.auth.AuthenticationManager.getNextMessage(AuthenticationManager.java:102) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:239) ... 10 more Caused by: java.io.IOException: Peer sent DISCONNECT message (reason code 2): Too many authentication failures for spacecurve at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:750) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:475) ... 1 more

    Jenkins JIRA | 3 years ago | cosmo king
    java.io.IOException: Publickey authentication failed.
  2. 0

    Using Ecualyptus slaves, it can take a while before the DNS name is populated with the correct IP is referenced by the name. Until then, euca-0-0-0-0.eucalyptus.eucadomain... is presented. Needless to say, if the ec2 plugin tries to connect to that name, it fails. The mitigation would seem to be to allow a wait before connect option, or a retry option which re-checks dns on retry. I edited the plugin myself to add a dumb fixed 60s delay and that did fix the issue, however this should be fixed properly. Stack trace follows. Connecting to euca-0-0-0-0.eucalyptus.eucadomain.sc.local on port 22. Connected via SSH. bootstrap() Getting keypair... Using key: jenkins cc:05:1a:f4:95:e0:0d:99:b9:ea:56:fd:6c:90:a1:d0:85:8d:74:5e -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAn/addoIs+dTHJlhb6D+mex0m/hdXbQz5UWBDIKnU5g2cPWFW L4n0HaoJ8nHMSviDmzFfZ+Mdutn+aEzSz/lvmHK1VS4tJ+W5adFc6CcohFU2u6w Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc Authentication failed. Trying again... Authenticating as sc ERROR: Publickey authentication failed. 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 hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:187) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:77) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:80) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.io.IOException: The connection is closed. at com.trilead.ssh2.auth.AuthenticationManager.deQueue(AuthenticationManager.java:79) at com.trilead.ssh2.auth.AuthenticationManager.getNextMessage(AuthenticationManager.java:102) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:239) ... 10 more Caused by: java.io.IOException: Peer sent DISCONNECT message (reason code 2): Too many authentication failures for spacecurve at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:750) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:475) ... 1 more

    Jenkins JIRA | 3 years ago | cosmo king
    java.io.IOException: Publickey authentication failed.
  3. 0

    resending: failing ssh authentication with Solaris slave

    Google Groups | 5 years ago | Max Spring
    java.io.IOException: Publickey authentication failed.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JIRA] [ec2-plugin] (JENKINS-30284) EC2 plugin too aggressive in timing in contacting new AWS instance over SSH

    Google Groups | 1 year ago | michael.kingsbury@aspect.com (JIRA)
    java.io.IOException: Publickey authentication failed.
  6. 0

    In every 10 or so instance launches, I see cases where the EC2 plugin opens a SSH connection to the new instance before the time where I believe the corresponding private key has been put in place by the AWS infrastructure during the launch of the instance. As a result, we see errors in the node launch. The output for the launch is below. just before slave CentOS (i-f295e51b) gets launched ... executing pre-launch scripts ... Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is still pending/launching, waiting 5s Node CentOS (i-f295e51b)(i-f295e51b) is ready Connecting to 10.240.1.146 on port 22, with timeout 10000. Failed to connect via ssh: The kexTimeout (10000 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to 10.240.1.146 on port 22, with timeout 10000. Failed to connect via ssh: The kexTimeout (10000 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to 10.240.1.146 on port 22, with timeout 10000. Failed to connect via ssh: The kexTimeout (10000 ms) expired. Waiting for SSH to come up. Sleeping 5. Connecting to 10.240.1.146 on port 22, with timeout 10000. Connected via SSH. bootstrap() Getting keypair... Using key: jenkins dc:xx:xx:xx -----BEGIN RSA PRIVATE KEY----- MIIEow<private key info> Authenticating as centos Authentication failed. Trying again... Authenticating as centos Authentication failed. Trying again... Authenticating as centos Authentication failed. Trying again... Authenticating as centos Authentication failed. Trying again... Authenticating as centos Authentication failed. Trying again... Authenticating as centos ERROR: Publickey authentication failed. java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:260) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:91) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:107) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:238) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: The connection is closed. at com.trilead.ssh2.auth.AuthenticationManager.deQueue(AuthenticationManager.java:63) at com.trilead.ssh2.auth.AuthenticationManager.getNextMessage(AuthenticationManager.java:86) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:290) ... 10 more Caused by: java.io.IOException: Peer sent DISCONNECT message (reason code 2): Too many authentication failures for centos at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:766) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) ... 1 more

    Jenkins JIRA | 1 year ago | Mike Kingsbury
    java.io.IOException: Publickey authentication failed.

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      Peer sent DISCONNECT message (reason code 2): Too many authentication failures for spacecurve

      at com.trilead.ssh2.transport.TransportManager.receiveLoop()
    2. Trilead
      TransportManager$1.run
      1. com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:750)
      2. com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:475)
      2 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:724)
      1 frame