Hi all, I got a warning of java 11 end of life. so I upgraded java version 11 to 17. But like above image, when I start jenkins service again, error occurred and the error said " Found an incorrect java version". But it I think it directs java 17 well. Anybody knows about this?
Thank you!
And which Jenkins version are you using?
1 Like
I’m using 2.452.3, plus I don’t use docker
/etc/init.d/jenkins looks like this is still the old way and not a real systemd config file. You should check what it is doing.
1 Like
Thank you! I checked /etc/init.d/jenkins file. And the script only admitted 11 java version. I added allowed java version 17 then it worked well. Thank you
1 Like
The Jenkins Linux installers stopped supporting /etc/init.d/jenkins as a configuration file when we switched from System V init to systemd in 2022. If your changes to /etc/init.d/jenkins are recognized by Jenkins, then that probably means that you are using the wrong technique to upgrade Jenkins.
When Jenkins is installed with a Linux package manager (like yum, dnf, apt, and zypper), it needs to be updated with the same Linux package manager. Upgrading the war file yourself does not run the package manager update process and leaves you running new code with old operating system configuration.
1 Like
Omg but I already upgraded jenkins by war file. Is it okay to upgrade package manager from this status???
Yes, though there may be surprises (depending on the package manager) since you’ve changed at least one of the files that is managed by the package manager.
1 Like
@MarkEWaite Thank you so much. I upgraded jenkins well!! It was so easy haha
------ just summary for other -----
- I checked jenkins on apt installed list
- execute apt update
- upgrade jenkins
- restart service