[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed

swang@vixs.com (JIRA)

unread,

Mar 10, 2017, 2:00:04 PM3/10/17

to jenkinsc...@googlegroups.com

Simon Wang created an issue

Jenkins /

JENKINS-42678

hudson.remoting.ChannelClosedException: channel is already closed

Issue Type:	Bug
Assignee:	Oleg Nenashev
Components:	_unsorted
Created:	2017/Mar/10 6:59 PM
Priority:	Minor
Reporter:	Simon Wang

Building remotely on fw-build-14 (FC14 Linux) in workspace /work/jenkins/workspace/robot-tesla-linux
java.io.IOException: remote file operation failed: /work/jenkins/workspace/robot-tesla-linux at hudson.remoting.Channel@376f735f:fw-build-14: hudson.remoting.ChannelClosedException: channel is already closed
at hudson.FilePath.act(FilePath.java:985)
at hudson.FilePath.act(FilePath.java:967)
at hudson.FilePath.mkdirs(FilePath.java:1150)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1263)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
at hudson.model.Run.execute(Run.java:1751)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.remoting.ChannelClosedException: channel is already closed
at hudson.remoting.Channel.send(Channel.java:550)
at hudson.remoting.Request.call(Request.java:129)
at hudson.remoting.Channel.call(Channel.java:752)
at hudson.FilePath.act(FilePath.java:978)
... 10 more
Caused by: java.io.IOException
at hudson.remoting.Channel.close(Channel.java:1109)
at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118)
at hudson.remoting.PingThread.ping(PingThread.java:126)
at hudson.remoting.PingThread.run(PingThread.java:85)
Caused by: java.util.concurrent.TimeoutException: Ping started at 1489166596118 hasn't completed by 1489166836119
... 2 more

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

o.v.nenashev@gmail.com (JIRA)

unread,

Mar 10, 2017, 2:06:03 PM3/10/17

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

JENKINS-42678

Re: hudson.remoting.ChannelClosedException: channel is already closed

Please provide

Logs from the agent side
Version of the Jenkins core
Version of Remoting on the agent side

Add Comment

bahdad@bigmir.net (JIRA)

unread,

Mar 31, 2017, 4:49:03 AM3/31/17

to jenkinsc...@googlegroups.com

Sasha Miroshnich edited a comment on

JENKINS-42678

Re: hudson.remoting.ChannelClosedException: channel is already closed

https://github.com/jenkinsci/jenkins/commit/6d95e3680c8edf49c2353633dd9c1a7072440989

Looks like it was fixed with trivial _try ... catch_ block at some forked version.
Could it be ported to some of the official builds?

Add Comment

bahdad@bigmir.net (JIRA)

unread,

Mar 31, 2017, 4:49:08 AM3/31/17

to jenkinsc...@googlegroups.com

Sasha Miroshnich commented on

JENKINS-42678

Re: hudson.remoting.ChannelClosedException: channel is already closed

Looks like it was fixed with trivial try ... catch block at some forked version.

Could it be ported to some of the official builds?

Add Comment

bahdad@bigmir.net (JIRA)

unread,

Mar 31, 2017, 4:57:01 AM3/31/17

to jenkinsc...@googlegroups.com

Sasha Miroshnich updated an issue

Jenkins /

JENKINS-42678

hudson.remoting.ChannelClosedException: channel is already closed

Change By:	Sasha Miroshnich
Comment:	https://github.com/jenkinsci/jenkins/commit/6d95e3680c8edf49c2353633dd9c1a7072440989 Looks like it was fixed with trivial _try ... catch_ block at some forked version.