[JIRA] (JENKINS-19107) Nodes Unable to monitor free temp space

2017-01-12 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor commented on  JENKINS-19107  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nodes Unable to monitor free temp space   
 

  
 
 
 
 

 
 Pavel this is still an issue and agree exactly with your comment I have experienced the same.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-20947) Failed to monitor for Free Swap Space

2017-01-12 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor commented on  JENKINS-20947  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to monitor for Free Swap Space   
 

  
 
 
 
 

 
 Please someone help still experiencing this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-20947) Failed to monitor for Free Swap Space

2016-11-22 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20947  
 
 
  Failed to monitor for Free Swap Space   
 

  
 
 
 
 

 
Change By: 
 Matt Taylor  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-20947) Failed to monitor for Free Swap Space

2016-11-03 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20947  
 
 
  Failed to monitor for Free Swap Space   
 

  
 
 
 
 

 
Change By: 
 Matt Taylor  
 
 
Attachment: 
 jenkins.err.zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-20947) Failed to monitor for Free Swap Space

2016-11-03 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor commented on  JENKINS-20947  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to monitor for Free Swap Space   
 

  
 
 
 
 

 
 Experiencing this same issue with a slave that is used on demand.  jenkins.err.zip   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-39486) failed to monitor for free swap space for nodes that use on demand

2016-11-03 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39486  
 
 
  failed to monitor for free swap space for nodes that use on demand   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins.err.zip  
 
 
Components: 
 core  
 
 
Created: 
 2016/Nov/03 6:20 PM  
 
 
Labels: 
 jenkins slave 2.0 windows  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matt Taylor  
 

  
 
 
 
 

 
 I have several nodes that are experiencing this failed to monitor for free swap space. Some of them are unable to even begin the job itself while others are shutting down the agent in the middle of the job while running in both cases it unacceptable and really disrupts our release and testing process. I have attached my error log and you can see it happens with node GRW7-64-B and PRW10-32-A  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-28536) Deploy VM from Template no longer working

2016-07-25 Thread mtay...@opto22.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Taylor commented on  JENKINS-28536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deploy VM from Template no longer working   
 

  
 
 
 
 

 
 I can't figure this out has anyone else figured it out? Provisioned slave GRW10-64 failed to launch org.jenkinsci.plugins.vsphere.tools.VSphereException: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "GRW10-64-B"! Does "GRW10-64_5d7c0e81-2573-4c14-8101-b9ad3fe8fe40" already exist? Clone task ended with status error at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:169) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneVm(VSphere.java:129) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:250) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:274) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:272) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "GRW10-64-B"! Does "GRW10-64_5d7c0e81-2573-4c14-8101-b9ad3fe8fe40" already exist? Clone task ended with status error at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:164) ... 10 more  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you 

[JIRA] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor edited a comment on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 Experiencing the same issue:Jenkins 1.654 Apr 20, 2016 10:33:53 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted connection #15 from /10.192.0.32:49188Apr 20, 2016 10:36:17 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog[GRW7-64-A] Powering down hardApr 20, 2016 10:36:18 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosedNioChannelHub keys=3 gen=482437: Computer.threadPoolForRemoting [#6] for GRW7-64-A terminatedjava.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@f5709[name=GRW7-64-A] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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: java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 7 moreApr 20, 2016 10:36:37 AM WARNING org.jenkinsci.remoting.nio.NioChannelHub runCommunication problemjava.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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)Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog[GRW7-64-A] Running disconnect procedure...Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog[GRW7-64-A] Shutting down Virtual Machine...Apr 20, 2016 10:36:37 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosedNioChannelHub keys=2 gen=486936: Computer.threadPoolForRemoting [#6] for GRW7-64-A terminatedjava.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@1fc9696[name=GRW7-64-A] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at 

[JIRA] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor commented on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 
Apr 20, 2016 10:33:53 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted connection #15 from /10.192.0.32:49188 Apr 20, 2016 10:36:17 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Powering down hard 
Apr 20, 2016 10:36:18 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed NioChannelHub keys=3 gen=482437: Computer.threadPoolForRemoting 6 for GRW7-64-A terminated java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@f5709[name=GRW7-64-A] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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: java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 7 more 
Apr 20, 2016 10:36:37 AM WARNING org.jenkinsci.remoting.nio.NioChannelHub run Communication problem java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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) 
Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Running disconnect procedure... 
Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Shutting down Virtual Machine... 
Apr 20, 2016 10:36:37 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed NioChannelHub keys=2 gen=486936: Computer.threadPoolForRemoting 6 for GRW7-64-A terminated java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@1fc9696[name=GRW7-64-A] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at 

[JIRA] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27251 
 
 
 
  windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matt Taylor 
 
 
 

Comment:
 
 l 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor edited a comment on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 [^jenkins-logs.zip][^jenkins-logs.zip] l 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor edited a comment on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 Same issues here:Apr 20, 2016 10:36:37 AM WARNING org.jenkinsci.remoting.nio.NioChannelHub runCommunication problemjava.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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)Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [ GRW7-64-A] Running disconnect procedure...Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog[GRW7-64-A] Shutting down Virtual Machine...Apr 20, 2016 10:36:37 AM WARNING ^  jenkins .slaves.JnlpSlaveAgentProtocol$Handler$1 onClosedNioChannelHub keys=2 gen=486936: Computer.threadPoolForRemoting [#6] for GRW7 - 64-A terminatedjava logs . io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@1fc9696[name=GRW7-64-A zip ]  at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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: java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 7 moreAnd this:Apr 20, 2016 10:33:53 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted connection #15 from /10.192.0.32:49188Apr 20, 2016 10:36:17 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [ GRW7-64-A] Powering down hardApr 20, 2016 10:36:18 AM WARNING ^  jenkins .slaves.JnlpSlaveAgentProtocol$Handler$1 onClosedNioChannelHub keys=3 gen=482437: Computer.threadPoolForRemoting [#6] for GRW7 - 64-A terminatedjava logs . io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@f5709[name=GRW7-64-A zip ]  at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) 

[JIRA] [core] (JENKINS-27251) windows slaves disconnect during build

2016-04-20 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor commented on  JENKINS-27251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows slaves disconnect during build  
 
 
 
 
 
 
 
 
 
 
Same issues here: 
Apr 20, 2016 10:36:37 AM WARNING org.jenkinsci.remoting.nio.NioChannelHub run Communication problem java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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) 
Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Running disconnect procedure... 
Apr 20, 2016 10:36:37 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Shutting down Virtual Machine... 
Apr 20, 2016 10:36:37 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed NioChannelHub keys=2 gen=486936: Computer.threadPoolForRemoting 6 for GRW7-64-A terminated java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@1fc9696[name=GRW7-64-A] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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: java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 7 more 
And this: 
Apr 20, 2016 10:33:53 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted connection #15 from /10.192.0.32:49188 Apr 20, 2016 10:36:17 AM INFO org.jenkinsci.plugins.vSphereCloud InternalLog [GRW7-64-A] Powering down hard 
Apr 20, 2016 10:36:18 AM WARNING jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed NioChannelHub keys=3 gen=482437: Computer.threadPoolForRemoting 6 for GRW7-64-A terminated java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@f5709[name=GRW7-64-A] at 

[JIRA] [core] (JENKINS-28731) Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state

2015-06-08 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor commented on  JENKINS-28731 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state  
 
 
 
 
 
 
 
 
 
 
I make sure that the Jenkins service is not started automatically as a service. To do so, I open the “Services” tool (which is part of the “Administrative Tools” in the control panel), choose “Jenkins” service, stop the service, and set the “Startup type” to disabled: 
Then, 
Jenkins can be started manually using following command (from the installation folder): 

 

java -jar jenkins.war
 

 
The reason being as Jenkins is normally started as a Windows service, it does not have sufficient rights to start UI-applications. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28731) Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state

2015-06-08 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor commented on  JENKINS-28731 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state  
 
 
 
 
 
 
 
 
 
 
No sorry I was just stating the steps I am taking, Still does not work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-28731) Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state

2015-06-03 Thread mtay...@opto22.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Taylor created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28731 
 
 
 
  Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 03/Jun/15 11:50 PM 
 
 
 

Environment:
 

 Jenkins 1.616  Windows 8.1 64bit  VirtualBox 4.3.28 
 
 
 

Labels:
 

 jenkins windows build job gui virtualbox 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Matt Taylor 
 
 
 
 
 
 
 
 
 
 
 == Symptom == Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes. 
 == Details == Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state. 
 However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. 
 Also another workaround is to have