[JIRA] (JENKINS-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Roger Bernier assigned an issue to Roger Bernier Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Roger Bernier Assignee: Francisco Fernández Roger Bernier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Francisco Fernández updated JENKINS-37812 PR merged Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Francisco Fernández Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Francisco Fernández updated JENKINS-37812 Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Francisco Fernández Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Francisco Fernández assigned an issue to Francisco Fernández Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Change By: Francisco Fernández Assignee: David van Laatum Francisco Fernández Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title Francisco Fernández started work on JENKINS-37812 Change By: Francisco Fernández Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title George Sakhnovsky edited a comment on JENKINS-37812 Re: No notification re. failed job if agent goes offline during the build If it's helpful to anyone: As a workaround, we installed the Mail Watcher Plugin and configured it to send e-mail alerts on node online status changes. This gave us some visibility into the scenario of jobs failing quietly due to agent issues . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title George Sakhnovsky edited a comment on JENKINS-37812 Re: No notification re. failed job if agent goes offline during the build If it's helpful to anyone: As a workaround, we installed the Mail Watcher Plugin and configured it to send e-mail alerts on node online status changes. This eliminated gave us some visibility into the scenario of jobs failing quietly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title George Sakhnovsky commented on JENKINS-37812 Re: No notification re. failed job if agent goes offline during the build If it's helpful to anyone: As a workaround, we installed the Mail Watcher Plugin and configured it to send e-mail alerts on node online status changes. This eliminated the scenario of jobs failing quietly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title
Chris Wilson commented on JENKINS-37812
Re: No notification re. failed job if agent goes offline during the build
This is happening to us too. Here is a stack trace. [Sorry if this is badly formatted, I tried hard to make the comment editor treat it as preformatted/monospace but it looks like I am unable to.] {{ FATAL: command execution failed java.io.IOException at hudson.remoting.Channel.close(Channel.java:1402) at hudson.remoting.Channel.close(Channel.java:1358) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:745) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:712) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at jenkins.model.Jenkins.access$2000(Jenkins.java:302) at jenkins.model.Jenkins$20.run(Jenkins.java:3328) at hudson.model.Queue._withLock(Queue.java:1370) at hudson.model.Queue.withLock(Queue.java:1247) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3322) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3197) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:898) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:545) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:873) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:355) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1507) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1471) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:927) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:271) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:523) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:307) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on xxx- failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:902) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:281) at com.sun.proxy.$Proxy57.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at
[JIRA] (JENKINS-37812) No notification re. failed job if agent goes offline during the build
Title: Message Title George Sakhnovsky created an issue Jenkins / JENKINS-37812 No notification re. failed job if agent goes offline during the build Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Aug/30 2:10 PM Environment: awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.101.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.101.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.101.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_101-mockbuild_2016_04_26_18_10-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_101 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.95-b01 JENKINS_HOME /var/lib/jenkins jna.loaded false jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna6131462595576184842.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 4.4.5-15.26.amzn1.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path
