Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15609

New created EC2 instance SCP Error

    Details

    • Similar Issues:

      Description

      When starting the new EC2 instance as slave node encountered a problem:

      java full version "1.6.0_24-b24"
      Copying slave.jar
      ERROR: Error during SCP transfer.
      java.io.IOException: Error during SCP transfer.
      	at com.trilead.ssh2.SCPClient.put(SCPClient.java:523)
      	at com.trilead.ssh2.SCPClient.put(SCPClient.java:476)
      	at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:126)
      	at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:57)
      	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:636)
      Caused by: java.io.IOException: Remote scp terminated unexpectedly.
      	at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50)
      	at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140)
      	at com.trilead.ssh2.SCPClient.put(SCPClient.java:519)
      	... 9 more
      

      On Master Jenkins the Error logs says"

      ct 24, 2012 6:06:43 AM hudson.slaves.NodeProvisioner update
      WARNING: Provisioned slave Jenkins Slaves (ami-4afe4623) failed to launch
      java.util.concurrent.ExecutionException: java.io.IOException: Slave failed to connect, even though the launcher didn't report it. See the log output for details.
      	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
      	at java.util.concurrent.FutureTask.get(FutureTask.java:111)
      	at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:253)
      	at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:239)
      	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:636)
      Caused by: java.io.IOException: Slave failed to connect, even though the launcher didn't report it. See the log output for details.
      	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:221)
      	... 5 more
      
      

      But re-lunching the slave nodes it runs properly.

      Is this a bug for EC2 plugin?

      Current Jenkins version 1.487 and Amazon EC2 Plugins is 1.17

      Thanks,

      Vinz

        Attachments

          Activity

          Hide
          francisu Francis Upton added a comment -

          Downgrading to minor since it it's quite old and intermittent.

          Show
          francisu Francis Upton added a comment - Downgrading to minor since it it's quite old and intermittent.
          Hide
          francisu Francis Upton added a comment -

          old

          Show
          francisu Francis Upton added a comment - old

            People

            • Assignee:
              francisu Francis Upton
              Reporter:
              vinzpr vinz r
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: