Error while upgrading Jenkin from 2.308 to 2.319

Hi Team,

I am upgrading Jenkin version from 2.308 to 2.319.

After replacing the 2.319 WAR file when I restart the service Jenkin GUI is up but Jenkin service is failed.

Jenkin service start Error :
[root@jenkins]# sudo service jenkins start
Starting jenkins (via systemctl): Job for jenkins.service failed because a timeout was exceeded. See “systemctl status jenkins.service” and “journalctl -xe” for details.
[root@ jenkins]#

[root@Jenkin default]# sudo service jenkins status
● jenkins.service - LSB: Jenkins Automation Server
Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
Active: failed (Result: timeout) since Sun 2022-12-04 23:50:49 IST; 20min ago
Docs: man:systemd-sysv-generator(8)

Dec 04 23:45:49 Linux-Jenkins systemd[1]: Starting LSB: Jenkins Automation Server…
Dec 04 23:45:49 Linux-Jenkins runuser[15914]: pam_unix(runuser:session): session opened for user jenkins by (uid=0)
Dec 04 23:50:49 Linux-Jenkins systemd[1]: jenkins.service start operation timed out. Terminating.
Dec 04 23:50:49 Linux-Jenkins systemd[1]: Failed to start LSB: Jenkins Automation Server.
Dec 04 23:50:49 Linux-Jenkins systemd[1]: Unit jenkins.service entered failed state.
Dec 04 23:50:49 Linux-Jenkins systemd[1]: jenkins.service failed.
Dec 04 23:52:20 Linux-Jenkins jenkins[15907]: Starting Jenkins Killed
[root@Jenkins default]

Java Version:

[root@Jenkins ~]# java -version
java version “1.8.0_291”
Java™ SE Runtime Environment (build - pxa6480sr6fp30-20210507_01(SR6 FP30))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20210415_469669 (JIT enabled, AOT enabled)
OpenJ9 - c2bc063
OMR - fa000e8
IBM - 8165371)
JCL - 20210419_01 based on Oracle jdk8u291-b09
[root@Dubois-Jenkins ~]#

Please help me in resolving the issue and provide the steps to upgrade Jenkin.

Thanks & Regards,
Harish Sharma

So 319 is a weekly release from a year ago. Generally stable releases are the ones with upgrade guides.

This just says there is an error. As with your other thread, check your Jenkins server logs. Probably plugins need updating.

Hello @harishpunj and welcome to this community :wave: .

Was the Jenkins service installed by your Linux distribution, or did you do it by yourself?

Beginning with Jenkins 2.332.1 and Jenkins 2.335, the Linux package installers use systemd to manage services. The RPM and deb package installers migrate configuration settings from System V init to systemd overrides.

I guess it’s a home-made systemd service you declared, am I right?

I thought this was it too, but 319 is older than 332

its just using the auto init.d systemd scripts that linux has

1 Like

Hekllo Halkeye,
Good Day…
In my jenkins system i hve the same issue for which this thread creates. Could u please suggest what need to be done to get sort out the issue.
Linux-Jenkins systemd[1]: Starting LSB: Jenkins Automation Server…
Urgent help needed

If you have the same issue, then you likely made the same mistake.

The original mistake was:

Don’t do that. Do not upgrade by replacing the war file with a newer version of the war file. Use the operating system package manager (apt, yum, dnf, zypper, etc.) to perform the upgrade.

Using a Jenkins version (like 2.319.x) with known security vulnerabilities that is not receiving any security fixes is unwise. Make a plan and find a way to upgrade to a recent release so that others are more likely to be willing to help with questions. Questions on versions that were released a year ago are much less likely to receive answers than questions on current versions.

You’ll need to provide detailed logs of the failure messages that are reported on your system. Without log files, all that can be offered are guesses of things that might have gone wrong.

The person who did upgrade last year he just replace war file and somehow manipulate config.xml file also rpm package version of Jenkins is 2.289. So please suggest what need to do.
Current RPM package:- 2.289
Jenkins version in config.xml:- 2.319

I think we have been really clear. If installed via yum or apt, upgrade via yum or apt. Don’t upgrade by replacing the war file.

1 Like

So what should we do now, could u please suggest on this.

Follow the instructions that were provided when the post said:

Use the operating system package manager to perform the upgrade.

So its been already done in the last year war file replaced with 2.319 and config.xml is showing new version. Now help me for following questions:
Is that any possibilities we can upgrade 2.289 rpm to 2.319 only
As if i tried to upgrade rpm version 2.289 using rum upgrade it will directly take 2.388 which is latest that would be issue as it having huge gap and lots of dependencies.

We are not trying to be rude, but it’s exhausting to repeat yourself to people who don’t put effort in.

Thanks for help but i did search a lot and when the things is not catchable, person become undesirable state and need help and guidance .
Thanks fr support