// troubleshooting guide · jenkins

Jenkins Not Starting: 'Job for jenkins.service failed'

Status
Workaround available
platforms:
Linux (systemd), Windows service
updated:
November 16, 2026
reports:
4
Method
how we research
Share

RUNBOOK · jenkins/not-starting5 FIXES

// quick answer

The systemd message is generic. Read journalctl for the real error: usually Java is missing or too old (current Jenkins needs Java 21 or 25), port 8080 is taken, or startup timed out.

Most likely fix: Read the real error

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Read the real error

    1. 01Run sudo systemctl status jenkins
    2. 02Run sudo journalctl -u jenkins -xe and find the first error line
    3. 03Look for 'failed to find a valid Java installation', 'failed to bind' or plugin stack traces
    Did this fix it?
  2. FIX 2Install a supported Java

    1. 01Run java -version
    2. 02Current weekly and LTS releases need Java 21 or 25; install one (e.g. sudo apt install openjdk-21-jre)
    3. 03If several JDKs exist, set the path with sudo systemctl edit jenkins and Environment="JAVA_HOME=/path/to/jdk"
    4. 04sudo systemctl daemon-reload && sudo systemctl restart jenkins
    Did this fix it?
  3. FIX 3Free or change the port

    1. 01Run sudo ss -ltnp | grep 8080 to find what uses the port
    2. 02Stop that service, or set Environment="JENKINS_PORT=8081" via sudo systemctl edit jenkins
    3. 03Restart Jenkins
    Did this fix it?
  4. FIX 4Raise the startup timeout

    1. 01Run sudo systemctl edit jenkins
    2. 02Add [Service] and TimeoutStartSec=infinity (or a large value)
    3. 03Reload systemd and restart
    Did this fix it?
  5. FIX 5Check JENKINS_HOME ownership

    1. 01Run ls -ld /var/lib/jenkins
    2. 02If needed: sudo chown -R jenkins:jenkins /var/lib/jenkins
    3. 03Restart Jenkins
    Did this fix it?

SANDBOX · jenkins RUNS IN YOUR BROWSER

Try it: push, review, run CI and merge in a code host and cloud workspace

A hands-on Jenkins-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

systemctl start jenkins fails with 'Job for jenkins.service failed because the control process exited with error code' or 'Start request repeated too quickly', and the web UI is unreachable.

Why it happens

  • C-01No valid Java found, or Java too old for this Jenkins version (Java 17 support ended in 2026)
  • C-02Another process already uses port 8080
  • C-03Startup takes longer than systemd's timeout on big installs
  • C-04A plugin or config error after an upgrade
  • C-05Wrong permissions on JENKINS_HOME

// this guide also covers

  • jenkins not starting
  • job for jenkins.service failed
  • jenkins failed to find a valid java installation
  • jenkins service won't start

Still not working?

If Jenkins keeps failing, you're not alone. See every Jenkins problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Jenkins Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Jenkins errors

All 14 Jenkins errors and fixes →