# Systemd is failing to launch jenkins **URL:** \ **Category:** Using Jenkins\ **Tags:** question\ **Created:** [November 21, 2024, 4:55pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733 "2024-11-21T16:55:49Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 21, 2024, 4:55pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/1 "2024-11-21T16:55:50Z")
Systemd is failing to launch Jenkins with error message ```auto jenkins.service: Job jenkins.service/start failed with result 'dependency'. ``` I tried launching jenkins with jenkins username, also tried a different username defining its name in override.conf but I am still getting same error. Please suggest. Jenkins setup: ```auto $ grep -vE '^$|^#' /etc/default/jenkins NAME=jenkins JAVA_ARGS="-Djava.awt.headless=true" PIDFILE=/var/run/$NAME/$NAME.pid JENKINS_USER=$NAME JENKINS_GROUP=$NAME JENKINS_WAR=/usr/share/java/$NAME.war JENKINS_HOME=/var/lib/$NAME RUN_STANDALONE=true JENKINS_LOG=/var/log/$NAME/$NAME.log JENKINS_ENABLE_ACCESS_LOG="no" MAXOPENFILES=8192 HTTP_PORT=8080 PREFIX=/$NAME JENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=$HTTP_PORT" $ sudo systemctl status jenkins.service ● jenkins.service - Jenkins Continuous Integration Server Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/jenkins.service.d └─override.conf Active: inactive (dead) Nov 21 08:01:54 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:01:54 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 08:11:12 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:11:12 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 08:19:04 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:19:04 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 16:36:48 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 16:36:48 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 16:47:08 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 16:47:08 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. $ ls -ld /var/lib/jenkins/ drwxr-xr-x 2 jenkins jenkins 4096 Oct 2 11:43 /var/lib/jenkins/ $ ls -ld /var/log/jenkins/ drwxr-xr-x 2 jenkins jenkins 4096 Oct 2 11:43 /var/log/jenkins/ $ ls -ld /var/cache/jenkins drwxr-x--- 2 jenkins jenkins 4096 Oct 2 11:43 /var/cache/jenkins ``` Packages: ```auto $ dpkg -l | grep jenkins ii jenkins 2.462.3 all Jenkins is the leading open source automation server supported by a large and growing community of developers, testers, designers and other people interested in continuous integration, continuous delivery and modern software delivery practices. Built on the Java Virtual Machine (JVM), it provides more than 1,800 plugins that extend Jenkins to automate with practically any technology software delivery teams use. In 2022, Jenkins reached 300,000 known installations making it the most widely deployed automation server. $ dpkg -l | grep java ii ca-certificates-java 20190405ubuntu1.1 all Common CA certificates (JKS keystore) ii java-common 0.72 all Base package for Java runtimes ii libatk-wrapper-java 0.37.1-1 all ATK implementation for Java using JNI ii libatk-wrapper-java-jni:amd64 0.37.1-1 amd64 ATK implementation for Java using JNI (JNI bindings) $ dpkg -l | grep jdk ii openjdk-17-jre:amd64 17.0.13+11-2ubuntu1~20.04 amd64 OpenJDK Java runtime, using Hotspot JIT ii openjdk-17-jre-headless:amd64 17.0.13+11-2ubuntu1~20.04 amd64 OpenJDK Java runtime, using Hotspot JIT (headless) ``` Content of override.conf ```auto $ cat /etc/systemd/system/jenkins.service.d/override.conf [Service] Environment="JAVA_OPTS=-Xms4g -Xmx16g -XX:+UseG1GC -Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=false -Dhudson.model.DirectoryBrowserSupport.CSP=" Environment="JENKINS_LOG=/var/log/jenkins/jenkins.log" ``` ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [November 21, 2024, 7:28pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/2 "2024-11-21T19:28:28Z")
We would need logs to try and understand what’s going on. ---
**Author:** ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)\ **Post date:** [November 21, 2024, 8:11pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/3 "2024-11-21T20:11:34Z")
hmm, the Jenkins service only depends on the `network` service. So if that would be down and not starting Jenkins itself will not start. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [November 21, 2024, 8:47pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/4 "2024-11-21T20:47:19Z")
Only peripherally related to your question, but comments provided in case they help. > [@ddas](#): > > Jenkins setup: > > ```auto > $ grep -vE '^$|^#' /etc/default/jenkins > > ``` Jenkins does not use `/etc/default/jenkins` when installed with a Linux package manager. The `systemd` overrides are used to customize options. > [@ddas](#): > > ```auto > $ dpkg -l | grep jdk > ii openjdk-17-jre:amd64 17.0.13+11-2ubuntu1~20.04 > ii openjdk-17-jre-headless:amd64 17.0.13+11-2ubuntu1~20.04 > > ``` Jenkins support for Ubuntu 20.04 will end in less than 6 months when Ubuntu ends their public support of Ubuntu 20.04. Use Ubuntu 22.04 or Ubuntu 24.04 for a longer operating system life and a longer time running on an operating system that Jenkins supports. ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 22, 2024, 3:56am UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/5 "2024-11-22T03:56:44Z")
Thanks for looking. Unfortunately, I do not see any useful longlines other than these, initially I thought something systemd is depending on is failing but I am not sure what is it, network connection is good, can ping the gateway, can reach internet. ```auto $ ping 8.8.8.8 -c 4 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=1.78 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=1.84 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=1.83 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=1.88 ms --- 8.8.8.8 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 1.778/1.832/1.876/0.035 ms ``` journalctl -u jenkins provides these below ```auto Nov 21 07:42:20 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 07:42:20 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 07:43:53 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 07:43:53 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. -- Reboot -- Nov 21 08:01:54 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:01:54 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 08:11:12 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:11:12 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 08:19:04 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 08:19:04 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 16:36:48 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 16:36:48 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. Nov 21 16:47:08 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 16:47:08 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. -- Reboot -- Nov 21 17:01:10 ppe-jenkins-worker01 systemd[1]: Dependency failed for Jenkins Continuous Integration Server. Nov 21 17:01:10 ppe-jenkins-worker01 systemd[1]: jenkins.service: Job jenkins.service/start failed with result 'dependency'. ``` ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 22, 2024, 4:01am UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/6 "2024-11-22T04:01:02Z")
Thanks for your response. I am able to reach the gateway and internet, so should not be network related, I could ssh to this jenkins box from a remote system in same network. ```auto $ ping -c 4 pkg.jenkins.io PING dualstack.d.sni.global.fastly.net (199.232.46.133) 56(84) bytes of data. 64 bytes from 199.232.46.133 (199.232.46.133): icmp_seq=1 ttl=51 time=36.7 ms 64 bytes from 199.232.46.133 (199.232.46.133): icmp_seq=2 ttl=51 time=37.0 ms 64 bytes from 199.232.46.133 (199.232.46.133): icmp_seq=3 ttl=51 time=37.0 ms 64 bytes from 199.232.46.133 (199.232.46.133): icmp_seq=4 ttl=51 time=37.0 ms --- dualstack.d.sni.global.fastly.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 36.691/36.901/36.998/0.122 ms ``` ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 22, 2024, 4:12am UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/7 "2024-11-22T04:12:22Z")
Thanks for your response, appreciate it. Here is what I have in the unit file. ```auto $ grep -vE '^$|^#' /lib/systemd/system/jenkins.service [Unit] Description=Jenkins Continuous Integration Server Requires=network.target After=network.target [Service] Type=notify NotifyAccess=main ExecStart=/usr/bin/jenkins Restart=on-failure SuccessExitStatus=143 User=jenkins Group=jenkins Environment="JENKINS_HOME=/var/lib/jenkins" WorkingDirectory=/var/lib/jenkins Environment="JENKINS_WEBROOT=%C/jenkins/war" Environment="JAVA_OPTS=-Djava.awt.headless=true" Environment="JENKINS_PORT=8080" [Install] WantedBy=multi-user.target ``` We (my employer) are not ready to roll out U22 or U24 yet ☹ so looking for some way to debug further and find out the root cause why systemd is failing. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [November 22, 2024, 6:01am UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/8 "2024-11-22T06:01:32Z")
The `/lib/systemd/system/jenkins.service` contents match with the contents on my Ubuntu 22.04 system. Does the override file contain anything suspicious? `/etc/systemd/system/jenkins.service.d/override.conf` is the override file on my Ubuntu 22.04 system. ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [November 22, 2024, 5:20pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/9 "2024-11-22T17:20:23Z")
- To check the status of your network service, please type `systemctl is-active network.target`. - If you’re looking for detailed error messages, go ahead and run `systemctl start jenkins.service -l`. - Want more verbose logs? Try `journalctl -u jenkins -xe`. - Make sure that your Java runtime is configured correctly and accessible. ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 26, 2024, 7:29pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/10 "2024-11-26T19:29:30Z")
Perfect, thank you so much, it helped. ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 26, 2024, 7:31pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/11 "2024-11-26T19:31:45Z")
I had to make multiple corrections in that `/etc/systemd/system/jenkins.service.d/override.conf` file. It now looks something like this. ```auto [Service] User=ansible Group=ansible Environment="JAVA_OPTS=-Xms4g -Xmx16g -XX:+AlwaysPreTouch -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/ -XX:+UseG1GC -XX:+UseStringDeduplication -XX:+ParallelRefProcEnabled -XX:+DisableExplicitGC -XX:+UnlockDiagnosticVMOptions -XX:+UnlockExperimentalVMOptions -Xlog:gc*=info,gc+heap=debug,gc+ref*=debug,gc+ergo*=trace,gc+age*=trace:file=/var/log/jenkins/gc.log:utctime,pid,level,tags:filecount=2,filesize=100M -XX:ErrorFile=/var/log/jenkins/hs_err_%p.log -XX:+LogVMOutput -XX:LogFile=/var/log/jenkins/hs_%p.log -Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=false -Dhudson.model.DirectoryBrowserSupport.CSP= -Djava.io.tmpdir=/var/lib/jenkins/tmp" ``` And finally I got it to work. ---
**Author:** ![ddas](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@ddas](https://community.jenkins.io/u/ddas)\ **Post date:** [November 26, 2024, 7:42pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/12 "2024-11-26T19:42:48Z")
I made changes to the order in which I was trying to install the packages, and launch the jenkins service with a different username other than `jenkins`, it’s `ansible` in this case. 1. After removing override.conf, purging packages and re-installing openjdk-11, jenkins, plugins, jenkins service came up running with `jenkins` user. 2. I then created the override.conf file with necessary changes. 3. chown’d the /var/lib/jenkins /var/log/jenkins /var/cache/jenkins directories to provide access to `ansible` user. 4. Restarted the jenkins service, and it came back running with `ansible` user as intended. ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [November 26, 2024, 8:10pm UTC](https://community.jenkins.io/t/systemd-is-failing-to-launch-jenkins/23733/13 "2024-11-26T20:10:39Z")
Thanks a lot for the feedback, @ddas ! 👍