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

java.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • /var/log/jenkins # rpm -qa | grep -i jenkins
      jenkins-2.164.1-1.2.noarch

      Environment-Development
      version-jenkins-2.164.1-1.2.noarch

      1. Jenkins.JPG
        Jenkins.JPG
        47 kB
      2. jenkinslogs.JPG
        jenkinslogs.JPG
        221 kB
      3. log.txt
        17 kB

        [JENKINS-56812] java.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor

        Kalpesh Jain added a comment -

        Can some one guess what is this issue missing descriptor

        Kalpesh Jain added a comment - Can some one guess what is this issue missing descriptor

        We are seeing the same warning messages: here is the gist of log just in case.

        Jenkins Version: 2.237 Weekly

        https://gist.github.com/nrayapati/06499ba8a56d7d8d410f64c477e5b2ca

        Naresh Rayapati added a comment - We are seeing the same warning messages: here is the gist of log just in case. Jenkins Version: 2.237 Weekly https://gist.github.com/nrayapati/06499ba8a56d7d8d410f64c477e5b2ca

        We see this in Jenkins 2.249.1 LTS.

        Torsten Kleiber added a comment - We see this in Jenkins 2.249.1 LTS.

        Glenn Herbert added a comment -

        Seeing this in 2.232 Weekly.  Unknown why this continues to happen as our only resort is to restore the entire Jenkins from backup.  This happens more frequently when Jenkins is ineloquently shut down such as a system power loss, but also can occur after installing a plugin and restarting Jenkins.

        Glenn Herbert added a comment - Seeing this in 2.232 Weekly.  Unknown why this continues to happen as our only resort is to restore the entire Jenkins from backup.  This happens more frequently when Jenkins is ineloquently shut down such as a system power loss, but also can occur after installing a plugin and restarting Jenkins.

        we saw this when we upgraded it from jenkins 2.253 to jenkins 2.278 .

        fresh instance works .. but existing instance does not work after upgrade

        Abdennour Toumi added a comment - we saw this when we upgraded it from jenkins 2.253 to jenkins 2.278 . fresh instance works .. but existing instance does not work after upgrade

        Bram Mertens added a comment -

        Seeing this on 2.263.3 as well.

        Bram Mertens added a comment - Seeing this on 2.263.3 as well.

        yuandong xu added a comment -

        Seeing this on 2.316 as well.

        yuandong xu added a comment - Seeing this on 2.316 as well.

        We are seeing this error as well. What is the solution for this error? 

        Farkhod Sadykov added a comment - We are seeing this error as well. What is the solution for this error? 

          Unassigned Unassigned
          kalpesh21 Kalpesh Jain
          Votes:
          7 Vote for this issue
          Watchers:
          21 Start watching this issue

            Created:
            Updated:
            Resolved: