So because I asked for clairification initially, this cannned response isn’t 100% applicable. But generally what we’ve seen is people initially install jenkins with a package manager (which i figure your systemd script comes from), then upgrade the war file directly, and with the switch to systemd in 2.332.1, everything went crazy. The recommendation is to update your package manager installed version.
If you have manually created your systemd service files, its worth posting them so we can see more of what you are doing.
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.
There is a blog post about it as well at
There is also a video introduction for RPM based distributions like Red Hat Enterprise Linux, Alma Linux, Rocky Linux, Oracle Linux, and Amazon Linux.
There is also a video introduction for deb based distributions like Debian and Ubuntu
