Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: git-plugin, matrix-project-plugin
-
Labels:
-
Environment:Jenkins 1.597
-
Similar Issues:
Description
Jan 23, 2015 11:43:52 PM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: /MY_DIR/jenkins/home/jobs/MY_JOB/builds/29 already existed; will not overwite with MY_JOB #29
at hudson.model.RunMap.put(RunMap.java:187)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1001)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1200)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)
I tried to manually start a job via the run button. I see the Dead
indicator in the executor status sidebar. I was able to restart the thread and then manually start the job again. This time it started with #30 and appears to be running OK.
Looking at JENKINS_HOME dir in linux, I see that there is a build directory for #29 and the job ran and failed (unrelated). Looking at the Jenkins webpage for the job, the build skips from 28 to (the now running) 30. #29 has no listing.
I know some items related to the major enhancement are not closed yet, like JENKINS-23152, so please close this if the behavior I'm seeing is expected until the next release. If this is unexpected - hopefully this report is informative - this issue happened 4x in a row for each job I had put in the build queue.
Attachments
Issue Links
- is blocking
-
JENKINS-24380 Use build numbers as IDs
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- links to
Activity
Right, ideally a way to reproduce the problem from scratch. When that cannot be found, there may be some clues that are helpful (for example: only happens when a certain plugin is installed/configured), but in general the problem may not be fixable. For certain bugs of course the error message/stack trace suffices to guess at a diagnosis. Unfortunately that is not the case here.
Is this the best/current bug to discuss the 'dead node' issue? Should I be using JENKINS-29268 or something else instead?
This bug is affecting us pretty badly (team of ~15 developers) and we're willing to put some work in to help get it fixed.
Thanks in advance
David Harris
added a comment - Is this the best/current bug to discuss the 'dead node' issue? Should I be using JENKINS-29268 or something else instead?
This bug is affecting us pretty badly (team of ~15 developers) and we're willing to put some work in to help get it fixed.
Thanks in advance I don't think a resolved issue is generally a good place to discuss an issue you're currently seeing. If there is an open issue that is the same, or appears strongly related, that would be a reasonable place for the discussion.
If the issue is still there, and this describes that issue, then I think this bug should be reopened.
Do not reopen this issue.
There is a known but unconfirmed occurrence when using reload-from-disk. If you know of some other means of reproducing, mention in JENKINS-27530.
Usually, isolating a problem to root cause needs enough description of the distinct conditions which caused the problem so that someone else can duplicate the problem.
In this case, it may need a support bundle (to show the versions of various plugins installed), a copy of the job definition (or a detailed enough description of the job definition that someone can recreate the job from that description), and a description of the actions taken to show the problem.