On 4/7/20 11:46 PM, 'monger_39' via Jenkins Users wrote:
Hi,
in my Jenkins I am regularly facing master/slave connection drops with a
message like:
hudson.remoting.ChannelClosedException: Channel "unknown": Remote
call on JNLP4-connect connection from IP/IP:58344 failed.
The channel is closing down or has closed down.
Usually these are caused by something external to the Remoting
communication protocol. Most often by something in the system or
networking environment. Sometimes by some bad interaction between
plugins that ends up impacting the channel.
Your best approach is to figure out where these disconnects originate
and resolve the issue.
I have seen a lot of bug-reports on this. For most, a workaround is
advised by disabling the Ping-Thread through setting:
You should be cautious about changing the ping settings or disabling it
entirely. It can cause some weird and unexpected behaviors. If you do
change the settings, I recommend you change one thing at a time and
evaluate the results. If it doesn't make any difference, restore it to
its default setting.
And, is there also a slave setting for the timeoutvalue?
It depends on how you launch the agent. Remoting system properties are
described at
https://github.com/jenkinsci/remoting/blob/master/docs/configuration.md
(naming for all these settings does not look to be very consistent...)
Unfortunately, that's the case.
Jeff Thompson
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ab43b555-176c-4834-e125-fb66ff612f4d%40cloudbees.com.
