-
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
[JENKINS-63082] Deadlock launching remote agent
Labels | New: regression |
Link |
New:
This issue is related to |
Environment |
Original:
Jenkins 2.245 Java 1.8.0_171 |
New:
Jenkins 2.245 or 2.235.3 Java 1.8.0_171 |
Environment |
Original:
Jenkins 2.245 or 2.235.3 Java 1.8.0_171 |
New:
Jenkins 2.245 or 2.235.3 Java 1.8.0_171 or 1.8.0_172 |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | Original: regression | New: deadlock lts-candidate regression remoting |
Remote Link | New: This issue links to "jenkins #4886 (Web Link)" [ 25402 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Released As | New: 2.253 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |