Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36792

Jenkins fails to start with Java 9 / 10 on Debian / Ubuntu

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Debian 8.5

      java version "1.8.0_91"
      Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

      Jenkins 2.14
    • Similar Issues:

      Description

      After running apt-get update / upgrade and Jenkins is updated from 2.13 to 2.14 by the package, it failed to start.

      I have also noticed this in previous 2.x upgrades as well. After I reboot my system, it loads correctly.

      sudo systemctl status jenkins.service
      ● jenkins.service - LSB: Start Jenkins at boot time
      Loaded: loaded (/etc/init.d/jenkins)
      Active: failed (Result: exit-code) since Tue 2016-07-19 05:58:50 EDT; 41s ago
      Process: 2079 ExecStop=/etc/init.d/jenkins stop (code=exited, status=0/SUCCESS )
      Process: 2120 ExecStart=/etc/init.d/jenkins start (code=exited, status=7)

      su[2135]: Successful su for jenkins by root
      su[2135]: + ??? root:jenkins
      su[2135]: pam_unix(su:session): session opened for u...0)
      jenkins[2120]: Starting Jenkins Continuous Integrati...d!
      systemd[1]: jenkins.service: control process exited,...=7
      systemd[1]: Failed to start LSB: Start Jenkins at bo...e.
      systemd[1]: Unit jenkins.service entered failed state.

        Attachments

          Issue Links

            Activity

            Hide
            antgel Antony Gelberg added a comment -

            Patrick Dayton Any clues? Hit me as well, it's open for a couple of years.

            Show
            antgel Antony Gelberg added a comment - Patrick Dayton Any clues? Hit me as well, it's open for a couple of years.
            Hide
            daytonpa Patrick Dayton added a comment - - edited

            I have no idea why I was assigned to this.  I don't do anything regarding development with Jenkins, except simply use it.  What's the output from

            `cat /var/log/jenkins`?

            Show
            daytonpa Patrick Dayton added a comment - - edited I have no idea why I was assigned to this.  I don't do anything regarding development with Jenkins, except simply use it.  What's the output from `cat /var/log/jenkins`?
            Hide
            antgel Antony Gelberg added a comment -

            Patrick Dayton We already deleted the log. NB Moving to Java 8 solved the problem (I had been using Java 10, Ubuntu 18.04). I'll edit the bug title and unassign, hopefully it will get picked up. I don't even know if newer Javas are supported.

            Show
            antgel Antony Gelberg added a comment - Patrick Dayton We already deleted the log. NB Moving to Java 8 solved the problem (I had been using Java 10, Ubuntu 18.04). I'll edit the bug title and unassign, hopefully it will get picked up. I don't even know if newer Javas are supported.
            Hide
            dnusbaum Devin Nusbaum added a comment - - edited

            Antony Gelberg Jenkins does not currently support Java 9+. JENKINS-40689 is an epic that aggregates many of the specific issues that occur in newer Java versions, so feel free to follow that instead and add any new issues that are not already in the list.

            When running Jenkins 2.111 or newer directly via the war (java -jar jenkins.war) fails because of the Java version, you should get a message on stderr that explains that Java 8 is required. See JENKINS-49737. If that isn't working for you then it might be worth opening a new issue either as a feature request if you aren't running the war directly or a bug if you are running it directly.

            Show
            dnusbaum Devin Nusbaum added a comment - - edited Antony Gelberg  Jenkins does not currently support Java 9+. JENKINS-40689 is an epic that aggregates many of the specific issues that occur in newer Java versions, so feel free to follow that instead and add any new issues that are not already in the list. When running Jenkins 2.111 or newer directly via the war ( java -jar jenkins.war ) fails because of the Java version, you should get a message on stderr that explains that Java 8 is required. See  JENKINS-49737 . If that isn't working for you then it might be worth opening a new issue either as a feature request if you aren't running the war directly or a bug if you are running it directly.
            Hide
            antgel Antony Gelberg added a comment -

            Devin Nusbaum Thanks for the info. No such message from the Debian package - I think people will end up here, I changed the title to suit.

            Show
            antgel Antony Gelberg added a comment - Devin Nusbaum Thanks for the info. No such message from the Debian package - I think people will end up here, I changed the title to suit.

              People

              • Assignee:
                Unassigned
                Reporter:
                audiotech520 Shawn M
              • Votes:
                3 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated: