[JIRA] [core] (JENKINS-19513) Jenkins should reconnect to a node after ChannelClosedException
Title: Message Title Katrin Nilsson commented on JENKINS-19513 Re: Jenkins should reconnect to a node after ChannelClosedException Are there any updates on this? 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-19513) Jenkins should reconnect to a node after ChannelClosedException
Title: Message Title Jacobo Jimenez commented on JENKINS-19513 Re: Jenkins should reconnect to a node after ChannelClosedException Same problem here using real SUSE Linux Enterprise Server 11.3 (x86_64) slaves. 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-19513) Jenkins should reconnect to a node after ChannelClosedException
Mic Le commented on JENKINS-19513 Jenkins should reconnect to a node after ChannelClosedException I am having the same issue when using VMWare Dynamic Slaves. Does anyone have a solution or workaround ? 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] [core] (JENKINS-19513) Jenkins should reconnect to a node after ChannelClosedException
Jonathan Langevin commented on JENKINS-19513 Jenkins should reconnect to a node after ChannelClosedException Same problem for me, using EC2 slaves plugin. 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] [core] (JENKINS-19513) Jenkins should reconnect to a node after ChannelClosedException
Daniel Beck updated JENKINS-19513 Jenkins should reconnect to a node after ChannelClosedException Change By: Daniel Beck (15/Jul/14 8:13 AM) Labels: remoting 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] [core] (JENKINS-19513) Jenkins should reconnect to a node after ChannelClosedException
Ryang Woo Park commented on JENKINS-19513 Jenkins should reconnect to a node after ChannelClosedException same problem Jenkins ver. 1.543 EnvInject 1.88 13:57:23 Started by an SCM change 13:57:23 [EnvInject] - Loading node environment variables. 13:57:23 [EnvInject] - [ERROR] - SEVERE ERROR occurs: hudson.remoting.ChannelClosedException: channel is already closed 13:57:23 ERROR: Publisher hudson.tasks.Mailer aborted due to exception 13:57:23 hudson.remoting.ChannelClosedException: channel is already closed 13:57:23 at hudson.remoting.Channel.send(Channel.java:524) 13:57:23 at hudson.remoting.Request.call(Request.java:129) 13:57:23 at hudson.remoting.Channel.call(Channel.java:722) 13:57:23 at hudson.EnvVars.getRemote(EnvVars.java:396) 13:57:23 at hudson.model.Computer.getEnvironment(Computer.java:908) 13:57:23 at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:29) 13:57:23 at hudson.model.Run.getEnvironment(Run.java:2191) 13:57:23 at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:914) 13:57:23 at hudson.tasks.Mailer.perform(Mailer.java:114) 13:57:23 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 13:57:23 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 13:57:23 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) 13:57:23 at hudson.model.Build$BuildExecution.post2(Build.java:183) 13:57:23 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 13:57:23 at hudson.model.Run.execute(Run.java:1703) 13:57:23 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 13:57:23 at hudson.model.ResourceController.execute(ResourceController.java:88) 13:57:23 at hudson.model.Executor.run(Executor.java:231) 13:57:23 Caused by: java.io.IOException 13:57:23 at hudson.remoting.Channel.close(Channel.java:1003) 13:57:23 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) 13:57:23 at hudson.remoting.PingThread.ping(PingThread.java:120) 13:57:23 at hudson.remoting.PingThread.run(PingThread.java:81) 13:57:23 Caused by: java.util.concurrent.TimeoutException: Ping started on 1393551418747 hasn't completed at 1393551658747 13:57:23 ... 2 more 13:57:23 Email was triggered for: Failure 13:57:23 Sending email for trigger: Failure 13:57:27 ERROR: Error: No workspace found! 13:57:27 Error retrieving environment vars: channel is already closed 13:57:31 Sending email to: cass.p...@chipsnmedia.com aiden@chipsnmedia.com cn...@chipsnmedia.com 13:57:32 Loading slave statistic 13:57:32 Loading slave statisticCODA980_refsw_commit_linuxjob/CODA980_refsw_commit_linux/132/ 13:57:32 Slave statistic loaded 13:57:32 [EnvInject] - [ERROR] - SEVERE ERROR occurs: channel is already closed 13:57:32 Finished: FAILURE 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/groups/opt_out.
