Skip to main content

Jenkins stops processing builds in the build queue after an error appears in the logs

Comments

2 comments

  • Ryan Campbell

    Please note that this general class of errors is tracked as https://issues.jenkins-ci.org/browse/JENKINS-59886

    The instances above are actually bugs in those particular plugins -- these RuntimeExceptions should be checked and appropriate responses made to the given extension point.

    0
  • Gregory Picot

    Hello,

    I have another case of Queue$MaintainTask failed :

    SEVERE: Timer task hudson.model.Queue$MaintainTask@XXXXX failed
    org.acegisecurity.userdetails.UsernameNotFoundException: XXXXX
    at hudson.security.LDAPSecurityRealm$DelegateLDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1268)
    at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:30)
    at hudson.model.User.getUserDetailsForImpersonation(User.java:388)
    at hudson.model.User.impersonate(User.java:370)
    at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$AuthenticationFromBuild$1.authenticate(ExecutorStepExecution.java:698)
    at jenkins.security.QueueItemAuthenticator.authenticate(QueueItemAuthenticator.java:44)
    at hudson.model.Queue$Item.authenticate(Queue.java:2321)
    at hudson.model.Node.canTake(Node.java:400)
    at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:274)
    at hudson.model.Queue.maintain(Queue.java:1627)
    at hudson.model.Queue$MaintainTask.doRun(Queue.java:2898)
    at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70)
    at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:834)

    The user requested exist in the LDAP, and is know by the master.

    It can happen when the LDAP is not reachable.

    In my case I hope to solve the issue by adding a cache to the LDAP configuration

    0

Please sign in to leave a comment.

About CloudBees Support

Our Support Engineers are available to help with any questions or problems you may have with any of our products.