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

After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • crowd2-plugin
    • None

      I tried to install the crowd 2 plugin as per instructions, here: https://stackoverflow.com/questions/15411208/authenticate-jenkins-users-against-jira

      I downloaded the plugin through the available tab in the plugins page.

      This resulted in exception as described here: https://issues.jenkins-ci.org/browse/JENKINS-59301 

      Before I could resolve this, the jenkins install was updated to 2.204.4. When I tried to login after the update, the exception occurred immedialetly after login. See the attached file for the stack-trace that is displayed.

      Now I cannot do anything at all in jenkins. I suppose uninstalling the crowd 2 plugin could solve this for now, but I have no idea how since the jenkins admin page is inaccessible.

        1. Error-2.txt
          6 kB
        2. stack-trace.txt
          14 kB

          [JENKINS-61322] After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login

          Mark Hagers added a comment -

          Update: in an attempt to get our jenkins server back up I manually removed the crowd2 directory and the file crowd2.jpi from the plugin directory. After restart the jenkins server is now inaccessible without an option to login and displays the error in the second attachment (Error-2.txt)

          What's best to do now? reinstall Jenkins?

          Mark Hagers added a comment - Update: in an attempt to get our jenkins server back up I manually removed the crowd2 directory and the file crowd2.jpi from the plugin directory. After restart the jenkins server is now inaccessible without an option to login and displays the error in the second attachment (Error-2.txt) What's best to do now? reinstall Jenkins?

          Mark Hagers added a comment -

          We solved this by restoring from a backup, so this is not very urgent currently.

          Even though few people may run into this, I still think this is a potentially serious issue:
          If you install a plugin that affects logging into jenkins (such as the crowd 2 plugin) and the plugin runs into a problem you may be unable to log in. There is no good recovery path from there, since you'll be unable to uninstall the plugin.

          Mark Hagers added a comment - We solved this by restoring from a backup, so this is not very urgent currently. Even though few people may run into this, I still think this is a potentially serious issue: If you install a plugin that affects logging into jenkins (such as the crowd 2 plugin) and the plugin runs into a problem you may be unable to log in. There is no good recovery path from there, since you'll be unable to uninstall the plugin.

          Kalle Niemitalo added a comment -

          To recover from such errors, you could edit only the securityRealm element in config.xml, I think.

          Kalle Niemitalo added a comment - To recover from such errors, you could edit only the securityRealm element in config.xml, I think.

          Bartosz Nowak added a comment -

          Duplicate JENKINS-59301

          Bartosz Nowak added a comment - Duplicate  JENKINS-59301

            dumam Bartosz Nowak
            markchagers Mark Hagers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: