Version upgrade - Jenkins service getting failed but the application is running fine

[vishnu]

We have upgraded our jenkins instance from 2.277.4 to 2.319.3 using jenkins.war. After upgrade, the jenkins service is getting failed [systemctl] but the application is up and running fine. Can anyone help to fix this issue.

[halkeye (Gavin Mogan)]

tl;dr don’t upgrade war if you are using system packages, update system packages

---

Hi there,

Jenkins 2.332.1 switched Jenkins from using System V init to use systemd with its Linux package installers for Debian, Ubuntu, Red Hat, Alma, openSUSE, Rocky, and more. The LTS Upgrade Guide describes that transition and how to adapt your environment to the transition.

Upgrading to Jenkins LTS 2.332.x

There is a blog post about it as well at

Linux installation packages migrated from System V init to systemd

There is also a video introduction for RPM based distributions like Red Hat Enterprise Linux, Alma Linux, Rocky Linux, Oracle Linux, and Amazon Linux.

🔴 Managing the Jenkins systemd Service on CentOS 7.9

There is also a video introduction for deb based distributions like Debian and Ubuntu

🔴 Managing the Jenkins systemd Service on Ubuntu 20.04

[vishnu]

Hi Gavin,

Thanks for your response. Can you please provide the alternate way to upgrade jenkins to 2.319.3 instead of war file upgrade. The current version has been installed using war file.

As you said, 2.332.1 switched Jenkins from using System V init to use systemd. But we are upgrading to 2.319.3 only, so we would like to understand why the service is going to failed state.