[JIRA] [ssh-slaves-plugin] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel

1,938 views
Skip to first unread message

jsposato@mobiquityinc.com (JIRA)

unread,
Oct 21, 2015, 10:29:01 AM10/21/15
to jenkinsc...@googlegroups.com
John Sposato commented on Bug JENKINS-25858
 
Re: java.io.IOException: Unexpected termination of the channel

Having same issue, our slaves are launched using the EC2 plugin.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

jsposato@mobiquityinc.com (JIRA)

unread,
Oct 21, 2015, 10:38:03 AM10/21/15
to jenkinsc...@googlegroups.com
John Sposato edited a comment on Bug JENKINS-25858
Having same issue, our slaves are launched using the EC2 plugin.  
 


{noformat}

java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
{noformat}

jsposato@mobiquityinc.com (JIRA)

unread,
Oct 21, 2015, 10:39:04 AM10/21/15
to jenkinsc...@googlegroups.com
John Sposato edited a comment on Bug JENKINS-25858
Having same issue, our slaves are launched using the EC2 plugin. 


{noformat}
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
{noformat}


CentOS 7

carlton@sumologic.com (JIRA)

unread,
Mar 7, 2016, 6:43:02 PM3/7/16
to jenkinsc...@googlegroups.com

I'm seeing this as well - I lose one or two slaves a day. Sample backtrace:

FATAL: java.io.IOException: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
        at hudson.remoting.Request.abort(Request.java:297)
        at hudson.remoting.Channel.terminate(Channel.java:844)
        at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
        at ......remote call to Elastic Slave (i-4cc13bf9)(Native Method)
        at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413)
        at hudson.remoting.Request.call(Request.java:172)
        at hudson.remoting.Channel.call(Channel.java:777)
        at hudson.FilePath.act(FilePath.java:978)
        at hudson.FilePath.act(FilePath.java:967)
        at hudson.FilePath.untar(FilePath.java:519)
        at hudson.plugins.cloneworkspace.CloneWorkspacePublisher$WorkspaceSnapshotTar.restoreTo(CloneWorkspacePublisher.java:243)
        at hudson.plugins.cloneworkspace.CloneWorkspaceSCM$Snapshot.restoreTo(CloneWorkspaceSCM.java:396)
        at hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:152)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1274)
        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:1738)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
        at hudson.model.ResourceController.execute(ResourceController.java:98)
        at hudson.model.Executor.run(Executor.java:381)
Caused by: java.io.IOException: Unexpected termination of the channel
        at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
        at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2332)
        at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2801)
        at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)
        at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
        at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:40)
        at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
        at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

I don't have the slave-side log for that specific error, but on earlier failures that I looked at, the slave said something like this:

2016-03-03 16:30:38.483-0800 [id=10]	SEVERE	h.r.SynchronousCommandTransport$ReaderThread#run: I/O error in channel channel
java.io.IOException: Unexpected EOF
	at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99)
	at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

I'm using the EC2 plugin to launch slaves; Ubuntu 14.04.2, Jenkins 1.609.3. I don't yet have solid evidence as to whether the network disconnects are caused by Jenkins code or by something in the networking stack, but it would be nice if Jenkins could handle this better somehow - not have the slave process die in this scenario and then reconnect to it, or something.

carlton@sumologic.com (JIRA)

unread,
Mar 7, 2016, 6:45:02 PM3/7/16
to jenkinsc...@googlegroups.com

Also, I see this bug marked as a duplicate of JENKINS-20101 but I don't see clear evidence that they're the same - that bug seems to be a situation where the master died for some reason, whereas in my situation (and, as far as I can tell, the other people commenting here), the master is running fine the whole time, it just loses its connection to a slave.

joaogbcravo@gmail.com (JIRA)

unread,
Mar 15, 2016, 7:19:01 AM3/15/16
to jenkinsc...@googlegroups.com

Hey guys!

I'm running Jenkins on AWS EC2 and I got this same problem. I was able to fix it with
https://github.com/scala/scala-jenkins-infra/issues/26#issuecomment-73825006

I don't know exactly why, but it fixed.. anyone can explain why?

Cheers

carlton@sumologic.com (JIRA)

unread,
Mar 15, 2016, 12:28:01 PM3/15/16
to jenkinsc...@googlegroups.com

This bug is tagged as ssh-slaves-plugin, but now that I understand the EC2 plugin, I realize that it replaces the SSH Slaves Plugin; I don't know for sure which plugin the original poster was using, but it seems like the rest of us are using EC2. I've been experimenting for the last week with setting "Connect by SSH Process" (under the advanced options) to true, and I haven't had any problems since I've done that, so I would recommend that to other people who are running into this symptom with the EC2 option. (It was added for exactly this reason, see https://github.com/jenkinsci/ec2-plugin/pull/139 )

There's still presumably a collection of potential underlying non-Jenkins issues - maybe kernel problems, maybe security groups, who knows, probably different for different installations - but it seems to me like the external ssh program is noticeably better at dealing with temporary network glitches than Trilead is.

orkru666@gmail.com (JIRA)

unread,
Dec 23, 2016, 10:25:02 AM12/23/16
to jenkinsc...@googlegroups.com

David Carlton but I'm getting the same with just *ssh-slaves-plugin*.
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

kerrhome (JIRA)

unread,
Feb 9, 2017, 10:17:04 AM2/9/17
to jenkinsc...@googlegroups.com

We just started getting this in the last couple of weeks. I don't remember seeing this before, but now we seem to see a failure every day or every other day over the last week. We are not using EC2 plugin. We are only using "ssh-slaves-plugin". The slave is a macOS VM that has not had any recent updates and we've been using it for years.

ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
Caused by: java.io.EOFException
	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325)
	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794)
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)
	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
	at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)

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

unread,
Mar 13, 2018, 7:46:06 AM3/13/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
 

Bulk issue update: The plugin connectivity is still unstable from what I see in this and other reports. Probably the recent patches in 1.24-1.25 caused some extra instability by getting rid of interlocks between agent connection and termination logic. Apparently it impacts some reconnection scenarios due to the race conditions.

Unfortunately I do not have capacity to work on the plugin in medium-term. So for now I am unassigning issues from myself. Ivan Fernandez Calvo was very kind to take ownership of the plugin and to handle some workload in it. Probably he will have some capacity to review the backlog I was unable to triage.
Jenkins / Bug JENKINS-25858
Change By: Oleg Nenashev
Assignee: Oleg Nenashev
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

vasilena.treneva@softwareag.com (JIRA)

unread,
Apr 10, 2018, 5:56:02 AM4/10/18
to jenkinsc...@googlegroups.com
Vassilena Treneva commented on Bug JENKINS-25858
 
Re: java.io.IOException: Unexpected termination of the channel

Using Jenkins ver. 2.113 with SSH Slaves plugin 1.26. All our UNIX, Windows and OSX slaves are using SSH connection.
We are seeing a lot of these. Is it the same issue? 

 

============================

Slave JVM has not reported exit code. Is it still running?
ERROR: Connection terminated
java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:354)


at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)

at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

 

============================

 

ERROR: Connection terminated
java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:354)


at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)

at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)
ERROR: Socket connection to SSH server was lost
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:210)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at com.trilead.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41)
at com.trilead.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52)
at com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79)
at com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108)
at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:232)
at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:706)
at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502)
at java.lang.Thread.run(Thread.java:748)
Slave JVM has not reported exit code before the socket was lost
[04/05/18 17:10:24] [SSH] Connection closed.

ifernandezcalvo@cloudbees.com (JIRA)

unread,
Apr 18, 2018, 2:15:03 PM4/18/18
to jenkinsc...@googlegroups.com

Overall recommendations:

francois@aichelbaum.com (JIRA)

unread,
Apr 18, 2018, 3:14:02 PM4/18/18
to jenkinsc...@googlegroups.com

Hi Ivan

 

I'm curious why your pinpointing in the various thread regarding this issue that we all need to review our TCP stack optimization whereas it used to work and stop after some update of either your code or the Linux kernel

 

As it also impacts Windows and Mac OS machines, I guess the culprit might not be the kernel or the TCP stack optim.

ifernandezcalvo@cloudbees.com (JIRA)

unread,
Apr 18, 2018, 3:19:03 PM4/18/18
to jenkinsc...@googlegroups.com

Those are overall recommendations, check it your Agents satisfy those recommendations, they resolve the 90% of Agents issues

francois@aichelbaum.com (JIRA)

unread,
Apr 18, 2018, 3:54:02 PM4/18/18
to jenkinsc...@googlegroups.com

As said on the other thread, we already went through those that you can find on Internet and they solved nothing as .... it was working before a change in the code

vasilena.treneva@softwareag.com (JIRA)

unread,
Apr 18, 2018, 4:03:02 PM4/18/18
to jenkinsc...@googlegroups.com

Francois Aichelbaum, do you know which version of the server/ssh plugin does NOT have this issue?

francois@aichelbaum.com (JIRA)

unread,
Apr 18, 2018, 4:15:04 PM4/18/18
to jenkinsc...@googlegroups.com

The ones prior to 12 December as this was the apparent last update without issue we did.

The next one (for us) was beginning for January and things got even worse following the rush for Kernel updates, hardware firmware updates and even more with VMware patches.

francois@aichelbaum.com (JIRA)

unread,
Apr 18, 2018, 4:15:05 PM4/18/18
to jenkinsc...@googlegroups.com
Francois Aichelbaum edited a comment on Bug JENKINS-25858
The ones prior to 12 December , 12th as this was the apparent last update without issue we did.


The next one (for us) was beginning for January and things got even worse following the rush for Kernel updates, hardware firmware updates and even more with VMware patches.

francois@aichelbaum.com (JIRA)

unread,
Apr 19, 2018, 4:42:06 AM4/19/18
to jenkinsc...@googlegroups.com

This morning, we ran those new TCP optim and failed as usual ... 

ifernandezcalvo@cloudbees.com (JIRA)

unread,
Apr 19, 2018, 5:14:05 AM4/19/18
to jenkinsc...@googlegroups.com

Francois Aichelbaum Do you use vMotion on those VMWare VMs? we know that Trilead library it is really sensitive to network performance/issues, we are trying to improve this to make the SSH connection more robust

francois@aichelbaum.com (JIRA)

unread,
Apr 19, 2018, 6:30:03 AM4/19/18
to jenkinsc...@googlegroups.com

we tried all that as far, for instance, as dedicating a VMware ESX host with higher ressources that needed and stick all the VM to that host. Anyhow, the LAN between our hosts is 10 Gbps and we have no connection issues between neither the hosts or the VM for the various services we host, besides Jenkins.

 

As said, it worked and went poof with the Jenkins updates and the Spectre/Meltdown patches that came at the same time

vernon.lingley@sonos.com (JIRA)

unread,
May 7, 2018, 12:44:04 PM5/7/18
to jenkinsc...@googlegroups.com

We just saw this one as well. So far it's only been on our AWS based Ubuntu 16.04 nodes. We're running Jenkins 2.73.3 and ssh-slaves plugin 1.21. 

06:11:18 java.io.EOFException
06:11:18 	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671)
06:11:18 	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146)
06:11:18 	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858)
06:11:18 	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:354)
06:11:18 	at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
06:11:18 	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
06:11:18 	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
06:11:18 Caused: java.io.IOException: Unexpected termination of the channel
06:11:18 	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
06:11:18 Caused: hudson.remoting.ChannelClosedException: Remote call on AWS-LIN-18 failed. The channel is closing down or has closed down
06:11:18 	at hudson.remoting.Channel.call(Channel.java:898)
06:11:18 	at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1079)
06:11:18 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:502)
06:11:18 	at hudson.model.Run.execute(Run.java:1737)
06:11:18 	at hudson.matrix.MatrixBuild.run(MatrixBuild.java:314)
06:11:18 	at hudson.model.ResourceController.execute(ResourceController.java:97)
06:11:18 	at hudson.model.Executor.run(Executor.java:421)

We can try upgrading the plugin to 1.23, but it looks like it may go back farther then that release.

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 21, 2018, 2:18:02 AM8/21/18
to jenkinsc...@googlegroups.com

I am aslo facing the same issue of agent went offline during build.

I am using jenkins v2.105 and jre 1.8

I am using Linux as master and IBM AIX and windows server 2K12 as slaves. we are executing nightly builds on slaves but sometimes due to agent goes offline that build won't get complete, so anybody has any workarround for this issue then please let me know.

Thanks in advance.
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

kuisathaverat@gmail.com (JIRA)

unread,
Aug 21, 2018, 7:42:02 AM8/21/18
to jenkinsc...@googlegroups.com

shraddha Magar Without the exception trace it is not possible to diagnose anything, Do you have the error trace on the Job and the corresponding error trace on the Jenkins logs? on the next version, the plugin will support by default the remoting debug I hope this would help to diagnose this kind of errors.

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 21, 2018, 8:17:02 AM8/21/18
to jenkinsc...@googlegroups.com

Below is the error I can see in build log

Agent went offline during the build
ERROR: Connection was broken: java.io.EOFException


 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671)
 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146)
 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858)

 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:354)

 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)

 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

kuisathaverat@gmail.com (JIRA)

unread,
Aug 21, 2018, 8:33:02 AM8/21/18
to jenkinsc...@googlegroups.com

This is on Jenkins side, right? this only said that the channel is broken but not the root cause, Do you have any logs on the Agent workdir folder? also, check the latest executed build in that Agent to see if there is more info, see https://github.com/jenkinsci/remoting/blob/master/docs/logging.md to enable logging on the Agent side.

kuisathaverat@gmail.com (JIRA)

unread,
Aug 21, 2018, 8:47:02 AM8/21/18
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo
 
Change By: Ivan Fernandez Calvo
Assignee: Ivan Fernandez Calvo

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 29, 2018, 5:21:02 AM8/29/18
to jenkinsc...@googlegroups.com
shraddha Magar commented on Bug JENKINS-25858
 
Re: java.io.IOException: Unexpected termination of the channel

Thanks for your quick reply.

Yes. Those logs were from Jenkins side.

Actually, slave goes offline for very short time and comes back online immediately. so not able to get the logs from agent.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 29, 2018, 5:22:02 AM8/29/18
to jenkinsc...@googlegroups.com
shraddha Magar edited a comment on Bug JENKINS-25858
Thanks for your quick reply.

Yes. Those logs were from Jenkins side.

Actually, slave goes offline for very short time and comes back online immediately. so not able to get the logs from agent. But due to that short time job is getting failed.

kuisathaverat@gmail.com (JIRA)

unread,
Aug 29, 2018, 5:44:02 AM8/29/18
to jenkinsc...@googlegroups.com

Which SSH Slaves Plugin version do you use? Did you add the `-workDir AGENT_WORK_DIR` parameter to your suffix command configuration to grab the logs?

https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 29, 2018, 7:53:02 AM8/29/18
to jenkinsc...@googlegroups.com

Also I have restarted Jenkins instance then agent which is configured on windows with JNLP got offline and its not coming online, its showing below error.

Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among http://x.x.x.x:x/jenkins/
Aug 29, 2018 1:43:04 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: x.x.x.x
  Agent port:    37091
  Identity:      51:a8:0d:a8:18:dd:db:d8:ea:18:b7:98:da:76:b2:ae
Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Aug 29, 2018 1:43:04 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to x.x.x.x:37091
Aug 29, 2018 1:43:35 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to x.x.x.x:37091 (retrying:2)
java.io.IOException: Failed to connect to x.x.x.x:37091
 at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242)
 at hudson.remoting.Engine.connect(Engine.java:686)
 at hudson.remoting.Engine.innerRun(Engine.java:547)
 at hudson.remoting.Engine.run(Engine.java:469)
Caused by: java.net.ConnectException: Connection timed out: connect
 at sun.nio.ch.Net.connect0(Native Method)
 at sun.nio.ch.Net.connect(Unknown Source)
 at sun.nio.ch.Net.connect(Unknown Source)
 at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
 at java.nio.channels.SocketChannel.open(Unknown Source)
 at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203)
 ... 3 more

 

Could you please help me out please?

just replaced master IP with x.x.x.x.

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 29, 2018, 7:54:05 AM8/29/18
to jenkinsc...@googlegroups.com
shraddha Magar edited a comment on Bug JENKINS-25858

kuisathaverat@gmail.com (JIRA)

unread,
Aug 29, 2018, 9:13:02 AM8/29/18
to jenkinsc...@googlegroups.com

This Windows Agent is a JNLP Agent, so your issue is not related to SSH Slaves plugin.

It seems a network/configuration issue, not a bug, ask on the google user groups see https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue

shraddha.magar5@gmail.com (JIRA)

unread,
Aug 29, 2018, 9:26:02 AM8/29/18
to jenkinsc...@googlegroups.com

yes. this agent is configured through JNLP.

and other issue is for AIX machine. we have agents configured on both AIX and Windows. we are using ssh slave plugin 1.26.

svanoort@cloudbees.com (JIRA)

unread,
Oct 25, 2018, 7:41:02 AM10/25/18
to jenkinsc...@googlegroups.com
Sam Van Oort assigned an issue to Sam Van Oort
 
Change By: Sam Van Oort
Assignee: Ivan Fernandez Calvo Sam Van Oort

kuisathaverat@gmail.com (JIRA)

unread,
Oct 13, 2019, 4:10:22 PM10/13/19
to jenkinsc...@googlegroups.com
Change By: Ivan Fernandez Calvo
Assignee: Sam Van Oort Ivan Fernandez Calvo
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

kuisathaverat@gmail.com (JIRA)

unread,
Oct 13, 2019, 4:10:24 PM10/13/19
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo resolved as Cannot Reproduce
Status: Open Resolved
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages