-
Bug
-
Resolution: Fixed
-
Critical
-
The dead node is Win7 running cygwin sshd, the server is RHEL5. Jenkins version 1.605.
Submitting log per instructions on the dead node page.
Unexpected executor death
java.lang.IllegalStateException: /hfs/d1/local/jenkins/jobs/test_other/builds/96 already existed; will not overwite with test_other #96
at hudson.model.RunMap.put(RunMap.java:187)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1006)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)
- is duplicated by
-
JENKINS-33794 nextBuildNumber not updated when reload configuration
-
- Resolved
-
-
JENKINS-29268 Unexpected executor death
-
- Resolved
-
-
JENKINS-29680 Crash after artifact promotion
-
- Resolved
-
-
JENKINS-29902 Unexpected executor death - java.lang.IllegalStateException: <build> already existed
-
- Resolved
-
-
JENKINS-34103 jenkins reindex purges build queue
-
- Resolved
-
-
JENKINS-34611 SEVERE: Unexpected executor death; java.lang.IllegalStateException: /var/lib/jenkins/builds/myproject/2 already existed;
-
- Resolved
-
- is related to
-
JENKINS-11563 Jenkins should fail initialization if it can not parse a job history
-
- Resolved
-
-
JENKINS-23152 builds getting lost due to GerritTrigger
-
- Resolved
-
-
JENKINS-26582 ISE from RunMap.put using /git/notifyCommit on a matrix project
-
- Closed
-
- links to
[JENKINS-27530] ISE from RunMap.put after reloading configuration from disk
Link |
New:
This issue is duplicated by |
Summary | Original: Dead node | New: ISE from RunMap.put (non-Git+Matrix causes) |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is related to |
Link |
New:
This issue is duplicated by |
Summary | Original: ISE from RunMap.put (non-Git+Matrix causes) | New: ISE from RunMap.put after reloading configuration from disk |
Would be interesting which logs you have installed, how the job is configured (e.g. parallel execution), when this issue occurred and when the "original" build 96 was created.
Could you install the Support Core plugin and attach a support bundle to this issue?
There are a few issues related to that (
JENKINS-26582is at least similar) since 1.597 changed how builds are stored on disk, but we don't yet have the cause. And the alternative to just overwrite the original build's data is even scarier than this...