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

ERROR trying to upgrade jenkins to 2.303.1 yields message: daemonize is needed

      hi,

       

      i'm trying to upgrade jenkins using the redhat package from:

      http://mirrors.jenkins-ci.org/redhat-stable/jenkins-2.303.1-1.1.noarch.rpm

       

      the following set of commands yields an installation error:

      ================================

      -bash-4.2$ sudo rpm -Uvh jenkins-2.303.1-1.1.noarch.rpm
      warning: jenkins-2.303.1-1.1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEY
      error: Failed dependencies:
      daemonize is needed by jenkins-2.303.1-1.1.noarch

      ================================

       

      for the past couple of years (at least 5 years) I was able to do so.

      did something change in this rpm?

      P.S. I installed openjdk11 a week ago - the jenkins controller is working properly.

          [JENKINS-66490] ERROR trying to upgrade jenkins to 2.303.1 yields message: daemonize is needed

          Mark Waite added a comment - - edited

          Refer to the installation instructions at https://www.jenkins.io/doc/book/installing/linux/#red-hat-centos for the current install instructions. The Jenkins rpm package now requires the daemonize package that is available from the epel-release repository.

          Thanks for detecting that we didn't include that change in the Jenkins 2.303.1 upgrade guide. It needs to be included there, in addition to the inclusion in the installation instructions.

          Mark Waite added a comment - - edited Refer to the installation instructions at https://www.jenkins.io/doc/book/installing/linux/#red-hat-centos for the current install instructions. The Jenkins rpm package now requires the daemonize package that is available from the epel-release repository. Thanks for detecting that we didn't include that change in the Jenkins 2.303.1 upgrade guide. It needs to be included there, in addition to the inclusion in the installation instructions.

          Amit Dar added a comment -

          thanks markewaite!

          since I'm installing it on an air-gapped centos 6 server, can you please make sure the instructions contain exactly what is needed - package wise?

          also - is there any additional configuration which needs to be done prior to the upgrade itself.

          thanks.

          Amit Dar added a comment - thanks markewaite ! since I'm installing it on an air-gapped centos 6 server, can you please make sure the instructions contain exactly what is needed - package wise? also - is there any additional configuration which needs to be done prior to the upgrade itself. thanks.

          Mark Waite added a comment -

          amidar I'm sorry, but I don't test CentOS 6 and don't intend to document or test for CentOS 6. CentOS 6 end of life was November 2020.

          The command line git version included in CentOS 6 has several use cases that do not work with the Jenkins git plugin. CentOS 6 does not receive maintenance updates.

          Mark Waite added a comment - amidar I'm sorry, but I don't test CentOS 6 and don't intend to document or test for CentOS 6. CentOS 6 end of life was November 2020. The command line git version included in CentOS 6 has several use cases that do not work with the Jenkins git plugin. CentOS 6 does not receive maintenance updates.

          Amit Dar added a comment -

          markewaite fair enough.

           

          how about CentOS 7? 

          I guess the time for server upgrade has come... still I need to know how to treat this air gapped environment... (up until now the jenkins rpm was all I needed...)

          Amit Dar added a comment - markewaite  fair enough.   how about CentOS 7?  I guess the time for server upgrade has come... still I need to know how to treat this air gapped environment... (up until now the jenkins rpm was all I needed...)

          Mark Waite added a comment -

          amidar The existing instructions work for CentOS 7 with an internet connection. You'll need to explore for yourself to see what is required in your air-gapped environment.

          Mark Waite added a comment - amidar The existing instructions work for CentOS 7 with an internet connection. You'll need to explore for yourself to see what is required in your air-gapped environment.

          Stephan Watermeyer added a comment - - edited

          Same problem here on one of our old Jenkins Boxes with CentOS 6 (which we still have in place for some legacy applications).

          So far i only installed daemonize manually

          wget https://github.com/bmc/daemonize/archive/refs/heads/master.zip
          unzip master.zip
          cd daemonize-master/
          configure
          make
          make install
          

          But havent solved it yet...

          [root@swpsci01 tmp]# rpm -U jenkins-latest.rpm
          warning: jenkins-latest.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEY
          error: Failed dependencies:
                  daemonize is needed by jenkins-2.303.1-1.1.noarch
          [root@swpsci01 tmp]# daemonize
          daemonize, version 1.7.8
          
          

          Stephan Watermeyer added a comment - - edited Same problem here on one of our old Jenkins Boxes with CentOS 6 (which we still have in place for some legacy applications). So far i only installed daemonize manually http://software.clapper.org/daemonize/ wget https: //github.com/bmc/daemonize/archive/refs/heads/master.zip unzip master.zip cd daemonize-master/ configure make make install But havent solved it yet... [root@swpsci01 tmp]# rpm -U jenkins-latest.rpm warning: jenkins-latest.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEY error: Failed dependencies: daemonize is needed by jenkins-2.303.1-1.1.noarch [root@swpsci01 tmp]# daemonize daemonize, version 1.7.8

          Mark Waite added a comment -

          phreakadelle the dependency in the rpm file can only be satisfied with an rpm package for daemonize. Installing from source won't do it because the RPM package manager won't realize that the dependency is satisfied. You might try enabling the epel-release repository (if they still support CentOS 6) and then installing.

          Mark Waite added a comment - phreakadelle the dependency in the rpm file can only be satisfied with an rpm package for daemonize. Installing from source won't do it because the RPM package manager won't realize that the dependency is satisfied. You might try enabling the epel-release repository (if they still support CentOS 6) and then installing.

          Amit Dar added a comment - - edited

          I eventually updated the air gapped Jenkins server on our site. it has centos 6.4 and I used the following packages:

          https://fedora-archive.ip-connect.info/epel/6/x86_64/epel-release-6-8.noarch.rpm

          https://fedora-archive.ip-connect.info/epel/6/x86_64/Packages/d/daemonize-1.7.3-1.el6.x86_64.rpm

           

          Amit Dar added a comment - - edited I eventually updated the air gapped Jenkins server on our site. it has centos 6.4 and I used the following packages: https://fedora-archive.ip-connect.info/epel/6/x86_64/epel-release-6-8.noarch.rpm https://fedora-archive.ip-connect.info/epel/6/x86_64/Packages/d/daemonize-1.7.3-1.el6.x86_64.rpm  

          Mark Waite added a comment -

          Fixed by updating the documentation to mention the change in RPM package definition

          Mark Waite added a comment - Fixed by updating the documentation to mention the change in RPM package definition

            markewaite Mark Waite
            amidar Amit Dar
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: