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:
And, is there also a slave setting for the timeoutvalue?
(naming for all these settings does not look to be very consistent...)
Unfortunately, that's the case.
Jeff Thompson
Unfortunately, it's really hard to say. Possibilities include resource contention, such as CPU or networking, anything in the middle, such as load balancers, firewalls, etc., network or system configuration. I heard of one a while back that ended up being connected to IP table definition. Can't remember if that was related to docker containers or full VMs. I've heard that there have been some common problems in some VM environments, but I don't know what environments or issues specifically. Maybe VMotion. Maybe the network gets overloaded, especially between VMs. Or interactions between loads on different VMs. I'm not as familiar with the current state, but in the past in other environments I have seen more interference between VMs than expected.
It comes down to standard troubleshooting sorts of behavior. Try to catch the problem. Gather information about different occurrences. Try to isolate any commonalities. Isolate a system for reproduction.
You could try a different type of agent, such as an SSH Agent. The behavior might be different. I've heard recently that Microsoft's SSHD implementation works well.
Good luck on troubleshooting
Jeff
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1263552947.287750.1586874699662%40mail.yahoo.com.
Hey Jeff,looks indeed like the 'standard' type of problems. Unfortunately in our network, I do not have theprivileges to do anything much. Not that that would help much, since I'm only a simple SW engineer,not a network specialist.The tip to try another agent connection is a good one though. Will try that.