Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-24761

Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • remoting

      My Jenkins job is failing continuously with this error, earlier it used to pass. I am getting the error on the Jenkins job execution page, but the job is still running on windows node. I don't know if it is Jenkins problem or windows slave's issue.
      Here I am pasting the logs:

      c:\jenkins\workspace\NSClient-Automation-1>FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
      hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
      	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.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)
      	at com.sun.proxy.$Proxy56.join(Unknown Source)
      	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956)
      	at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)
      	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)
      	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:756)
      	at hudson.model.Build$BuildExecution.build(Build.java:198)
      	at hudson.model.Build$BuildExecution.doRun(Build.java:159)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
      	at hudson.model.Run.execute(Run.java:1706)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:88)
      	at hudson.model.Executor.run(Executor.java:232)
      Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
      	at hudson.remoting.Request.abort(Request.java:299)
      	at hudson.remoting.Channel.terminate(Channel.java:802)
      	at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951)
      	at hudson.remoting.Channel$2.handle(Channel.java:475)
      	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
      Caused by: hudson.remoting.Channel$OrderlyShutdown
      	... 3 more
      Caused by: Command close created at
      	at hudson.remoting.Command.<init>(Command.java:56)
      	at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:921)
      	at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:919)
      	at hudson.remoting.Channel.close(Channel.java:1002)
      	at hudson.remoting.Channel.close(Channel.java:985)
      	at hudson.remoting.Channel$CloseCommand.execute(Channel.java:926)
      	at hudson.remoting.Channel$2.handle(Channel.java:461)
      	... 1 more
      

      Jenkins ver. 1.565.2

        1. stacktrace-2.32.2.log
          3 kB
          Peter Rifel
        2. stacktrace-2.46.1.log
          2 kB
          Peter Rifel

          [JENKINS-24761] Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown

          Hi, this project called "Jenkins", not "junkins" or "junking". Thanks.

          Kanstantsin Shautsou added a comment - Hi, this project called "Jenkins", not "junkins" or "junking". Thanks.

          Daniel Beck added a comment -

          Does this issue still occur? Does it occur after a Jenkins restart? Is only one specific job affected? Only one specific slave? Is it sufficient to just disconnect and reconnect the slave to get things working again?

          Daniel Beck added a comment - Does this issue still occur? Does it occur after a Jenkins restart? Is only one specific job affected? Only one specific slave? Is it sufficient to just disconnect and reconnect the slave to get things working again?

          wbauer added a comment -

          I see this as well, master is RHEL 6.5 linux jenkins version 1.572 and only windows slaves are affected (look s like they loose connection sporadically). Mac and Linux slaves are fine. I was not able to consistently reproduce or pinpoint how, when or why this happens yet - due to time constraints.

          wbauer added a comment - I see this as well, master is RHEL 6.5 linux jenkins version 1.572 and only windows slaves are affected (look s like they loose connection sporadically). Mac and Linux slaves are fine. I was not able to consistently reproduce or pinpoint how, when or why this happens yet - due to time constraints.

          Gil Zellner added a comment -

          Happens to me too. Master is Ubuntu 12.04 x64 on AWS, Running Jenkins 1.594
          Slaves are Mac OS Yosemite.

          Gil Zellner added a comment - Happens to me too. Master is Ubuntu 12.04 x64 on AWS, Running Jenkins 1.594 Slaves are Mac OS Yosemite.

          David Rubio added a comment -

          Same problem here. Master is Ubuntu 12.04 x64 with Jenkins 1.597. The slave is a Windows 7 machine.

          David Rubio added a comment - Same problem here. Master is Ubuntu 12.04 x64 with Jenkins 1.597. The slave is a Windows 7 machine.

          I've also seen this problem intermittently connecting from an Ubuntu 12.04 master to slaves also running Ubuntu 12.04. The problem clears up after a slave connection restart.

          Carter Sanders added a comment - I've also seen this problem intermittently connecting from an Ubuntu 12.04 master to slaves also running Ubuntu 12.04. The problem clears up after a slave connection restart.

          Kevin Cheng added a comment -

          We are seeing this randomly as well. I am not sure if it is related to the reliability of the network between master and slave. We use Jenkins v 1.596.1. Master is running Ubuntu 12.04 and slave is running Ubuntu 14.01

          Note: Our master runs in datacenter while most of the slaves are running in AWS for scalability reason. The connection between DC and AWS is through a dual 10GB direct link.

          The reason I ask whether this issue might be impacted by the network reliability is that we also have one other setup 100% in AWS (both master and slaves) and we only see this issue in a about 1:100 ratio comparing to the "DC-AWS" setup.

          Kevin Cheng added a comment - We are seeing this randomly as well. I am not sure if it is related to the reliability of the network between master and slave. We use Jenkins v 1.596.1. Master is running Ubuntu 12.04 and slave is running Ubuntu 14.01 Note: Our master runs in datacenter while most of the slaves are running in AWS for scalability reason. The connection between DC and AWS is through a dual 10GB direct link. The reason I ask whether this issue might be impacted by the network reliability is that we also have one other setup 100% in AWS (both master and slaves) and we only see this issue in a about 1:100 ratio comparing to the "DC-AWS" setup.

          Marc Fournier added a comment -

          Same here, using 1.596.2. The slaves are launched on demand by the digitalocean plugin.

          Marc Fournier added a comment - Same here, using 1.596.2. The slaves are launched on demand by the digitalocean plugin.

          Sean Cullen added a comment -

          Any update on this folks?

          Sean Cullen added a comment - Any update on this folks?

          Jason Dolan added a comment -

          We have the same issue here running Jenkins 1.642.4 on linux-x64 (CentOS 6) while running Windows nodes.

          danielbeck integer

          • Does this issue still occur? Yes, for us at least.
          • Does it occur after a Jenkins restart? We don't know and given that it failed 7 hours into a large test run, it's a bit time-consuming to turn this around to find out. With respect, I'm reluctant to spend more time on it until I know if this JIRA issue will be updated / viewed by you.
          • Is only one specific job affected? We have only one job running windows nodes so that question is not applicable.
          • Only one specific slave? We only have one Windows AMI slave so we are not in a position to try other Windows slaves.
          • Is it sufficient to just disconnect and reconnect the slave to get things working again? This is not applicable as the Window slaves are spun up on demand by our Amazon EC2 plugin.

          It would be great if we can have an update on this, given it's been over 2 years and 8 other people have appeared to encountered the same issue, even if the update is just to say you don't have the time to fix it and / or if it is fixed in a later version of Jenkins, thanks : )

          Here is the error we encounter:
          hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
          at hudson.remoting.Request.abort(Request.java:297)
          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 jck-win-i586 (i-0a3184e25e48f202c)(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 hudson.FilePath.act(FilePath.java:979)
          at hudson.FilePath.act(FilePath.java:968)
          at hudson.FilePath.deleteRecursive(FilePath.java:1170)
          at org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:68)
          at org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:61)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
          at hudson.security.ACL.impersonate(ACL.java:213)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)
          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.<init>(Command.java:56)
          at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1074)
          at hudson.remoting.Channel$CloseCommand.<init>(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

          Jason Dolan added a comment - We have the same issue here running Jenkins 1.642.4 on linux-x64 (CentOS 6) while running Windows nodes. danielbeck integer Does this issue still occur? Yes, for us at least. Does it occur after a Jenkins restart? We don't know and given that it failed 7 hours into a large test run, it's a bit time-consuming to turn this around to find out. With respect, I'm reluctant to spend more time on it until I know if this JIRA issue will be updated / viewed by you. Is only one specific job affected? We have only one job running windows nodes so that question is not applicable. Only one specific slave? We only have one Windows AMI slave so we are not in a position to try other Windows slaves. Is it sufficient to just disconnect and reconnect the slave to get things working again? This is not applicable as the Window slaves are spun up on demand by our Amazon EC2 plugin. It would be great if we can have an update on this, given it's been over 2 years and 8 other people have appeared to encountered the same issue, even if the update is just to say you don't have the time to fix it and / or if it is fixed in a later version of Jenkins, thanks : ) Here is the error we encounter: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:297) 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 jck-win-i586 (i-0a3184e25e48f202c)(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 hudson.FilePath.act(FilePath.java:979) at hudson.FilePath.act(FilePath.java:968) at hudson.FilePath.deleteRecursive(FilePath.java:1170) at org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:68) at org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:61) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 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.<init>(Command.java:56) at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1074) at hudson.remoting.Channel$CloseCommand.<init>(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

          Daniel Beck added a comment -

          1.642.4

          1.642.x has been unsupported since April. We've since released 1.651.x, 2.7.x and 2.19.x LTS lines, and are about to release 2.32.1 which also includes a major update to the remoting library with improved stability and diagnostics.

          Daniel Beck added a comment - 1.642.4 1.642.x has been unsupported since April. We've since released 1.651.x, 2.7.x and 2.19.x LTS lines, and are about to release 2.32.1 which also includes a major update to the remoting library with improved stability and diagnostics.

          Jason Dolan added a comment -

          danielbeck

          Thanks Daniel and for the quick reply - much obliged! We recently attempted an upgrade to the latest version of Jenkins including our plugins but had to abandon it as there were too many compatibility issues for us to resolve in our upgrade window between one or more of the following: Jenkins / our plugins / our pipeline plugin infrastructure / Jenkinsfile syntax. We plan on revisiting the upgrade in the coming weeks / months. We'll definitely wait for that update before attempting another Jenkins upgrade. Given that we'll still need our Windows nodes test jobs, we can check if it still occurs in later versions.

          Jason Dolan added a comment - danielbeck Thanks Daniel and for the quick reply - much obliged! We recently attempted an upgrade to the latest version of Jenkins including our plugins but had to abandon it as there were too many compatibility issues for us to resolve in our upgrade window between one or more of the following: Jenkins / our plugins / our pipeline plugin infrastructure / Jenkinsfile syntax. We plan on revisiting the upgrade in the coming weeks / months. We'll definitely wait for that update before attempting another Jenkins upgrade. Given that we'll still need our Windows nodes test jobs, we can check if it still occurs in later versions.

          Peter Rifel added a comment - - edited

          danielbeck I am experiencing this issue as well. I am running 2.46.1 LTS with the Amazon ECS Plugin 1.11. I updated to 2.46.1 today and continued to experience the error after upgrading from 2.32.2.

          We only have agents in ECS so experimenting with reconnecting the agents is not applicable. It is very sporadic but has occurred on as many as 3 job retries in a row and across many jobs and multiple masters.

          I thought that the Remoting / JNLP4 upgrades in 2.46.1 might fix the problem but they did not. 

          Attached are the two stacktraces from stacktrace-2.32.2.log and stacktrace-2.46.1.log. I tried disabling the jnlp4 agent protocols in 2.46.1 but we continued to get a similar stacktrace to the one in 2.32.2. I also tried disabling the Response Time node monitoring but that did not help. 

          I realize that the sporadicalness of the issue makes it difficult to repro, but do you have suggestions on how to go about exposing the underlying problem?

          Peter Rifel added a comment - - edited danielbeck I am experiencing this issue as well. I am running 2.46.1 LTS with the Amazon ECS Plugin 1.11. I updated to 2.46.1 today and continued to experience the error after upgrading from 2.32.2. We only have agents in ECS so experimenting with reconnecting the agents is not applicable. It is very sporadic but has occurred on as many as 3 job retries in a row and across many jobs and multiple masters. I thought that the Remoting / JNLP4 upgrades in 2.46.1 might fix the problem but they did not.  Attached are the two stacktraces from stacktrace-2.32.2.log and stacktrace-2.46.1.log . I tried disabling the jnlp4 agent protocols in 2.46.1 but we continued to get a similar stacktrace to the one in 2.32.2. I also tried disabling the Response Time node monitoring but that did not help.  I realize that the sporadicalness of the issue makes it difficult to repro, but do you have suggestions on how to go about exposing the underlying problem?

          Nickolay Rumyantsev added a comment - - edited

          I observed the same error when my Jenkins was restarted during stash pipeline command execution. The job resumed and the failed with this stacktrace:

          Command close created at at hudson.remoting.Command.<init>(Command.java:60) at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1123) at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1121) at hudson.remoting.Channel.close(Channel.java:1281) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1128) Caused: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) at hudson.remoting.Channel$1.handle(Channel.java:527) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:896) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) at hudson.remoting.Channel$1.handle(Channel.java:527) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) at ......remote call to ecs_defvkit_10.244.130.150(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:829) at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:974) at hudson.FilePath.archive(FilePath.java:456) at org.jenkinsci.plugins.workflow.flow.StashManager.stash(StashManager.java:100) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:103) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:91) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
          

          Nickolay Rumyantsev added a comment - - edited I observed the same error when my Jenkins was restarted during stash pipeline command execution. The job resumed and the failed with this stacktrace: Command close created at at hudson.remoting.Command.<init>(Command.java:60) at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1123) at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1121) at hudson.remoting.Channel.close(Channel.java:1281) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1128) Caused: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) at hudson.remoting.Channel$1.handle(Channel.java:527) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:896) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) at hudson.remoting.Channel$1.handle(Channel.java:527) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) at ......remote call to ecs_defvkit_10.244.130.150(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:829) at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:974) at hudson.FilePath.archive(FilePath.java:456) at org.jenkinsci.plugins.workflow.flow.StashManager.stash(StashManager.java:100) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:103) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:91) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang. Thread .run( Thread .java:745)

          Oleg Nenashev added a comment -

          nickolayr

          Could you please provide the following info?:

          • Jenkins System log for the time of outage
          • Agent log (+/- 15min)

          On the job side everything looks to be correct, the disconnect is being triggered by something else

          Oleg Nenashev added a comment - nickolayr Could you please provide the following info?: Jenkins System log for the time of outage Agent log (+/- 15min) On the job side everything looks to be correct, the disconnect is being triggered by something else

          kevin huang added a comment - - edited

          I use jenkins with docker cloud, but I often meet this problem.

          The Jenkins Version is Jenkins ver. 2.46.2, slave version is 3.7,system is ubuntu 14.04

          When the task is running, it will throw this problem suddenly:

          [WS-CLEANUP] Deleting project workspace...
          FATAL: java.nio.channels.ClosedChannelException
          java.nio.channels.ClosedChannelException
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
          	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
          	at hudson.remoting.Channel.close(Channel.java:1295)
          	at hudson.remoting.Channel.close(Channel.java:1263)
          	at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:704)
          	at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96)
          	at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:502)
          	at hudson.remoting.Channel.terminate(Channel.java:917)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
          	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
          	at hudson.remoting.Channel.close(Channel.java:1295)
          	at hudson.remoting.Channel.close(Channel.java:1263)
          	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:566)
          	at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:172)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState$4.invoke(JnlpConnectionState.java:421)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:312)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:418)
          	at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler$1.run(JnlpProtocol4Handler.java:334)
          	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
          	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          	at java.lang.Thread.run(Thread.java:745)
          Caused: hudson.remoting.RequestAbortedException
          	at hudson.remoting.Request.abort(Request.java:307)
          	at hudson.remoting.Channel.terminate(Channel.java:896)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
          	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
          	at hudson.remoting.Channel.close(Channel.java:1295)
          	at hudson.remoting.Channel.close(Channel.java:1263)
          	at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:704)
          	at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96)
          	at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:502)
          	at hudson.remoting.Channel.terminate(Channel.java:917)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
          	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
          	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)
          	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)
          	at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)
          	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311)
          	at hudson.remoting.Channel.close(Channel.java:1295)
          	at hudson.remoting.Channel.close(Channel.java:1263)
          	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:566)
          	at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:172)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState$4.invoke(JnlpConnectionState.java:421)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:312)
          	at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:418)
          	at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler$1.run(JnlpProtocol4Handler.java:334)
          	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
          	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          	at java.lang.Thread.run(Thread.java:745)
          	at ......remote call to JNLP4-connect connection from 10.25.21.21/10.25.21.21:49874(Native Method)
          	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
          	at hudson.remoting.Request.call(Request.java:172)
          	at hudson.remoting.Channel.call(Channel.java:829)
          	at hudson.FilePath.act(FilePath.java:985)
          	at hudson.FilePath.act(FilePath.java:974)
          	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
          	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833)
          	at hudson.scm.SCM.checkout(SCM.java:496)
          	at hudson.model.AbstractProject.checkout(AbstractProject.java:1281)
          	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
          	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
          	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
          	at hudson.model.Run.execute(Run.java:1728)
          	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          	at hudson.model.ResourceController.execute(ResourceController.java:98)
          	at hudson.model.Executor.run(Executor.java:405)
          Collecting metadata...
          Metadata collection done.
          Email was triggered for: Failure - Any
          Sending email for trigger: Failure - Any
          Error evaluating token: Workspace is not accessible
          Error evaluating token: Workspace is not accessible
          ERROR: Error: No workspace found!
          Error evaluating token: Workspace is not accessible
          Error evaluating token: Workspace is not accessible
          Error evaluating token: Workspace is not accessible
          

          kevin huang added a comment - - edited I use jenkins with docker cloud, but I often meet this problem. The Jenkins Version is Jenkins ver. 2.46.2 , slave version is 3.7,system is ubuntu 14.04 When the task is running, it will throw this problem suddenly: [WS-CLEANUP] Deleting project workspace... FATAL: java.nio.channels.ClosedChannelException java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1295) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:704) at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96) at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:502) at hudson.remoting.Channel.terminate(Channel.java:917) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1295) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:566) at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:172) at org.jenkinsci.remoting.engine.JnlpConnectionState$4.invoke(JnlpConnectionState.java:421) at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:312) at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:418) at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler$1.run(JnlpProtocol4Handler.java:334) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang. Thread .run( Thread .java:745) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:307) at hudson.remoting.Channel.terminate(Channel.java:896) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1295) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:704) at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:96) at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:502) at hudson.remoting.Channel.terminate(Channel.java:917) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:311) at hudson.remoting.Channel.close(Channel.java:1295) at hudson.remoting.Channel.close(Channel.java:1263) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:566) at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:172) at org.jenkinsci.remoting.engine.JnlpConnectionState$4.invoke(JnlpConnectionState.java:421) at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:312) at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:418) at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler$1.run(JnlpProtocol4Handler.java:334) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang. Thread .run( Thread .java:745) at ......remote call to JNLP4-connect connection from 10.25.21.21/10.25.21.21:49874(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:829) at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:974) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at hudson.scm.SCM.checkout(SCM.java:496) at hudson.model.AbstractProject.checkout(AbstractProject.java:1281) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Collecting metadata... Metadata collection done. Email was triggered for : Failure - Any Sending email for trigger: Failure - Any Error evaluating token: Workspace is not accessible Error evaluating token: Workspace is not accessible ERROR: Error: No workspace found! Error evaluating token: Workspace is not accessible Error evaluating token: Workspace is not accessible Error evaluating token: Workspace is not accessible

          Oleg Nenashev added a comment -

          Without logs from the Agent side I cannot say anything.

          "OrderlyShutdown" is a valid behavior if the agent requests the channel shutdown due to whatever reason. 

           

          Oleg Nenashev added a comment - Without logs from the Agent side I cannot say anything. "OrderlyShutdown" is a valid behavior if the agent requests the channel shutdown due to whatever reason.   

            Unassigned Unassigned
            sushant Sushant Gupta
            Votes:
            15 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated: