-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.642.4 (DockerHub 'jenkins' image latest)
Amazon EC2 plugin 1.31
Windows slave Java Runtime 8.0.73
Windows AMI based off MS2012R2-EBS-HVM
When starting the AWS Windows slave, failure occurs with:
Apr 05, 2016 8:12:55 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:00 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:05 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:10 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:10 PM null FINER: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is ready ITKAWSWindows (i-0234e203d06253ae7) booted at 1459901636000 Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-54-152-165-170.compute-1.amazonaws.com(54.152.165.170) with WinRM as Administrator WinRM service responded. Waiting for WinRM service to stabilize on ITKAWSWindows (i-0234e203d06253ae7) WinRM should now be ok on ITKAWSWindows (i-0234e203d06253ae7) Connected with WinRM. Creating tmp directory if it does not exist slave.jar sent remotely. Bootstrapping it <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.53.3 This is a Windows slave ERROR: Connection terminated java.io.IOException: Pipe closed at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260) at java.io.PipedInputStream.receive(PipedInputStream.java:226) at java.io.PipedOutputStream.write(PipedOutputStream.java:149) at java.io.OutputStream.write(OutputStream.java:75) at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:93) at hudson.remoting.ChunkedOutputStream.drain(ChunkedOutputStream.java:89) at hudson.remoting.ChunkedOutputStream.write(ChunkedOutputStream.java:58) at java.io.OutputStream.write(OutputStream.java:75) at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:45) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) at hudson.remoting.Channel.send(Channel.java:582) at hudson.remoting.Channel.close(Channel.java:1156) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118) at hudson.remoting.PingThread.run(PingThread.java:96) Ouch: hudson.remoting.RequestAbortedException: java.io.IOException: Pipe closed at hudson.remoting.Request.abort(Request.java:297) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.Channel.close(Channel.java:1160) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118) at hudson.remoting.PingThread.run(PingThread.java:96) at ......remote call to ITKAWSWindows (i-0234e203d06253ae7)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:32) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:573) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:381) at hudson.plugins.ec2.win.EC2WindowsLauncher.launch(EC2WindowsLauncher.java:68) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:100) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253) 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: Pipe closed at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260) at java.io.PipedInputStream.receive(PipedInputStream.java:226) at java.io.PipedOutputStream.write(PipedOutputStream.java:149) at java.io.OutputStream.write(OutputStream.java:75) at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:93) at hudson.remoting.ChunkedOutputStream.drain(ChunkedOutputStream.java:89) at hudson.remoting.ChunkedOutputStream.write(ChunkedOutputStream.java:58) at java.io.OutputStream.write(OutputStream.java:75) at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:45) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) at hudson.remoting.Channel.send(Channel.java:582) at hudson.remoting.Channel.close(Channel.java:1156) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118) at hudson.remoting.PingThread.run(PingThread.java:96) ERROR: Connection terminated
A successful connection occur if the initialization is cancelled, then I manually launch the slave agent via the Jenkins GUI.
- is caused by
-
JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call
- Closed