Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12875

"No valid crumb was included in the request" errors all around

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • CentOS release 5.5 (Final) 64b

      After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":

      Console output

      • When building, the log is unavailable, see console_log.png
      • Once the build is done, the complete log is available, but the same error appears on the side console_side.png

      Build configuration

      • Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
      • Cannot add build steps (when choosing a build step type an error is reported in background), see add_build_step.png

      Manage Jenkins configuration

      • The page loads only partially (first half is permanently greyed out, see configuration.png). The firebug error console displays the "No valid crumb was included in the request" error.

      Manage Jenkins plugins

      • Cannot upgrade nor downgrade, see error shown plugins.png

        1. Screen Shot 2014-03-12 at 10.43.58 AM.png
          Screen Shot 2014-03-12 at 10.43.58 AM.png
          111 kB
        2. add_build_step.png
          add_build_step.png
          98 kB
        3. configuration.png
          configuration.png
          85 kB
        4. console_log.png
          console_log.png
          105 kB
        5. console_side.png
          console_side.png
          202 kB
        6. plugins.png
          plugins.png
          92 kB

          [JENKINS-12875] "No valid crumb was included in the request" errors all around

          Núria Aloy created issue -
          Núria Aloy made changes -
          Description Original: After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":

          h4. Console output

          * When building, the log is unavailable, see !console_log.png!
          * Once the build is done, the complete log is available, but the same error appears on the side !console_side.png!

          h4. Build configuration

          * Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
          * Cannot add build steps (when choosing a build step type an error is reported in background), see !add_build_step.png!

          h4. Manage Jenkins configuration

          * The page loads only partially (first half is permanently greyed out, see !configuration.log!). The firebug error console displays the "No valid crumb was included in the request" error.

          h4. Manage Jenkins plugins

          * Cannot upgrade nor downgrade, see error shown !plugins.png!
          New: After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":

          h4. Console output

          * When building, the log is unavailable, see [^console_log.png]
          * Once the build is done, the complete log is available, but the same error appears on the side [^console_side.png]

          h4. Build configuration

          * Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
          * Cannot add build steps (when choosing a build step type an error is reported in background), see [^add_build_step.png]

          h4. Manage Jenkins configuration

          * The page loads only partially (first half is permanently greyed out, see [^configuration.log]). The firebug error console displays the "No valid crumb was included in the request" error.

          h4. Manage Jenkins plugins

          * Cannot upgrade nor downgrade, see error shown [^plugins.png]
          Núria Aloy made changes -
          Description Original: After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":

          h4. Console output

          * When building, the log is unavailable, see [^console_log.png]
          * Once the build is done, the complete log is available, but the same error appears on the side [^console_side.png]

          h4. Build configuration

          * Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
          * Cannot add build steps (when choosing a build step type an error is reported in background), see [^add_build_step.png]

          h4. Manage Jenkins configuration

          * The page loads only partially (first half is permanently greyed out, see [^configuration.log]). The firebug error console displays the "No valid crumb was included in the request" error.

          h4. Manage Jenkins plugins

          * Cannot upgrade nor downgrade, see error shown [^plugins.png]
          New: After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) several parts of Jenkins have become unusable with error "No valid crumb was included in the request":

          h4. Console output

          * When building, the log is unavailable, see [^console_log.png]
          * Once the build is done, the complete log is available, but the same error appears on the side [^console_side.png]

          h4. Build configuration

          * Builds cannot be launched anymore from the build page (The firebug error console displays the "No valid crumb was included in the request" error). They still can be launched from the dashboard though.
          * Cannot add build steps (when choosing a build step type an error is reported in background), see [^add_build_step.png]

          h4. Manage Jenkins configuration

          * The page loads only partially (first half is permanently greyed out, see [^configuration.png]). The firebug error console displays the "No valid crumb was included in the request" error.

          h4. Manage Jenkins plugins

          * Cannot upgrade nor downgrade, see error shown [^plugins.png]
          Maarten van den Ende made changes -
          Link New: This issue is related to JENKINS-12787 [ JENKINS-12787 ]

          Núria Aloy added a comment -

          After yet another restart things seems to be back to normal (???!!)

          Núria Aloy added a comment - After yet another restart things seems to be back to normal (???!!)
          Núria Aloy made changes -
          Priority Original: Blocker [ 1 ] New: Major [ 3 ]

          Not completely normal. The loading thing in the management section is still happening

          Maarten van den Ende added a comment - Not completely normal. The loading thing in the management section is still happening

          Núria Aloy added a comment -

          In the Jenkins configuration page:

          Error: Form.findMatchingInput is not a function
          Source File: http://jenkins.rightnow.com:8080/static/6dcd23a9/scripts/hudson-behavior.js
          Line: 338

          Núria Aloy added a comment - In the Jenkins configuration page: Error: Form.findMatchingInput is not a function Source File: http://jenkins.rightnow.com:8080/static/6dcd23a9/scripts/hudson-behavior.js Line: 338

          windyroad added a comment -

          I'm not as blocked as the reporting user, but I'm having the same problem (no valid crumb..). In my case it only seems to affect the console output, though the error can be seen for "ajaxBuildQueue" and "ajaxExecuters" on the config page, the home page (and I'm assuming others).

          What's interesting is that I only get this problem through a reverse proxy. http://ve.mbqblqmj.vesrv.com:8080/ works fine, but http://ci.windyroad.org/ (which is RPed to http://ve.mbqblqmj.vesrv.com:8080/) does not.

          windyroad added a comment - I'm not as blocked as the reporting user, but I'm having the same problem (no valid crumb..). In my case it only seems to affect the console output, though the error can be seen for "ajaxBuildQueue" and "ajaxExecuters" on the config page, the home page (and I'm assuming others). What's interesting is that I only get this problem through a reverse proxy. http://ve.mbqblqmj.vesrv.com:8080/ works fine, but http://ci.windyroad.org/ (which is RPed to http://ve.mbqblqmj.vesrv.com:8080/ ) does not.

          windyroad added a comment -

          I've offered USD100.00 at FreedomSponsors to have this fixed (http://www.freedomsponsors.org/core/issue/31/no-valid-crumb-was-included-in-the-request-errors-all-around).
          Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too)
          I'll then check it out and will gladly pay.

          windyroad added a comment - I've offered USD100.00 at FreedomSponsors to have this fixed ( http://www.freedomsponsors.org/core/issue/31/no-valid-crumb-was-included-in-the-request-errors-all-around ). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay.

            danielbeck Daniel Beck
            naloy Núria Aloy
            Votes:
            20 Vote for this issue
            Watchers:
            43 Start watching this issue

              Created:
              Updated:
              Resolved: