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

Cannot upgrade Debian package when not set to start on boot

    XMLWordPrintable

Details

    Description

      Trying to upgrade Jenkins, which has been installed on Ubuntu as a deb package from pkg.jenkins.io, results in the following error if Jenkins has been set to to not run standalone in /etc/default/jenkins:
       

      Setting up jenkins (2.164.3) ...
      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; bad; vendor preset: enabled)
         Active: failed (Result: exit-code) since Sun 2019-05-12 15:00:08 CEST; 37ms ago
           Docs: man:systemd-sysv-generator(8)
        Process: 22350 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)
      
      May 12 15:00:08 server07.pepsoft.org systemd[1]: Starting LSB: Start Jenkins at boot time...
      May 12 15:00:08 server07.pepsoft.org jenkins[22350]: Not configured to run standalone
      May 12 15:00:08 server07.pepsoft.org systemd[1]: jenkins.service: Control process exited, code=exited status=1
      May 12 15:00:08 server07.pepsoft.org systemd[1]: Failed to start LSB: Start Jenkins at boot time.
      May 12 15:00:08 server07.pepsoft.org systemd[1]: jenkins.service: Unit entered failed state.
      May 12 15:00:08 server07.pepsoft.org systemd[1]: jenkins.service: Failed with result 'exit-code'.
      dpkg: error processing package jenkins (--configure):
       subprocess installed post-installation script returned error exit status 1
      Errors were encountered while processing:
       jenkins
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      

      /etc/default/jenkins contains the following lines:

      # set this to false if you don't want Jenkins to run by itself
      # in this set up, you are expected to provide a servlet container
      # to host jenkins.
      RUN_STANDALONE=false
      #RUN_STANDALONE=true
      

      This is because I have configured my pre-existing Tomcat container to run Jenkins because I don't want a separate Java process to take up the limited resources of my VPS.

      If I change the setting to true, the upgrade does succeed.

      It seems that the upgrade script should take that setting into account, and/or check whether the service is running to begin with, before trying to stop and start it.

      Attachments

        Issue Links

          Activity

            basil Basil Crow added a comment -

            Duplicates JENKINS-54558.

            basil Basil Crow added a comment - Duplicates JENKINS-54558 .
            basil Basil Crow added a comment -

            As of 2.335, Jenkins has moved to systemd, and the RUN_STANDALONE option has not been ported from System V init to systemd. If for some reason you don't want the service to start automatically, run systemctl disable jenkins to mask the systemd service unit.

            basil Basil Crow added a comment - As of 2.335, Jenkins has moved to systemd , and the RUN_STANDALONE option has not been ported from System V init to systemd . If for some reason you don't want the service to start automatically, run systemctl disable jenkins to mask the systemd service unit.

            People

              kohsuke Kohsuke Kawaguchi
              captain_chaos Pepijn Schmitz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: