[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.

24 views
Skip to first unread message

joe@mihalich.net (JIRA)

unread,
Apr 18, 2019, 1:21:04 AM4/18/19
to jenkinsc...@googlegroups.com
Joe Mihalich updated an issue
 
Jenkins / Bug JENKINS-57096
The latest debian installers 2.164+ do not work with java 11.
Change By: Joe Mihalich
it's hard to believe i'm the only one experiencing this.  The debian package installer is completely broken for java 11 starting with the supported 2.164.x releases.  When installing on Ubuntu 18.04 with (in my case) openjdk-11-jdk installed, you get the following error:

 
{code:java}
Unpacking jenkins (2.164.2) ...
Setting up jenkins (2.264.2) ...
Job for jenkins.service failed because the control process exited with error code.
See "systemctl status jenkins.service" and "journalctl -xe" for details.
invoke-rc.d: initscript jenkins, action "start" failed.
● jenkins.service - LSB: Start Jenkins at boot time
   Loaded: loaded (/etc/init.d/jenkins; generated)
   Active: failed (Result: exit-code) since Thu 2019-04-18 04:47:26 UTC; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 9040 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Starting LSB: Start Jenkins at boot time...
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Found an incorrect Java version
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Java version found:
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: openjdk version "11.0.2" 2019-01-15
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Aborting
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Control process exited, code=exited status=1
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Failed with result 'exit-code'.
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Failed to start LSB: Start Jenkins at boot time.
{code}
inspection of the jenkins init script in /etc/init.d/jenkins reveals the isssue:
{code:java}
JAVA_ALLOWED_VERSION="18"

 ...

 # Work out the JAVA version we are working with:
JAVA_VERSION=$($JAVA -version 2>&1 | sed -n ';s/.* version "\(.*\)\.\(.*\)\..*"/\1\2/p;')
if [ "$JAVA_VERSION" = "$JAVA_ALLOWED_VERSION" ]; then
    echo "Correct java version found" >&2
else
    echo "Found an incorrect Java version" >&2
    echo "Java version found:" >&2
    echo $($JAVA -version) >&2
    echo "Aborting" >&2
    exit 1
fi
{code}
Obviously the first problem is you're only allowing version 18.  

The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15".  So that command is completely broken for java 11.

With this busted, there's no 'official' way for me to install this on Ubuntu right now.

 
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

joe@mihalich.net (JIRA)

unread,
Apr 18, 2019, 1:21:04 AM4/18/19
to jenkinsc...@googlegroups.com
Joe Mihalich created an issue
Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: core, packaging
Created: 2019-04-18 05:20
Environment: lilnux
Labels: jenkins
Priority: Major Major
Reporter: Joe Mihalich

it's hard to believe i'm the only one experiencing this.  The debian package installer is completely broken for java 11 starting with the supported 2.164.x releases.  When installing on Ubuntu 18.04 with (in my case) openjdk-11-jdk installed, you get the following error:

 

Unpacking jenkins (2.164.2) ...
Setting up jenkins (2.264.2) ...
Job for jenkins.service failed because the control process exited with error code.
See "systemctl status jenkins.service" and "journalctl -xe" for details.
invoke-rc.d: initscript jenkins, action "start" failed.
● jenkins.service - LSB: Start Jenkins at boot time
   Loaded: loaded (/etc/init.d/jenkins; generated)
   Active: failed (Result: exit-code) since Thu 2019-04-18 04:47:26 UTC; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  
Process: 9040 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Starting LSB: Start Jenkins at boot time...
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Found an incorrect Java version
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Java version found:
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: openjdk version "11.0.2" 2019-01-15
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)
Apr 18 04:47:26 ip-10-0-109-178 jenkins[9040]: Aborting
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Control process exited, code=exited status=1
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: jenkins.service: Failed with result 'exit-code'.
Apr 18 04:47:26 ip-10-0-109-178 systemd[1]: Failed to start LSB: Start Jenkins at boot time.

inspection of the jenkins init script in /etc/init.d/jenkins reveals the isssue:

JAVA_ALLOWED_VERSION="18"

# Work out the JAVA version we are working with:
JAVA_VERSION=$($JAVA -version 2>&1 | sed -n ';s/.* version "\(.*\)\.\(.*\)\..*"/\1\2/p;')
if [ "$JAVA_VERSION" = "$JAVA_ALLOWED_VERSION" ]; then
    echo "Correct java version found" >&2
else
    echo "Found an incorrect Java version" >&2
    echo "Java version found:" >&2
    echo $($JAVA -version) >&2
    echo "Aborting" >&2
    exit 1
fi

Obviously the first problem is you're only allowing version 18.  

The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15".  So that command is completely broken for java 11.

With this busted, there's no 'official' way for me to install this on Ubuntu right now.

 

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 18, 2019, 1:38:03 AM4/18/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: java11 java11-compatibility jenkins

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 18, 2019, 1:41:05 AM4/18/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

This is something I missed during the installer review for Java 11 GA.It somehow worked on my test machine, likely a clean environment issue

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 18, 2019, 4:31:01 AM4/18/19
to jenkinsc...@googlegroups.com
Baptiste Mathus assigned an issue to Unassigned
 
Change By: Baptiste Mathus
Assignee: Kohsuke Kawaguchi

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 18, 2019, 5:11:02 AM4/18/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
Change By: Baptiste Mathus
Priority: Major Critical

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 18, 2019, 5:39:02 AM4/18/19
to jenkinsc...@googlegroups.com
Baptiste Mathus commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

We will have a look very soon. Thanks a lot for reporting this.

joe@mihalich.net (JIRA)

unread,
Apr 18, 2019, 12:40:02 PM4/18/19
to jenkinsc...@googlegroups.com

Great, thanks.  In the mean time, i'm running on Java 8.

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 19, 2019, 4:23:04 AM4/19/19
to jenkinsc...@googlegroups.com
Baptiste Mathus assigned an issue to Adrien Lecharpentier
 
Change By: Baptiste Mathus
Assignee: Adrien Lecharpentier

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 19, 2019, 4:23:04 AM4/19/19
to jenkinsc...@googlegroups.com
Baptiste Mathus started work on Bug JENKINS-57096
 
Change By: Baptiste Mathus
Status: Open In Progress

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 19, 2019, 4:23:05 AM4/19/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
Change By: Baptiste Mathus
Labels: java11 java11-compatibility jenkins triaged

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 19, 2019, 11:04:04 AM4/19/19
to jenkinsc...@googlegroups.com
Adrien Lecharpentier commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

Baptiste Mathus Oleg Nenashev I have a question for you: do we want to force the version to be Java 11 or do we still accept to run Jenkins on Java 8? I lean in favor the the acceptance option. (I always try to be inclusive )

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 19, 2019, 11:34:03 AM4/19/19
to jenkinsc...@googlegroups.com

Joe Mihalich I create https://github.com/jenkinsci/packaging/pull/117 with what I validated to be a fix in my case. Could you please check if in your case, it's working as well? Thanks!

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 19, 2019, 11:34:04 AM4/19/19
to jenkinsc...@googlegroups.com
Change By: Adrien Lecharpentier
Status: In Progress Review

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 12:58:01 PM4/19/19
to jenkinsc...@googlegroups.com
Joe Mihalich commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

Yes, I'll try to check it out sometime today, thanks.

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 1:59:02 PM4/19/19
to jenkinsc...@googlegroups.com

Adrien Lecharpentier can you verify how you installed jenkins in your pull request?  I cannot install it via the deb package cuz, at the current point of failure in the deb package install, the /var/lib/jenkins directory is empty.  So, copying in the new jenkins file to /etc/init.d doesn't help me cuz jenkins can't start anyway.

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 1:59:04 PM4/19/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
[~alecharp] can you verify how you installed jenkins in for your pull request test ?  I cannot install it via the deb package cuz, at the current point of failure in the deb package install, the /var/lib/jenkins directory is empty.  So, copying in the new jenkins file to /etc/init.d doesn't help me cuz jenkins can't start anyway.

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 2:00:02 PM4/19/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
[~alecharp] can you verify how you installed jenkins for your pull request test?  I cannot install it via the deb package cuz, at the current point of failure in the deb package install, the /var/lib/jenkins directory is empty.  So, copying in the new jenkins file to /etc/init.d doesn't help me cuz jenkins can't start anyway.   I am using an Ubunty 18.04 VM as well to test this out.

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 19, 2019, 2:06:02 PM4/19/19
to jenkinsc...@googlegroups.com

I followed the instructions from https://jenkins.io/doc/book/installing/#debianubuntu.

The installation was successful, but at the end of the installation process I have a failure when it tries to start Jenkins. Then I changed the /etc/init.d/jenkins script to have the changeset I filled in my PR. After that, I had to systemctl daemon-reload and then I could run service jenkins start.

I used the same version of Ubuntu, with only a apt install openjdk-11-jdk.

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 3:34:02 PM4/19/19
to jenkinsc...@googlegroups.com
Joe Mihalich updated an issue
Change By: Joe Mihalich
Attachment: jenkins-output.txt

joe@mihalich.net (JIRA)

unread,
Apr 19, 2019, 3:34:02 PM4/19/19
to jenkinsc...@googlegroups.com
Joe Mihalich commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

That's exactly what i did.  I started over, and got the same result.  I'm attaching the output of my shell commands for you to see.

Joe

jenkins-output.txt

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 20, 2019, 6:02:02 AM4/20/19
to jenkinsc...@googlegroups.com

Joe Mihalich could you please provide the output of the commands listed at the end of the log you provided? systemctl status jenkins.service and journalctl -xe.

In the meantime, I'll try with the weekly release as you have, as in my case I was testing with the stable branch.

joe@mihalich.net (JIRA)

unread,
Apr 20, 2019, 1:53:01 PM4/20/19
to jenkinsc...@googlegroups.com
Joe Mihalich updated an issue
Change By: Joe Mihalich
Attachment: status-output.txt

joe@mihalich.net (JIRA)

unread,
Apr 20, 2019, 1:53:03 PM4/20/19
to jenkinsc...@googlegroups.com

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 3:52:02 AM4/23/19
to jenkinsc...@googlegroups.com

Thank you Joe Mihalich. I don't see what's wrong. Could you please change the line 67 from

    echo $(JAVA -version) >&2

to 

    echo $JAVA_VERSION

This way, I could see what the sed expression on line 60 returned in your case. Thank you for your patience.

skoh@tensorengr.com (JIRA)

unread,
Apr 23, 2019, 8:58:02 AM4/23/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

If I comment out the section of the code that Joe Mihalich posted.  I am able to continue.  There seems to be a disconnect between the sed script and the java -version output.  Thanks for the tip, Joe.

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 10:08:02 AM4/23/19
to jenkinsc...@googlegroups.com

Song Koh could you please apply what I asked in my previous comment and provide me the same output so I can see what I missed in the sed expression? Thanks.

skoh@tensorengr.com (JIRA)

unread,
Apr 23, 2019, 11:24:02 AM4/23/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

Sure.   The output is...

---------------------------------------------------------

Found an incorrect Java version
Java version found:
110 2019-01-15
Aborting

-------------------------------------------------------------

 

 

skoh@tensorengr.com (JIRA)

unread,
Apr 23, 2019, 11:27:01 AM4/23/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

Just for the record, the original post already had this info...

"The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15". So that command is completely broken for java 11."

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 11:30:03 AM4/23/19
to jenkinsc...@googlegroups.com

Song Koh thank you. I know it was included in the original post, but I thought I fixed it with the PR I filled. Could you please make sure you are using the same /etc/init.d/jenkins context as in https://github.com/jenkinsci/packaging/pull/117? Thanks.

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 11:58:03 AM4/23/19
to jenkinsc...@googlegroups.com

Hi, here's the output you requested:

 

jmihalich@ubuntu1804-jm:~$ sudo /etc/init.d/jenkins start
JAVA_VERSION = 110
Correct java version found
[....] Starting jenkins (via systemctl): jenkins.serviceJob for jenkins.service failed because the control process exited with error code.
See "systemctl status jenkins.service" and "journalctl -xe" for details.
failed!
jmihalich@ubuntu1804-jm:~$ ls -la /var/lib/jenkins
total 8
drwxr-xr-x 2 jenkins jenkins 4096 Apr 22 15:09 .
drwxr-xr-x 36 root root 4096 Apr 23 15:49 ..

 

I want to repeat again that, for whatever reason, after running sudo apt-get install jenkins, and it fails, the /var/lib/jenkins directory is empty. (see above).  That is most likely why jetty startup is failing.

 

Joe

 

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 12:13:04 PM4/23/19
to jenkinsc...@googlegroups.com

thank you Joe Mihalich. So the java version is correctly parsed, the sed expression is correct. The problem must be after that

The fact that the /var/lib/jenkins is empty is not a real surprise, as the instance didn't start once, there is no "jenkins-home" (which is the purpose of the folder).

Could you please provide me the output of journalctl -xe?

Thanks.

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 12:16:04 PM4/23/19
to jenkinsc...@googlegroups.com

jmihalich@ubuntu1804-jm:~$ journalctl -xe
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent (ssh-agent emulation).
– Subject: Unit UNIT has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
– Subject: Unit UNIT has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG network certificate management daemon.
– Subject: Unit UNIT has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
– Subject: Unit UNIT has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache.
– Subject: Unit UNIT has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Reached target Shutdown.
– Subject: Unit UNIT has finished start-up
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has finished starting up.
–
-- The start-up result is RESULT.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Starting Exit the Session...
– Subject: Unit UNIT has begun start-up
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit UNIT has begun starting up.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Received SIGRTMIN+24 from PID 8881 (kill).
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: us...@0.service: Killing process 8881 (kill) with signal SIGKILL.
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Stopped User Manager for UID 0.
– Subject: Unit us...@0.service has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit us...@0.service has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Removed slice User Slice of root.
– Subject: Unit user-0.slice has finished shutting down
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit user-0.slice has finished shutting down.
Apr 23 15:55:14 ubuntu1804-jm jenkins[8814]: ...fail!
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Control process exited, code=exited status=7
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Failed with result 'exit-code'.
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: Failed to start LSB: Start @@PRODUCTNAME@@ at boot time.
– Subject: Unit jenkins.service has failed
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Unit jenkins.service has failed.
–
-- The result is RESULT.
Apr 23 15:55:14 ubuntu1804-jm sudo[8782]: pam_unix(sudo:session): session closed for user root
Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection.
Apr 23 15:58:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available
Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Apr 23 16:08:29 ubuntu1804-jm kernel: e1000: enp0s3 NIC Link is Down
Apr 23 16:08:29 ubuntu1804-jm systemd-networkd[647]: enp0s3: Lost carrier
Apr 23 16:08:29 ubuntu1804-jm systemd-networkd[647]: enp0s3: DHCP lease lost
Apr 23 16:08:29 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection.
Apr 23 16:08:33 ubuntu1804-jm kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: Gained carrier
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: DHCPv4 address 10.0.2.15/24 via 10.0.2.2
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: Configured
Apr 23 16:08:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 12:17:03 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
jmihalich@ubuntu1804-jm:~$ journalctl -xe
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent (ssh-agent emulation).
-- – Subject: Unit UNIT has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
-- – Subject: Unit UNIT has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG network certificate management daemon.
-- – Subject: Unit UNIT has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
-- – Subject: Unit UNIT has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache.
-- – Subject: Unit UNIT has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Reached target Shutdown.
-- – Subject: Unit UNIT has finished start-up
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has finished starting up.
-- –
-- The start-up result is RESULT.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Starting Exit the Session...
-- – Subject: Unit UNIT has begun start-up
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit UNIT has begun starting up.
Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Received SIGRTMIN+24 from PID 8881 (kill).
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: us...@0.service: Killing process 8881 (kill) with signal SIGKILL.
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Stopped User Manager for UID 0.
-- – Subject: Unit us...@0.service has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit us...@0.service has finished shutting down.
Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Removed slice User Slice of root.
-- – Subject: Unit user-0.slice has finished shutting down
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit user-0.slice has finished shutting down.
Apr 23 15:55:14 ubuntu1804-jm jenkins[8814]: ...fail!
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Control process exited, code=exited status=7
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Failed with result 'exit-code'.
Apr 23 15:55:14 ubuntu1804-jm systemd[1]: Failed to start LSB: Start @@PRODUCTNAME@@ at boot time.
-- – Subject: Unit jenkins.service has failed
 -- – Defined-By: systemd
 -- – Support: [ http://www.ubuntu.com/support ]
-- –
-- Unit jenkins.service has failed.
-- –
-- The result is RESULT.
Apr 23 15:55:14 ubuntu1804-jm sudo[8782]: pam_unix(sudo:session): session closed for user root
Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection.
Apr 23 15:58:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available
Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Apr 23 16:08:29 ubuntu1804-jm kernel: e1000: enp0s3 NIC Link is Down
Apr 23 16:08:29 ubuntu1804-jm systemd-networkd[647]: enp0s3: Lost carrier
Apr 23 16:08:29 ubuntu1804-jm systemd-networkd[647]: enp0s3: DHCP lease lost
Apr 23 16:08:29 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection.
Apr 23 16:08:33 ubuntu1804-jm kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: Gained carrier
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: DHCPv4 address 10.0.2.15/24 ********* via 10.0.2.2 *****
Apr 23 16:08:33 ubuntu1804-jm systemd-networkd[647]: enp0s3: Configured
Apr 23 16:08:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 12:31:02 PM4/23/19
to jenkinsc...@googlegroups.com

ok, so there is no additional details here. Would you have a /var/log/jenkins/jenkins.log file to share? I'm not sure you should have one..

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 12:42:02 PM4/23/19
to jenkinsc...@googlegroups.com

There's no log file on /var/log/jenkins.

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 12:56:04 PM4/23/19
to jenkinsc...@googlegroups.com

I added a set -x to the jenkins script, here's the output.

 

jmihalich@ubuntu1804-jm:~$ sudo /etc/init.d/jenkins start
+ PATH=/bin:/usr/bin:/sbin:/usr/sbin
+ DESC=@@SUMMARY@@
+ NAME=@@ARTIFACTNAME@@
+ SCRIPTNAME=/etc/init.d/@@ARTIFACTNAME@@
+ '[' -r /etc/default/@@ARTIFACTNAME@@ ']'
+ DAEMON=/usr/bin/daemon
+ DAEMON_ARGS='--name=@@ARTIFACTNAME@@ --inherit --env=JENKINS_HOME= --output= --pidfile='
++ type -p java
+ JAVA=/usr/bin/java
+ '[' -n '' ']'
+ '[' '' = yes ']'
+ SU=/bin/su
+ '[' '!' -x /usr/bin/daemon ']'
+ '[' '' = false ']'
+ '[' -z /usr/bin/java ']'
+ JAVA_ALLOWED_VERSIONS=("18" "110")
++ sed -n ';s/.* version "\(.*\)\.\(.*\)\..*".*/\1\2/p;'
++ /usr/bin/java -version
+ JAVA_VERSION=110
+ [[ 18 110 =~ 110 ]]
+ echo 'Correct java version found'
Correct java version found
+ '[' -r /etc/default/locale ']'
+ . /etc/default/locale
++ LANG=en_US.UTF-8
+ export LANG LANGUAGE
+ . /lib/init/vars.sh
++ TMPTIME=0
++ SULOGIN=no
++ DELAYLOGIN=no
++ UTC=yes
++ VERBOSE=no
++ FSCKFIX=no
++ '[' -f /etc/default/rcS ']'
++ unset EDITMOTD
++ unset RAMRUN
++ unset RAMLOCK
++ '[' -r /proc/cmdline ']'
+++ cat /proc/cmdline
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ '[' '' ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in $(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in $(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)
++ '[' -r /lib/lsb/init-functions.d/40-systemd ']'
++ . /lib/lsb/init-functions.d/40-systemd
+++ _use_systemctl=0
+++ '[' -d /run/systemd/system ']'
+++ prog=jenkins
+++ service=jenkins.service
++++ systemctl -p LoadState --value show jenkins.service
+++ state=loaded
+++ '[' loaded = masked ']'
+++ '[' 10073 -ne 1 ']'
+++ '[' -z '' ']'
+++ case $(readlink -f "$0") in
++++ readlink -f /etc/init.d/jenkins
+++ '[' loaded '!=' not-found ']'
+++ _use_systemctl=1
++++ systemctl -p CanReload --value show jenkins.service
+++ '[' no = no ']'
+++ '[' start = reload ']'
+++ '[' 1 = 1 ']'
+++ set +e
+++ set +u
+++ '[' xstart = xstart -o xstart = xstop -o xstart = xrestart -o xstart = xreload -o xstart = xforce-reload -o xstart = xtry-restart -o xstart = xstatus ']'
+++ systemctl_redirect /etc/init.d/jenkins start
+++ local s
+++ local rc
+++ local prog=jenkins
+++ local command=start
+++ case "$command" in
+++ s='Starting jenkins (via systemctl)'
+++ service=jenkins.service
++++ systemctl is-system-running
+++ OUT=degraded
+++ '[' degraded '!=' degraded ']'
+++ '[' start = status ']'
+++ log_daemon_msg 'Starting jenkins (via systemctl)' jenkins.service
+++ '[' -z 'Starting jenkins (via systemctl)' ']'
+++ log_daemon_msg_pre 'Starting jenkins (via systemctl)' jenkins.service
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z ']'
+++ FANCYTTY=1
+++ case "$FANCYTTY" in
+++ true
+++ echo -n '[....] '
[....] +++ '[' -z jenkins.service ']'
+++ echo -n 'Starting jenkins (via systemctl): jenkins.service'
Starting jenkins (via systemctl): jenkins.service+++ log_daemon_msg_post 'Starting jenkins (via systemctl)' jenkins.service
+++ :
+++ /bin/systemctl --no-pager start jenkins.service
Job for jenkins.service failed because the control process exited with error code.
See "systemctl status jenkins.service" and "journalctl -xe" for details.
+++ rc=1
+++ '[' start = status ']'
+++ log_end_msg 1
+++ '[' -z 1 ']'
+++ local retval
+++ retval=1
+++ log_end_msg_pre 1
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 2
+++ GREEN=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ /usr/bin/tput civis
+++ /usr/bin/tput sc
+++ /usr/bin/tput hpa 0
+++ '[' 1 -eq 0 ']'
+++ '[' 1 -eq 255 ']'
+++ /bin/echo -ne '[FAIL'
[FAIL+++ /usr/bin/tput rc
+++ /usr/bin/tput cnorm
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z 1 ']'
+++ true
+++ case "$FANCYTTY" in
+++ true
++++ /usr/bin/tput setaf 1
+++ RED=''
++++ /usr/bin/tput setaf 3
+++ YELLOW=''
++++ /usr/bin/tput op
+++ NORMAL=''
+++ '[' 1 -eq 0 ']'
+++ '[' 1 -eq 255 ']'
+++ /bin/echo -e ' failed!'
 failed!
+++ log_end_msg_post 1
+++ :
+++ return 1
+++ return 1
+++ exit 1

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 1:09:01 PM4/23/19
to jenkinsc...@googlegroups.com

there's no log file

that's what I feared. Not really a surprise, as the instance never started correctly.

I tested, again, from a newly installation of Ubuntu Server without any default set, installing only openjdk-11-jdk and jenkins latest (2.174 when I write this). It failed with the default /etc/init.d/jenkins but as soon as I changed it for the patched version of the PR, it worked dirrectly.

In my case, installing the jenkins package also installed the daemon package. Is it possible this package is missing in your case?

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:12:02 PM4/23/19
to jenkinsc...@googlegroups.com

oh, is it just 'daemon' ?

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:12:03 PM4/23/19
to jenkinsc...@googlegroups.com

what daemon package are we talking about?  Can you give me the exact deb package name so i can check?

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:15:03 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich updated an issue
Change By: Joe Mihalich
Comment:
what daemon package are we talking about?  Can you give me the exact deb package name so i can check?

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:15:04 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich updated an issue
Change By: Joe Mihalich
Comment:
oh, is it just 'daemon' ?

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:16:02 PM4/23/19
to jenkinsc...@googlegroups.com
 
Re: The latest debian installers 2.164+ do not work with java 11.

Here's a list of all the dependency packages:

 

jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep 'daemon\|adduser\|procps\|psmisc\|net-tools'
ii  acpid                                 1:2.0.28-1ubuntu1                  amd64        Advanced Configuration and Power Interface event daemon
ii  adduser                               3.116ubuntu1                       all          add and remove users and groups
ii  cron                                  3.0pl1-128.1ubuntu1                amd64        process scheduling daemon
ii  daemon                                0.6.4-1build1                      amd64        turns other processes into daemons
ii  dbus                                  1.12.2-1ubuntu1                    amd64        simple interprocess messaging system (daemon and utilities)
ii  dmeventd                              2:1.02.145-4.1ubuntu3              amd64        Linux Kernel Device Mapper event daemon
ii  libprocps6:amd64                      2:3.3.12-3ubuntu1.1                amd64        library for accessing process information from /proc
ii  lxd                                   3.0.3-0ubuntu1~18.04.1             amd64        Container hypervisor based on LXC - daemon
ii  net-tools                             1.60+git20161116.90da8a0-1ubuntu1  amd64        NET-3 networking toolkit
ii  openvpn                               2.4.4-2ubuntu1.1                   amd64        virtual private network daemon
ii  procps                                2:3.3.12-3ubuntu1.1                amd64        /proc file system utilities
ii  psmisc                                23.1-1ubuntu0.1                    amd64        utilities that use the proc file system
ii  rsyslog                               8.32.0-1ubuntu4                    amd64        reliable system and kernel logging daemon
ii  thermald                              1.7.0-5ubuntu2                     amd64        Thermal monitoring and controlling daemon
ii  udev                                  237-3ubuntu10.20                   amd64        /dev/ and hotplug management daemon

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:19:02 PM4/23/19
to jenkinsc...@googlegroups.com

also, i tried this with the stable release 2.164.2 and had the same issue.  I repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails via:

dpkg-deb -R and dpkg-deb -build

and I'm still getting the same issue.

 

Joe

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:19:03 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
also, i tried this with the stable release 2.164.2 and had the same issue.  I repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails .  I did this via:
{code:java}
dpkg-deb -R and dpkg-deb -build{code}

and I'm still getting the same issue.

 

Joe

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:19:04 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
also, i tried this with the stable release 2.164.2 and had the same issue.  I Then i also repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails.  I did this via:

{code:java}
dpkg-deb -R and dpkg-deb -build{code}
and I'm still getting the same issue.

 

Joe

 

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:21:03 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
Here's a list of all the dependency packages:

 
{code:java}

jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep 'daemon\|adduser\|procps\|psmisc\|net-tools'
ii
  acpid                     1:2.0.28-1ubuntu1                  amd64        Advanced Configuration and Power Interface event daemon
ii   adduser                     3.116ubuntu1                     all          add and remove users and groups
ii   cron                     3.0pl1-128.1ubuntu1                amd64        process scheduling daemon
ii  daemon                      0.6.4-1build1                     amd64        turns other processes into daemons
ii   dbus                     1.12.2-1ubuntu1                    amd64        simple interprocess messaging system (daemon and utilities)

ii  dmeventd                     2:1.02.145-4.1ubuntu3              amd64        Linux Kernel Device Mapper event daemon
ii  libprocps6:amd64                     2:3.3.12-3ubuntu1.1                amd64        library for accessing process information from /proc
ii  lxd                     3.0.3-0ubuntu1~18.04.1             amd64        Container hypervisor based on LXC - daemon
ii
  net-tools                     1.60+git20161116.90da8a0-1ubuntu1  amd64        NET-3 networking toolkit
ii   openvpn                     2.4.4-2ubuntu1.1                   amd64        virtual private network daemon
ii   procps                     2:3.3.12-3ubuntu1.1                amd64        /proc file system utilities

ii  psmisc                     23.1-1ubuntu0.1                    amd64        utilities that use the proc file system
ii  rsyslog                     8.32.0-1ubuntu4                    amd64        reliable system and kernel logging daemon
ii  thermald                     1.7.0-5ubuntu2                     amd64        Thermal monitoring and controlling daemon
ii  udev                     237-3ubuntu10.20                   amd64        /dev/ and hotplug management daemon
{code}

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:24:01 PM4/23/19
to jenkinsc...@googlegroups.com

One other piece of info just so we make sure we're in sync...

 

jmihalich@ubuntu1804-jm:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:31:02 PM4/23/19
to jenkinsc...@googlegroups.com

  This is a totally vanilla 18.04 install.  I'm not sure how we're seeing different things happening...

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:31:03 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
One other piece of info just so we make sure we're in sync...

 
{code:java}

jmihalich@ubuntu1804-jm:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep jdk
ii  openjdk-11-jdk:amd64                  11.0.2+9-3ubuntu1~18.04.3          amd64        OpenJDK Development Kit (JDK)
ii  openjdk-11-jdk-headless:amd64         11.0.2+9-3ubuntu1~18.04.3          amd64        OpenJDK Development Kit (JDK) (headless)
ii  openjdk-11-jre:amd64                  11.0.2+9-3ubuntu1~18.04.3          amd64        OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-11-jre-headless:amd64         11.0.2+9-3ubuntu1~18.04.3          amd64        OpenJDK Java runtime, using Hotspot JIT (headless)
 {code}

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:32:02 PM4/23/19
to jenkinsc...@googlegroups.com
Joe Mihalich edited a comment on Bug JENKINS-57096
  This is a totally vanilla 18.04 VirtualBox VM install.  I'm not sure how we're seeing different things happening...

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 23, 2019, 1:40:02 PM4/23/19
to jenkinsc...@googlegroups.com

Joe Mihalich it seems we have the exact same setup, the same versions and all. But I can start Jenkins. What's bothering me is that we don't see why in your case (or I don't know where to look).
I just edited the /etc/init.d/jenkins manually each time, but as we could see, the problem is not in the Java version anymore.

So I guess my patched is fixing the problem but you are facing a new one.

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 1:43:02 PM4/23/19
to jenkinsc...@googlegroups.com

agreed, the java problem seems fixed, but yeah i have no idea what's going on now.

skoh@tensorengr.com (JIRA)

unread,
Apr 23, 2019, 2:05:02 PM4/23/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

Adrien,

I think your commit 063512b6bce8ee4960c95d1ad8985bb2d0b84a36 will fix the init.d/jenkins issue.

I am using  debian package   jenkins 2.174

I will limp along with with the the patch until the commit shows up on our end.  We must have more than a 4 day lag.

Everything else seems to be working for me.

joe@mihalich.net (JIRA)

unread,
Apr 23, 2019, 2:15:02 PM4/23/19
to jenkinsc...@googlegroups.com

Song Koh what OS and version are you using?

skoh@tensorengr.com (JIRA)

unread,
Apr 23, 2019, 2:20:03 PM4/23/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19.1
DISTRIB_CODENAME=tessa
DISTRIB_DESCRIPTION="Linux Mint 19.1 Tessa"

 

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 25, 2019, 4:39:01 AM4/25/19
to jenkinsc...@googlegroups.com

So it happens due to the change in the java -version format. It explains how I missed it in the test. But I confirm that recent JDK vesions return a different format:

 

 

C:\Users\Oleg\Documents\jenkins\demo\demo-jenkins-config-as-code>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
C:\Users\Oleg\Documents\jenkins\demo\demo-jenkins-config-as-code>C:\Tools\jdk-11.0.2\bin\java.exe -version
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)

 

 

Patch from Adrien Lecharpentier in  https://github.com/jenkinsci/packaging/pull/11 should workaround the issue.

 

 

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 25, 2019, 4:40:02 AM4/25/19
to jenkinsc...@googlegroups.com
Oleg Nenashev edited a comment on Bug JENKINS-57096
So it happens due to the change in the java -version format. It explains how I missed it in the test. But I confirm that recent JDK vesions return a different format:

 

 
{noformat}

C:\Users\Oleg\Documents\jenkins\demo\demo-jenkins-config-as-code>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
C:\Users\Oleg\Documents\jenkins\demo\demo-jenkins-config-as-code>C:\Tools\jdk-11.0.2\bin\java.exe -version
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
{noformat}
 

 

Patch from [~alecharp] in    [https://github.com/jenkinsci/packaging/pull/ 11 117 ] should workaround the issue.
{code:java}
 {code}
 

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 25, 2019, 11:57:02 AM4/25/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated Bug JENKINS-57096
 

The target Jenkins release is 2.175, LTS backporting is not clear for packaging. CC Oliver Gondža
Change By: Oleg Nenashev
Status: In Review Fixed but Unreleased
Resolution: Fixed

ogondza@gmail.com (JIRA)

unread,
Apr 26, 2019, 4:18:03 AM4/26/19
to jenkinsc...@googlegroups.com
Oliver Gondža commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

Oleg Nenashev, packaging fixes for current line can be backported to https://github.com/jenkinsci/packaging/tree/stable-2.164. Mind the feature is not covered by the certifications pipeline so will have to be tested manually.

In case you would consider backporting this, note the release is in less than 2 weeks. I would like to have things either omitted or ready to go in that branch by 2019-05-08 for KK to cut the release cleanly (mint it is a public holiday for part of us).

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 29, 2019, 7:21:02 AM4/29/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
 
Change By: Baptiste Mathus
Environment: lilnux linux

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Apr 29, 2019, 7:22:02 AM4/29/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
Change By: Baptiste Mathus
Released As: 2.175

adrien.lecharpentier@gmail.com (JIRA)

unread,
Apr 29, 2019, 7:29:01 AM4/29/19
to jenkinsc...@googlegroups.com
Adrien Lecharpentier commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

Oliver Gondža I'd vote to backport this fix. The LTS package for Debian/Ubuntu is currently broken with Java 11. However, we stated that this LTS is the first one to support Java 11 runtime.

skoh@tensorengr.com (JIRA)

unread,
Apr 29, 2019, 9:23:03 AM4/29/19
to jenkinsc...@googlegroups.com
Song Koh commented on Bug JENKINS-57096

I verify that jenkins-2.175 works with java 11 in "Linux Mint 19.1 Tessa"

 

$ dpkg --list jenkins*
Desired=Unknown/Install/Remove/Purge/Hold

Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
/ Name Version Architecture Description
+++=======================================================================
ii jenkins 2.175 all Jenkins is an open source automat

$ java -version
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)

 

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 29, 2019, 9:24:02 AM4/29/19
to jenkinsc...@googlegroups.com
 

Thanks for the update!
Change By: Oleg Nenashev
Status: Fixed but Unreleased Resolved

joe@mihalich.net (JIRA)

unread,
Apr 29, 2019, 12:47:02 PM4/29/19
to jenkinsc...@googlegroups.com
Joe Mihalich commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

Not sure what changed, but it is now working with Ubuntu 18.04 and openjdk 11.  Thanks for getting this working.

 

ogondza@gmail.com (JIRA)

unread,
May 7, 2019, 8:16:02 AM5/7/19
to jenkinsc...@googlegroups.com
Oliver Gondža updated an issue
 
Change By: Oliver Gondža
Labels: 2.164.3-fixed java11 java11-compatibility jenkins triaged

ogondza@gmail.com (JIRA)

unread,
May 7, 2019, 8:19:02 AM5/7/19
to jenkinsc...@googlegroups.com
Oliver Gondža commented on Bug JENKINS-57096
 
Re: The latest debian installers 2.164+ do not work with java 11.

I have backported this to be picked up by 2.164.3 during tomorrows release.

judd@engineer.com (JIRA)

unread,
May 8, 2019, 5:30:02 PM5/8/19
to jenkinsc...@googlegroups.com

I am wanting to use Amazon Corretto JDK 11 on Ubuntu and want to try out 2.164.3.  Is it going to be released today?
Reply all
Reply to author
Forward
0 new messages