Cannot log in after 2.3 > 2.5 upgrade

Using Jenkins Ask a question
1

Ok. This replaces my earlier question. I am moving forward to simply get 2.5 with Java 21 (MS open java 21) working instead of fixing the old.

I have a backup (files) of the old Jenkins directory including all jobs in the 2.3 / Java 8 format.

After upgrading both java and jenkins I now get the “Log in to Jenkins screen” wanting Username and Password. The username and password we were using does not work. So I followed instructions changing useSecurity to false. It still comes up to this screen.

NOTE: 2.5 was installed OVER the existing 2.3 installation. (same programdata\jenkins directory).

Jenkins is running on a Win Server 2019 system.

2

With 2.5 I assume you mean 2.504.1 and with 2.3 some 2.3xx.x version? Which one exactly?
Have you also updated the plugins? Have you checked the upgrade guide. As this seems to be a big jump over several years in Jenkins releases it is likely that that you need to update some plugins manually.
You should check the logs for any plugin not being loaded properly.

3

I did not update plugins before the upgrade. :anguished_face: Sigh. This’ll be fun since uninstalling new and reinstalling old and using my backup directory now does the same thing in the old version.

Sorry - even older. 2.213 > 2.504.1

4

That’s almost 6 years.

I would try the following:

  • first collect all plugins you have currently installed, just the technical name (this is basically all the .jpi files in the plugins folder without the extension) and write that in a file one plugin per line
  • Use the GitHub - jenkinsci/plugin-installation-manager-tool: Plugin Manager CLI tool for Jenkins to download the latest version of the plugins into a separate folder
  • Copy all the downloaded .jpi files into the plugins folder of your Jenkins
  • start Jenkins
5

Thanks. I was just looking at the (long) list of plugins. I shall do that and see where I am.

Log file says “Jenkins is fully up and running”.

Oh - I started to look at the upgrade guide, but it was 22 processes to go through.

6

Skip / remove “suspended” plugins? Are the folders with the same name important at this point?

7

the folders are not important, they are basically just the jpi extracted.

Even when it says Jenkins is fully up and running there can be plugin loading problems which would be in the log earlier

8

Almost there. Since I had a copy of the entire old system, I did a “clean” install of everything and have been slowly moving my jobs etc back in.

I have jobs, a vSphere cloud, and my nodes. I think all I have to finish is my credentials!

9

Update: Had to add manually OopenWebStart to the environment path.

I now get Could not read or parse the jnlp fila at (jenkins jnlp path)

If I download the jnlp (which appears to have legit info) and run locally i get the same error. So, OpenWebStart DOES “download” from jenkins but doesn’t like something jenkins is sending?

Original:
Ok. IF I’m reading things right, javaws will no longer work as a agent side launch. I was using:

javaws http://jenkins1:9191/computer/vm-test-10x64c/slave-agent.jnlp
Now I am on 2.504 and Java 21 and information seems to indicate javaws is deprecated (LONG ago) and to use WebStart. Which I donwload on the agent and installed.

I am unsure the command line to use now from the agent to grab and execute the .jnlp now?

I think this is the last roadblock to being fully running.

BTW - doing the fresh install and doing a small amount of user/cloud reconfigure and pulling in nodes/jobs was FAR easier in the end doing such a LONG upgrade.