Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
Jenkins 2.245 or 2.235.3
Java 1.8.0_171 or 1.8.0_172
-
-
2.253
Description
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.
Attachments
Issue Links
- 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
Yes, it seems to work now. At first, I still had some hiccups (on far fewer slaves) since there were still some (hung up) java processes running on the slaves but after a restart of those, all of them are up again.