-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.245 or 2.235.3
Java 1.8.0_171 or 1.8.0_172
-
-
2.253
We are seeing the bug originally described in JENKINS-62181. Remote agents hang on launch. This is using a supposedly patched release.
In our experience, we are seeing a correct launch of this agent the first time after Jenkins is rebooted. Then, after the agent times out (in-demand delay 1, idle delay 5) and goes down, it cannot be restarting, it deadlocks on launch.
It hangs here:
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 4.3
This is a Unix agent
I don't know how to put in a test for Java deadlocks. Please advise. This is blocking usage.
- is related to
-
JENKINS-62181 Remoting deadlock when launching remote agent
-
- Resolved
-
- relates to
-
JENKINS-63458 Agent deadlock associated with SlaveInitializer, part III
-
- Resolved
-
- links to
We are seeing hanging agents launched by SSH as well immediately after core upgrade 2.222.2 -> 2.235.3 yesterday (as well as upgrading all plugins with all new versions since ~ 3 months).
Interesting thing is that not all agents hang. Maybe the working ones have kept connection and would behave like this as well if they had to reconnect? I dare not try...
I set agent java logging to FINEST, but not much more info there AFAICT:
I did a jstack as well:
I see same thing as in
JENKINS-62181:Note that when I manually kill the agent java process (that is indeed started on agent!) I get this log:
so the ssh connection seems OK. It seems to be a java code problem.
Please let me know if there's any more information you need, or procedures you would like me to test.