Jenkins dedicates a java.lang.Thread
for each executor. Under normal operation, this thread is alive all the time (although unless a build is going on the thread is sleeping.) The "dead executor" sign (see the picture on the right) happens when this thread dies unexpectedly. When this happens, please check your Jenkins system log (http://server/jenkins/log
) and look for a stack trace, then report that to Jenkins users list or the issue tracker.
Obsolete as of Jenkins 2.13.
6 Comments
Unknown User (leoromanovsky)
The server had to be restarted in mid-build and now all the executioners are dead. How can I resolve this?
Unknown User (qatest)
im getting the dead alert on jenkins (site monitor job)..is it a bug frm site monitor plugin or jenkins...
jenkins-screenshot.PNG
pls assist asap
Unknown User (tdxmgy)
I met one slave dead always,but master and slave all dead, except slaves which are running jobs.If need log,I can sutmit
Sep 18, 2014 4:06:19 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: item.isStuck() in /view/Z2_SISLEY/ajaxBuildQueue. Reason: java.lang.ArrayIndexOutOfBoundsException: Assertion error: fa
iling to load #123 DESC: lo=18,hi=16,size=18,size2=18
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #123 DESC: lo=18,hi=16,size=18,size2=18
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:442)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103)
at hudson.model.Job.getLastBuildsOverThreshold(Job.java:887)
at hudson.model.Job.getEstimatedDuration(Job.java:894)
at hudson.model.Queue$BuildableItem.isStuck(Queue.java:1654)
at sun.reflect.GeneratedMethodAccessor734.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
Unknown User (zhaoying818)
remove the builds history or set next build number bigger can solve it
Unknown User (aditigidra)
I am facing the same issue. There is also an option 'Restart the thread' showing up. This is freeing up the executor.
My question is whether this is sufficient?
Unknown User (basu)
Aditi, 'Restart the thread' will just clear it out.
To fix this issue install 'Set Next Build Number' jenkins plugin.
Give the next build number in jenkins job using this plugin.
Refer "Next Build Number Plugin" for more information.