[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-05-27 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 
 
Here is more: 
ERROR: Connection terminated java.io.IOException: Pipe closed at java.io.PipedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Failed to install restarter Ouch: Connection terminated hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) at ..remote call to Jenkins Slave (i-0f31fdf7)(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.systemd_slave_installer.SlaveInstallerFactoryImpl.createIfApplicable(SlaveInstallerFactoryImpl.java:33) at org.jenkinsci.modules.slave_installer.SlaveInstallerFactory.createIfApplicable(SlaveInstallerFactory.java:29) at org.jenkinsci.modules.slave_installer.SlaveInstallerFactory.createFor(SlaveInstallerFactory.java:46) at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:30) 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:69) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:1074) at hudson.remoting.Channel$CloseCommand.(Channel.java:1072) at hudson.remoting.Channel.close(Channel.java:1156) at hudson.remoting.Channel.close(Channel.java:1138) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1079) ... 2 more hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1080) at hudson.remoting.Channel$1.handle(Channel.java:501) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) at ..remote call to Jenkins Slave (i-0f31fdf7)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) 

[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-05-27 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 
 
Correct, i'm getting it right now with 1.33 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-05-27 Thread franc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-34044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 
 
Can you make this happen on 1.33 (the current release)? There have been many fixes since 1.31. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-05-27 Thread bstew...@novetta.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brendan Stewart commented on  JENKINS-34044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 
 
I'm seeing this also, occurs frequently enough that i can't get my builds completed. I'm using the aws cli s3 for copying files to my slaves (as a powershell build step) when this occurs. 
14:25:27 Agent went offline during the build 14:28:45 ERROR: Connection was broken: java.io.IOException: Pipe closed 14:28:45 at java.io.PipedInputStream.checkStateForReceive(Unknown Source) 14:28:45 at java.io.PipedInputStream.receive(Unknown Source) 14:28:45 at java.io.PipedOutputStream.write(Unknown Source) 14:28:45 at java.io.OutputStream.write(Unknown Source) 14:28:45 at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:93) 14:28:45 at hudson.remoting.ChunkedOutputStream.drain(ChunkedOutputStream.java:89) 14:28:45 at hudson.remoting.ChunkedOutputStream.write(ChunkedOutputStream.java:58) 14:28:45 at java.io.OutputStream.write(Unknown Source) 14:28:45 at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:45) 14:28:45 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) 14:28:45 at hudson.remoting.Channel.send(Channel.java:582) 14:28:45 at hudson.remoting.Channel.close(Channel.java:1156) 14:28:45 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:119) 14:28:45 at hudson.remoting.PingThread.run(PingThread.java:96) 14:28:45  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-04-05 Thread matt.mccorm...@kitware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt McCormick commented on  JENKINS-34044 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 
 
Build script for the AMI: 
 https://github.com/InsightSoftwareConsortium/ITKBuildRobot/tree/master/MS2012R2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed

2016-04-05 Thread matt.mccorm...@kitware.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt McCormick created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34044 
 
 
 
  EC2 Plugin: Windows: java.io.IOException: Pipe closed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 2016/Apr/06 12:43 AM 
 
 
 

Environment:
 

 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 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Matt McCormick 
 
 
 
 
 
 
 
 
 
 
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