# \[SOLVED\] Did a system upgrade, now I can't log in

**URL:** <https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525>\
**Category:** Using Jenkins\
**Created:** [January 8, 2025, 10:40am UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525 "2025-01-08T10:40:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![snailgun](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@snailgun](https://community.jenkins.io/u/snailgun)\
**Post date:** [January 8, 2025, 10:40am UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525/1 "2025-01-08T10:40:31Z")

</div>

It all started with me getting notified that some plugins needed to be updated. Updated them and opted for the automatic restart of Jenkins.  
That worked fine but then I did a system upgrade and after that I’m greeted with:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/4/45cfbf7dd58b2baf9665f70716ccc799fae804df.png)

I’ve tried logging in with both local and AD accounts.

OS: FreeBSD  
Jenkins: 2.487  
Java: 21

While troubleshooting I found this in the logs:

```auto
WARNING	h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID e12ee04b-ca04-4ba0-8939-a5b4eb9801d6
java.lang.NoSuchMethodError: 'void org.springframework.util.Assert.isTrue(boolean)'
	at PluginClassLoader for ldap//org.springframework.ldap.support.LdapUtils$CollectingAttributeValueCallbackHandler.handleAttributeValue(LdapUtils.java:343)

```

We’ve got a NGINX as reverse proxy running on the same machine.

Any help is much appreciated.  
Thanks in advance!

---

<div class="post-metadata">

**Author:** ![slide\_o\_mix](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/slide_o_mix/32/20977_2.png) [@slide\_o\_mix](https://community.jenkins.io/u/slide_o_mix)\
**Post date:** [January 8, 2025, 11:50am UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525/2 "2025-01-08T11:50:57Z")

</div>

It looks like you are running into the known issue with 2.479.1 and the LDAP plugin which requires a new release of the LDAP plugin (see release notes for 2.479.1 [Changelog](https://www.jenkins.io/changelog-stable/2.479.1/)) see here for information from the upgrade guide: [Upgrading to Jenkins LTS 2.479.x](https://www.jenkins.io/doc/upgrade-guide/2.479/#upgrade-spring-security-spring-framework-and-servlet-containers)

---

<div class="post-metadata">

**Author:** ![snailgun](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@snailgun](https://community.jenkins.io/u/snailgun)\
**Post date:** [January 8, 2025, 2:22pm UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525/3 "2025-01-08T14:22:45Z")

</div>

Thanks a lot!  
At least that error is gone but now I get this:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/7/7ffbf613f5baa1bd1dbd361e666c348ba4280edd.png)

And in the logs:

```auto
025-01-08 14:12:35.678+0000 [id=23]	SEVERE	jenkins.model.Jenkins#save: An attempt to save Jenkins'' global configuration before it has been loaded has been made during milestone Completed initialization. This is indicative of a bug in the caller and may lead to full or partial loss of configuration.
java.lang.IllegalStateException: call trace
	at jenkins.model.Jenkins.save(Jenkins.java:3519)
	at jenkins.model.Jenkins.<init>(Jenkins.java:998)
	at hudson.model.Hudson.<init>(Hudson.java:102)
	at hudson.model.Hudson.<init>(Hudson.java:87)
	at hudson.WebAppMain$3.run(WebAppMain.java:249)
2025-01-08 14:12:35.678+0000 [id=23]	SEVERE	hudson.util.BootFailure#publish: Failed to initialize Jenkins
java.lang.IllegalStateException: An attempt to save the global configuration was made before it was loaded
	at jenkins.model.Jenkins.save(Jenkins.java:3528)
	at jenkins.model.Jenkins.<init>(Jenkins.java:998)
	at hudson.model.Hudson.<init>(Hudson.java:102)
	at hudson.model.Hudson.<init>(Hudson.java:87)
	at hudson.WebAppMain$3.run(WebAppMain.java:249)
Caused: hudson.util.HudsonFailedToLoad
	at hudson.WebAppMain$3.run(WebAppMain.java:277)

```

Should I downgrade to jenkins-lts-2.479.2\_1 or it should work with our current version as well?  
Sorry if my questions sound nooby but this is my first time operating Jenkins 🙂

---

<div class="post-metadata">

**Author:** ![slide\_o\_mix](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/slide_o_mix/32/20977_2.png) [@slide\_o\_mix](https://community.jenkins.io/u/slide_o_mix)\
**Post date:** [January 8, 2025, 3:26pm UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525/4 "2025-01-08T15:26:04Z")

</div>

I would definitely recommend sticking with the LTS (stable) release line. The LTS release line has much more testing and is generally better for production environments.

---

<div class="post-metadata">

**Author:** ![snailgun](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@snailgun](https://community.jenkins.io/u/snailgun)\
**Post date:** [January 8, 2025, 4:06pm UTC](https://community.jenkins.io/t/solved-did-a-system-upgrade-now-i-cant-log-in/25525/5 "2025-01-08T16:06:29Z")

</div>

My guy. You’re a total life saver! 😃

Running the LTS now with OpenJDK21 and it’s back in business 🥳