• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • Ubuntu 14

      Jenkins won't schedule builds on Ubuntu with the latest version 1.583. I don't see any errors in the jenkins.log to indicate a problem either. I found an issue that seemed related on RedHat, but I'm not sure if it's actually related at all. Mentioning it here just in case: https://bugzilla.redhat.com/show_bug.cgi?id=1149372.

          [JENKINS-25116] Jenkins won't schedule builds

          Daniel Beck added a comment -

          Please explain in more detail what behavior you're seeing. How you are scheduling builds? What is supposed to happen, what actually happens? Are queue items created? If so, what is the reason they're not getting scheduled?

          Daniel Beck added a comment - Please explain in more detail what behavior you're seeing. How you are scheduling builds? What is supposed to happen, what actually happens? Are queue items created? If so, what is the reason they're not getting scheduled?

          Taylor Leese added a comment -

          Basically, if I click on "schedule a build" from the dashboard or "build now" from the project page it doesn't actually schedule a build to run. For example, on the project page when I click "build now" it says "build scheduled" but then no build starts and there is no build in the history. Note, GitHub webhooks do seem to trigger the job successfully and ad-hoc builds use to work so I'm thinking it's something to do with the version of Jenkins I'm now using. In regards to why they aren't scheduling, I wish I knew. I see nothing in the logs to indicate an error and no error in the UI.

          Taylor Leese added a comment - Basically, if I click on "schedule a build" from the dashboard or "build now" from the project page it doesn't actually schedule a build to run. For example, on the project page when I click "build now" it says "build scheduled" but then no build starts and there is no build in the history. Note, GitHub webhooks do seem to trigger the job successfully and ad-hoc builds use to work so I'm thinking it's something to do with the version of Jenkins I'm now using. In regards to why they aren't scheduling, I wish I knew. I see nothing in the logs to indicate an error and no error in the UI.

          Daniel Beck added a comment -

          Does this happen on all projects? Only specific ones? What about when you create a project now?

          Enable your web browser's developer tools, and check the response to the 'Build Now' link. It should return HTTP 201 Created and contain a header like Location: http://jenkins/queue/item/71. Go to the URL http://jenkins/queue/item/71/api/xml and post its XML contents.

          Provide a full list of the plugins that are installed, and some other environment info as explained here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

          Run the following script in Manage Jenkins » Script Console and report its output: println hudson.model.Queue.QueueDecisionHandler.all()

          Daniel Beck added a comment - Does this happen on all projects? Only specific ones? What about when you create a project now? Enable your web browser's developer tools, and check the response to the 'Build Now' link. It should return HTTP 201 Created and contain a header like Location: http://jenkins/queue/item/71 . Go to the URL http://jenkins/queue/item/71/api/xml and post its XML contents. Provide a full list of the plugins that are installed, and some other environment info as explained here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Run the following script in Manage Jenkins » Script Console and report its output: println hudson.model.Queue.QueueDecisionHandler.all()

          Taylor Leese added a comment -

          I used Firebug and noticed there was a 403 error on the POST to submit the job related to the crumb issuer. I disabled "Prevent Cross Site Request Forgery exploits" and then it started working again. This makes sense since I had recently enabled it, but didn't notice this was the cause. Thanks for your help.

          Taylor Leese added a comment - I used Firebug and noticed there was a 403 error on the POST to submit the job related to the crumb issuer. I disabled "Prevent Cross Site Request Forgery exploits" and then it started working again. This makes sense since I had recently enabled it, but didn't notice this was the cause. Thanks for your help.

          Daniel Beck added a comment -

          When you reenable that option, does it stop working again? Was there output or other headers explaining what the problem was? Were there JavaScript issues (e.g. parse errors) reported in your browser? Is Jenkins running behind a reverse proxy? Does it work if you check the proxy compatibility option?

          Daniel Beck added a comment - When you reenable that option, does it stop working again? Was there output or other headers explaining what the problem was? Were there JavaScript issues (e.g. parse errors) reported in your browser? Is Jenkins running behind a reverse proxy? Does it work if you check the proxy compatibility option?

          Taylor Leese added a comment -

          Yes, when I reenable the option it stops working and yes, the proxy compatibility option is on. Currently, I have Jenkins setup to run behind nginx. Here is some information regarding the request/response:

          Headers:
          Cache-Control must-revalidate,no-cache,no-store
          Connection keep-alive
          Content-Encoding gzip
          Content-Type text/html;charset=ISO-8859-1
          Date Mon, 13 Oct 2014 00:27:09 GMT
          Server nginx/1.6.2
          Transfer-Encoding chunked
          view source
          .crumb e537ac28fab87ecb9a9319aaf5bc193b
          Accept text/javascript, text/html, application/xml, text/xml, /
          Accept-Encoding gzip, deflate
          Accept-Language en-US,en;q=0.5
          Cache-Control no-cache
          Connection keep-alive
          Content-Length 0
          Content-Type application/x-www-form-urlencoded; charset=UTF-8
          Cookie JSESSIONID.bae0ecf2=mk3f6tod1v51fh5xb4xbgm5c; screenResolution=1440x900
          Host jenkins.fountain.com
          Pragma no-cache
          Referer https://jenkins.fountain.com/job/Build/
          User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
          X-Prototype-Version 1.7
          X-Requested-With XMLHttpRequest

          Response:
          <html>
          <head>
          <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
          <title>Error 403 No valid crumb was included in the request</title>
          </head>
          <body><h2>HTTP ERROR 403</h2>
          <p>Problem accessing /job/Build/build. Reason:
          <pre> No valid crumb was included in the request</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>
          <br/>

          </body>
          </html>

          Taylor Leese added a comment - Yes, when I reenable the option it stops working and yes, the proxy compatibility option is on. Currently, I have Jenkins setup to run behind nginx. Here is some information regarding the request/response: Headers: Cache-Control must-revalidate,no-cache,no-store Connection keep-alive Content-Encoding gzip Content-Type text/html;charset=ISO-8859-1 Date Mon, 13 Oct 2014 00:27:09 GMT Server nginx/1.6.2 Transfer-Encoding chunked view source .crumb e537ac28fab87ecb9a9319aaf5bc193b Accept text/javascript, text/html, application/xml, text/xml, / Accept-Encoding gzip, deflate Accept-Language en-US,en;q=0.5 Cache-Control no-cache Connection keep-alive Content-Length 0 Content-Type application/x-www-form-urlencoded; charset=UTF-8 Cookie JSESSIONID.bae0ecf2=mk3f6tod1v51fh5xb4xbgm5c; screenResolution=1440x900 Host jenkins.fountain.com Pragma no-cache Referer https://jenkins.fountain.com/job/Build/ User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 X-Prototype-Version 1.7 X-Requested-With XMLHttpRequest Response: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> <title>Error 403 No valid crumb was included in the request</title> </head> <body><h2>HTTP ERROR 403</h2> <p>Problem accessing /job/Build/build. Reason: <pre> No valid crumb was included in the request</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> </body> </html>

          Daniel Beck added a comment -

          Duplicates JENKINS-12875.

          Daniel Beck added a comment - Duplicates JENKINS-12875 .

            Unassigned Unassigned
            tleese22 Taylor Leese
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: