[JIRA] [monitoring-plugin] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title Andreas Kuttruff commented on JENKINS-20947 Re: Failed to monitor for Free Swap Space Here the command line which starts the JNLP Slave .\Java\bin\java -jar -Dhudson.remoting.Launcher.pingIntervalSec=-1 slave.jar -jnlpUrl http://om-ui1.mum.de:8080/computer/01-w7x64DEHS-HyperCAD-S/slave-agent.jnlp -secret b9d8fde46213d8fe26bfc0f7fc36f7. 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] [monitoring-plugin] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title Andreas Kuttruff commented on JENKINS-20947 Re: Failed to monitor for Free Swap Space Hi Stephen, I made the changes you mentioned and got following failure, but I don't know if it is the same failure as JENKINS-25218 Building remotely on 01-w7x64DEHS-HyperCAD-S (DE uitest vm Windows7 64bit hypersnapshot) in workspace C:\JenkinsSlave\workspace\Trunk_Smoke_Sim_HCAD-S_DE FATAL: java.io.EOFException hudson.remoting.RequestAbortedException: java.io.EOFException at hudson.remoting.Request.abort(Request.java:296) at hudson.remoting.Channel.terminate(Channel.java:815) at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(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) at ..remote call to 01-w7x64DEHS-HyperCAD-S(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:980) at hudson.FilePath.act(FilePath.java:969) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1282) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(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) Add Comment
[JIRA] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff commented on JENKINS-20947 Failed to monitor for Free Swap Space I had a closer look into and I recongized that there was a log entry (see below) after closing the slave cmd. If my interpretation is right the slave hangs during a SVN action. I have to check if we have a SVN problem here. Maybe it was not the same problem as before. Building remotely on 01-w7x64ENHSSw2013 (vm EN SolidWorks2013 uitest hypersnaphot Windows7 64bit) in workspace C:\JenkinsSlave\workspace\2014.2_Smoketest_EN_Simulation_SolidWorks2013 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.FilePath.act(FilePath.java:909) at hudson.FilePath.act(FilePath.java:893) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:909) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:844) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.Channel$2.terminate(Channel.java:483) at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:195) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:581) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(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: Failed to abort This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff commented on JENKINS-20947 Failed to monitor for Free Swap Space Daniel: I am starting the slave via cmd which copies the latest slave.jar from jenknins server before executing the slave. Slave Log jar version entry: JNLP agent connected from /192.168.6.190 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.43 This is a Windows slave Slave successfully connected and online MANIFEST.MF Header: Manifest-Version: 1.0 Trusted-Library: true Application-Name: Jenkins Remoting Agent Build-Jdk: 1.7.0_07 Built-By: kohsuke Permissions: all-permissions Created-By: Apache Maven Main-Class: hudson.remoting.Launcher Version: 2.43 Codebase: * Archiver-Version: Plexus Archiver Java Version: java version "1.7.0_55" Java(TM) SE Runtime Environment (build 1.7.0_55-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff commented on JENKINS-20947 Failed to monitor for Free Swap Space Upgrading Jenkins to version 1.568 (including fix of JENKINS-22932) doesn't solve my problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff commented on JENKINS-20947 Failed to monitor for Free Swap Space Daniel: Thank you for the hint. Sometimes Interpretation of log entries is difficult. I think issue 22932 is a good candidate for my Problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff updated JENKINS-20947 Failed to monitor for Free Swap Space For me this behaviour is critical because, the slave doesn't work anymore. Change By: Andreas Kuttruff (11/Jun/14 11:34 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff updated JENKINS-20947 Failed to monitor for Free Swap Space Change By: Andreas Kuttruff (10/Jun/14 6:10 AM) Component/s: master-slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [monitoring] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff updated JENKINS-20947 Failed to monitor for Free Swap Space I am running also massively into this issue rearding running VM's on demand which run slaves. More Information see attached PDF file 'MonitorFreeSwapSpace.pdf' Change By: Andreas Kuttruff (06/Jun/14 8:30 AM) Attachment: MonitorFreeSwapSpace.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
