[JIRA] (JENKINS-49537) "Waiting for next available executor on master" solved by *looking* at other jobs
Title: Message Title Jesse Glick resolved as Cannot Reproduce Fine logging on Queue might give you a lead. Jenkins / JENKINS-49537 "Waiting for next available executor on master" solved by *looking* at other jobs Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49537) "Waiting for next available executor on master" solved by *looking* at other jobs
Title: Message Title
Niklas Hambuechen commented on JENKINS-49537
Re: "Waiting for next available executor on master" solved by *looking* at other jobs
I got it again now and found out that going on the Jenkins main page (not the Blue one, the classic one) is what unlocks the build. Details: https://jenkins1.example.com/job/example/job/myfeaturebranch/3/console shows: Push event to branch myfeaturebranch {{ 19:52:57 Connecting to https://api.github.com using username/**}} {{ Obtained Jenkinsfile from ...}} {{ Running in Durability level: MAX_SURVIVABILITY}} {{ [Pipeline] slackSend}} {{ run slackstepsend, step null:false, desc :false}} {{ Slack Send Pipeline step configured values from global config - baseUrl: true, teamDomain: true, token: true, channel: true, color: false}} {{ [Pipeline] node}} {{ Still waiting to schedule task}} {{ Waiting for next available executor on master}} `journalctl -u jenkins -e` shows: Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#1}} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#1}} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: Mar 03, 2018 7:56:52 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 19:56:52 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#1}} Visiting https://jenkins1.example.com/job/example/job/myfeaturebranch/2/console had no effect Visiting https://jenkins1.example.com/blue/organizations/jenkins/example/detail/myfeaturebranch/2/pipeline/ printed into the logs: Mar 03 20:00:15 jenkins1 jenkins-start[5197]: Mar 03, 2018 8:00:15 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor {{ Mar 03 20:00:15 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 20:00:15 jenkins1 jenkins-start[5197]: Mar 03, 2018 8:00:15 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 20:00:15 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 20:00:15 jenkins1 jenkins-start[5197]: Mar 03, 2018 8:00:15 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 20:00:15 jenkins1 jenkins-start[5197]: SEVERE: Could not find execution for run example/myfeaturebranch#2}} {{ Mar 03 20:00:16 jenkins1 jenkins-start[5197]: Mar 03, 2018 8:00:16 PM io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor }} {{ Mar 03 20:00:16 jenkins1 jenkins-start[5197]: SEVERE: Could not find
[JIRA] (JENKINS-49537) "Waiting for next available executor on master" solved by *looking* at other jobs
Title: Message Title Niklas Hambuechen commented on JENKINS-49537 Re: "Waiting for next available executor on master" solved by *looking* at other jobs The style editing in this JIRA doesn't work at all It inserts random characters even when using visual mode. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49537) "Waiting for next available executor on master" solved by *looking* at other jobs
Title: Message Title
Niklas Hambuechen created an issue
Jenkins / JENKINS-49537
"Waiting for next available executor on master" solved by *looking* at other jobs
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-02-13 17:52
Environment:
Jenins 2.95, on NixOS
Priority:
Minor
Reporter:
Niklas Hambuechen
OK so this is a weird one. Once a week or so, by Jenkins builds get stuck with Waiting for next available executor on master. E.g. now, the a build got stuck for 2 days this way. The funny thing is: I can resolve this bug simply by read-only-browsing around in the Jenkins UI. Once I view the console output of the finished build before the hanging build, the hanging build suddenly starts building. So, "looking angry at Jenkins" makes the issue go away. I could reproduce this 4 times so far, but it takes a week or so to happen again so it's not exactly easy to reproduce. After short consideration if you have any idea what might cause this, please advise how I can gather more information to figure this out. Thanks! (I've filed the bug as `core` but don't know if it might be caused by a different plugin.)
Jenkins 2.95 Plugins: {{ org.jenkins-ci.main:jenkins-war:2.95 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2 common
