[JIRA] (JENKINS-39552) After restart, interrupted pipeline deadlocks waiting for executor

4 views
Skip to first unread message

emil.styrke@gmail.com (JIRA)

unread,
Nov 7, 2016, 7:27:02 AM11/7/16
to jenkinsc...@googlegroups.com
Emil Styrke created an issue
 
Jenkins / Bug JENKINS-39552
After restart, interrupted pipeline deadlocks waiting for executor
Issue Type: Bug Bug
Assignee: Unassigned
Components: pipeline
Created: 2016/Nov/07 12:26 PM
Environment: Jenkins 2.29
Labels: pipeline
Priority: Minor Minor
Reporter: Emil Styrke

I had a pipeline build running, and then restarted Jenkins. After coming up again, I had this in the log for one of the parallel steps in the build:

Resuming build at Mon Nov 07 13:11:05 CET 2016 after Jenkins restart
Waiting to resume part of Atlassian Bitbucket » honey » master #4: ???
Waiting to resume part of Atlassian Bitbucket » honey » master #4: Waiting for next available executor on bcubuntu32

And the last message repeating every few minutes. The slave bcubuntu32 has only one executor, and it seems like this executor was "used up" for this task of waiting for an available executor...

After I went into the configuration and changed number of executors to 2, the build continued as normal.

A possibly related issue: Before restart, I put Jenkins in quiet mode, but the same build agent hung at the end of the pipeline part that was running, never finishing the build. In the end I made the restart without waiting for the part to finish.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

andrew.bayer@gmail.com (JIRA)

unread,
Feb 23, 2018, 4:37:03 PM2/23/18
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
Change By: Andrew Bayer
Component/s: workflow-durable-task-step-plugin
Component/s: pipeline
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

vivek.pandey@gmail.com (JIRA)

unread,
Nov 15, 2018, 5:42:02 PM11/15/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Labels: cloudbees-internal-pipeline pipeline triaged-2018-11
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

joerg.schwaerzler@infineon.com (JIRA)

unread,
Mar 2, 2020, 6:57:03 AM3/2/20
to jenkinsc...@googlegroups.com
Joerg Schwaerzler commented on Bug JENKINS-39552
 
Re: After restart, interrupted pipeline deadlocks waiting for executor

We're facing the same issue here - Jenkins 2.190.2, workflow-durable-task-step-plugin: 2.35.
Are there probably any updates/workaround available in the meantime?

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

joerg.schwaerzler@infineon.com (JIRA)

unread,
Mar 2, 2020, 7:16:07 AM3/2/20
to jenkinsc...@googlegroups.com
Joerg Schwaerzler edited a comment on Bug JENKINS-39552
We're facing the same issue here - Jenkins 2.190.2, workflow-durable-task-step-plugin: 2.35.
Are there probably any updates/workaround available in the meantime?


Seems like we can work around this issue by temporarily adding a second executor...
Reply all
Reply to author
Forward
0 new messages