Jenkins Jobs are not Starting

Issue

When clicking on build, it looks like nothing is happening: the build is not appearing in the Jenkins Queue.

Environment

Resolution

This kind of symptoms mean that something is holding a lock on the Jenkins Queue.
For instance, the Docker Plugin prior to 1.0.0 can be affected by this kind of issue.
You can verify that you are experiencing a Deadlock by going into /threadDump.
You should see several threads mentioning hudson.model.Queue.withLock.

In case you encounter a case like that, it is best to open a case with CloudBees Support.

For such a case, CloudBees Support will need the data as indicated in this KB article (Linux)
or this one (Windows).

Workaround

In case you would like to investigate the issue yourself, you should look into the thread dump for a stack having a lock on the Jenkins Queue and performing long operation.
For instance the following dump exhibits the issue:

at java.net.SocketInputStream.socketRead0(Native Method) <--- socket operation
// suppressed for clarity
at com.nirima.jenkins.plugins.docker.strategy.DockerOnceRetentionStrategy$1$1.run(DockerOnceRetentionStrategy.java:112)
at hudson.model.Queue._withLock(Queue.java:1320)
at hudson.model.Queue.withLock(Queue.java:1197) <--- Lock on the Queue
at com.nirima.jenkins.plugins.docker.strategy.DockerOnceRetentionStrategy$1.run(DockerOnceRetentionStrategy.java:106) <--- docker plugin
// suppressed for clarity

NB: you should take several thread dumps to ensure there is a lock, one single thread dump showing the previous stack is perfectly normal.

References

JENKINS-42187

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.