• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Red Hat Linux, Jenkins version 1.505

      When I kill a running job in Jenkins at the very early stage of its build, it doesn't get killed and goes to a null state. I can't see that in the main console, but when I go to the job page, I see the job running. I am unable to kick off another build for the same job as it says that the job is already running. Please see the screenshot.
      The only way I have for now is to restart jenkins. It has been happening quite frequently in the past 2-3 days time. Please send me a resolution for this at the earliest, it is not easy to restart jenkins very often in a busy day.

      Thanks,
      Aswini

          [JENKINS-17667] Unable to kill a job which is running

          For future reference, since I found that bug googling, seems like we're currently having some form of reminiscence of that issue. Running 1.593.
          Currently crawling the thread dump, I don't see anything obvious, yet.

          Baptiste Mathus added a comment - For future reference, since I found that bug googling, seems like we're currently having some form of reminiscence of that issue. Running 1.593. Currently crawling the thread dump, I don't see anything obvious, yet.

          Daniel Beck added a comment -

          Likely a different issue. If in doubt, file a new bug.

          Daniel Beck added a comment - Likely a different issue. If in doubt, file a new bug.

          Baptiste Mathus added a comment - - edited

          Reopening, as this is exactly the same behaviour described above:
          "null on master" and so on.

          Btw, this is very weird because this job is "restricted" to slaves who have a label which is not set on the master.

          I've got a thread dump

          Baptiste Mathus added a comment - - edited Reopening, as this is exactly the same behaviour described above: "null on master" and so on. Btw, this is very weird because this job is "restricted" to slaves who have a label which is not set on the master. I've got a thread dump

          Thread dump for the issue with Jenkins 1.593

          Baptiste Mathus added a comment - Thread dump for the issue with Jenkins 1.593

          After Jenkins restart, the timing has been adjusted and the node on which it seems Jenkins actually wanted to send the build has been fixed:
          "took 0 ms on rhel6-3" (instead now of "master" as it was displayed while it was stuck).

          So, that also matches the issue described, and the guy who did this confirmed: the build was tried to be killed very early during its launch.

          Baptiste Mathus added a comment - After Jenkins restart, the timing has been adjusted and the node on which it seems Jenkins actually wanted to send the build has been fixed: "took 0 ms on rhel6-3" (instead now of "master" as it was displayed while it was stuck). So, that also matches the issue described, and the guy who did this confirmed: the build was tried to be killed very early during its launch.

          @Daniel I reopened before seing your comment, because the symptoms are exactly the same at first sight, and I didn't want to disseminate data onto different JIRA issues when it seemed to be the same one.
          But if needed I can still file a new one, and link to here.

          Baptiste Mathus added a comment - @Daniel I reopened before seing your comment, because the symptoms are exactly the same at first sight, and I didn't want to disseminate data onto different JIRA issues when it seemed to be the same one. But if needed I can still file a new one, and link to here.

          Ozgur Kaya added a comment -

          Disable the job and then enable the job.. You will see that all jobs has killed and not rerunning.

          Ozgur Kaya added a comment - Disable the job and then enable the job.. You will see that all jobs has killed and not rerunning.

          Daniel Beck added a comment -

          I didn't want to disseminate data onto different JIRA issues

          A good idea as long as it never misleads or contradicts. As soon as that happens it's a mess and you need to figure out what's going on. Since you can mark jobs as being related, this shouldn't be an issue.

          Daniel Beck added a comment - I didn't want to disseminate data onto different JIRA issues A good idea as long as it never misleads or contradicts. As soon as that happens it's a mess and you need to figure out what's going on. Since you can mark jobs as being related, this shouldn't be an issue.

          Jesse Glick added a comment -

          Not sure why this got reassigned away from me. I committed the fix to the known issue. (If there are other issues with similar symptoms, they should be filed separately and linked.)

          Jesse Glick added a comment - Not sure why this got reassigned away from me. I committed the fix to the known issue. (If there are other issues with similar symptoms, they should be filed separately and linked.)

          I observed the same issue in the Jenkins version. 1.625.3. The issue occurred in the Multi-configuration project job. In my case the issue appeared after changing the Job weight of the Multi-configuration project job to 2 from 1. The next build of the Multi-configuration project job were non responsive. The non-responsive build under the build history displayed the on hover message "Started Null ago, Estimated remaining time: null." Could trigger the next build after reverting the job weight to 1 and after enabling the job configuration option "Execute concurrent builds if necessary"

          Santosh Phalke added a comment - I observed the same issue in the Jenkins version. 1.625.3. The issue occurred in the Multi-configuration project job. In my case the issue appeared after changing the Job weight of the Multi-configuration project job to 2 from 1. The next build of the Multi-configuration project job were non responsive. The non-responsive build under the build history displayed the on hover message "Started Null ago, Estimated remaining time: null." Could trigger the next build after reverting the job weight to 1 and after enabling the job configuration option "Execute concurrent builds if necessary"

            jglick Jesse Glick
            aswini_r Aswini Rajasekaran
            Votes:
            1 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: