Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: workflow-durable-task-step-plugin
-
Labels:None
-
Environment:Jenkins 2.46.2 core and libraries
Pipeline 2.5
-
Similar Issues:
Description
In the middle of a build on a Windows slave, the build hung for a day with this message:
Cannot contact starfire: java.io.IOException: remote file operation failed: D:\jenkins\workspace\spro-2017\protocols\windows\msvc-15.0-32b-native-release-static-win32\sourcebuildspace at hudson.remoting.Channel@5f758b70:JNLP4-connect connection from starfire.blue.roguewave.com/10.68.9.64:63685: hudson.remoting.ChannelClosedException: channel is already closed
I had to terminate the build manually.
Attachments
Issue Links
- duplicates
-
JENKINS-49707 Auto retry for elastic agents after channel closure
-
- Open
-
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | workflow-durable-task-step-plugin [ 21715 ] | |
Component/s | pipeline [ 21692 ] |
Link | This issue duplicates JENKINS-49707 [ JENKINS-49707 ] |
Hi. I'm also affected by this bug - in my case tests run using jenkins are making machine reboot/sleep/hibernate and after such event Master hangs despite slave reconnecting and appearing as online.
I've also asked at SO about it: https://stackoverflow.com/questions/62393684/jenkins-pipeline-on-master-stuck-when-slave-reboots/
EDIT: My jenkins version is 2.222.4.