Details
-
Improvement
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
-
2.335, 2.332.1
Description
Currently debian packages (and presumably redhat/suse/etc) ship with old style SysV init.d file.
Most distributions are now systemd based, and to be able to make use of it's additional features it would be useful have /lib/systemd/system/jenkins.service file.
This would allow features like systemd's restart functionality to work (useful when Jenkins occasionally crashes, etc). See discussion around this here: http://serverfault.com/questions/760552/how-to-use-automatic-restart-with-jenkins-on-systemd
Details of how provide both systemd unit file and SysV init file are detailed here:
https://wiki.debian.org/Teams/pkg-systemd/Packaging
This should be applicable to all distro, and systemd unit most likely the same across them all, as it's much more standardised than each distros SysV init infrastructure.
Attachments
Issue Links
- is related to
-
JENKINS-65809 Jenkins fails to restart after plugin updates on Debian 11 (bullseye)
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Resolved
-
- links to
Activity
We just upgraded LTS from 2.319.3 to 2.332.1 and this seemed to break our install. To fix we had to manually re-enable the service with:
systemctl enable jenkins
After running that, all is well.
drew j
added a comment - We've recently upgraded to LTS 2.332.1 as well and have noticed that on RHEL-based distos, the shipped unit file does not respect the configuration which is still written to `/etc/sysconfig/jenkins`.
We had a custom `JENKINS_JAVA_CMD` statement which was ignored as a part of rebuilding on the new LTS version, which caused the service to fail to start up.
I think if the RHEL package is going to ship wit h `/etc/sysconfig/jenkins`, the unit file needs to respect it when it's altered.
drew j
added a comment - We've recently upgraded to LTS 2.332.1 as well and have noticed that on RHEL-based distos, the shipped unit file does not respect the configuration which is still written to `/etc/sysconfig/jenkins`.
We had a custom `JENKINS_JAVA_CMD` statement which was ignored as a part of rebuilding on the new LTS version, which caused the service to fail to start up.
I think if the RHEL package is going to ship wit h `/etc/sysconfig/jenkins`, the unit file needs to respect it when it's altered. 
Ian Williams
added a comment - hybby, that should probably be a new issue, linked to this one as this issue is closed.
Ian Williams
added a comment - hybby , that should probably be a new issue, linked to this one as this issue is closed. 
Basil Crow
added a comment - lkisac01 Kindly refrain from commenting on closed tickets with requests for help that have nothing to do with the ticket you are commenting on. This is a bug tracker, not a help desk. A quick search of this bug tracker will show that you are looking for JENKINS-67165. For further requests for help please post to the user mailing list.
Basil Crow
added a comment - lkisac01 Kindly refrain from commenting on closed tickets with requests for help that have nothing to do with the ticket you are commenting on. This is a bug tracker, not a help desk. A quick search of this bug tracker will show that you are looking for JENKINS-67165 . For further requests for help please post to the user mailing list . 
zbynek Fixed in jenkinsci/packaging#285 toward Jenkins 2.336. In the future, please file a new Jira issue with details about the Linux distribution being used and steps to reproduce the problem.