[JIRA] (JENKINS-37999) Debian Jessie package produce error on installation, Jenkins fails to start
Title: Message Title Michael Weghorn commented on JENKINS-37999 Re: Debian Jessie package produce error on installation, Jenkins fails to start I found this Debian bug report about circular Java dependencies which seems to describe the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774873 So this bug most probably a bug in the Debian Java packages contained in Debian jessie, not a bug in the Jenkins Debian package. Workaround from a user/administrator point of view: install the package "default-jre-headless" first, then install Jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37999) Debian Jessie package produce error on installation, Jenkins fails to start
Title: Message Title Michael Weghorn commented on JENKINS-37999 Re: Debian Jessie package produce error on installation, Jenkins fails to start Note: The change I made for the workaround can currently be seen in the branch "jenkins-37999" of my GitHub fork of the packaging git repository: https://github.com/michaelweghorn/packaging/tree/jenkins-37999 (Note: This fork will probably be deleted at some point in the future.) I did not create a pull request as I am not sure the underlying problem is actually one in Jenkins. In case you should want to integrate that into Jenkins, please feel free to do so and let me know in case something is necessary from my side (create a pull request on GitHub...). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37999) Debian Jessie package produce error on installation, Jenkins fails to start
Title: Message Title Michael Weghorn commented on JENKINS-37999 Re: Debian Jessie package produce error on installation, Jenkins fails to start I still experience the same problem with version 2.25 of the jenkins package in Debian jessie. I have further analysed the problem. The installation works fine if the Debian package "default-jre-headless" is already installed before the installation of the "jenkins" package via apt is started. The problem here seems to be that Jenkins needs Java to be fully set up when Jenkins is set up (in the postinst script in the "jenkins" Debian package). As can be seen from the error description above, the package "openjdk-7-jre-headless" is set up after the setup of jenkins. Therefore, the jenkins setup fails. (It works totally fine when trying it again after this failed setup, because openjdk-7-jre-headless and default-jre-headless are then correctly set up.) The jenkins package defines "default-jre-headless" as a dependency in its control file. "default-jre-headless" itself depends on "openjdk-7-jre-headless". From my understanding of the "Depends" field (as defined in the Debian Policy Manual, https://www.debian.org/doc/debian-policy/ch-relationships.html), those Java packages should normally be configured before Jenkins is. For some reason, this is not the case here. It might be due to some cyclic dependency in the underlying packages that jenkins depends on (or for some other reason I can currently not think of...). I can no longer reproduce the bug with the current development version of Debian (unstable/sid). The problem also does no more appear when using "Pre-Depends: default-jre-headless (>= 2:1.7) | java7-runtime-headless" instead of the normal "Depends" in Jenkins's control file. (As I mentioned before, I would expect that "Depends" should normally suffice, but it apparently does not in Debian jessie.) I do not feel able to say with certainty whether the bug is actually one in the Debian packaging of Jenkins or of the underlying Java packages. The mentioned workaround (using "Pre-Depends" in the control file of Jenkins's packaging) did work for myself. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37999) Debian Jessie package produce error on installation, Jenkins fails to start
Title: Message Title JEK NIS created an issue Jenkins / JENKINS-37999 Debian Jessie package produce error on installation, Jenkins fails to start Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2016/Sep/06 10:05 PM Priority: Critical Reporter: JEK NIS Following the installation instructions for debian packages found here: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu is not successful. The installation process fails with this error: Setting up default-jre-headless (2:1.7-52) ... Setting up jenkins (2.7.3) ... Job for jenkins.service failed. See 'systemctl status jenkins.service' and 'journalctl -xn' for details. invoke-rc.d: initscript jenkins, action "start" failed. dpkg: error processing package jenkins (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ca-certificates (20141019+deb8u1) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d done. done. Setting up openjdk-7-jre-headless:amd64 (7u111-2.6.7-1~deb8u1) ... update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java to provide /usr/bin/java (java) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto
