-->

Tuesday, September 7, 2021

[Solved] Error: Package: jenkins-2.303.1-1.1.noarch (jenkins) Requires: daemonize --skip-broken to work

Issue:- 

The issue occurs when trying to install the jenkins on the Centos7 EC2 Instance in the AWS.

 # yum install jenkins -y


Error:- 

 --> Finished Dependency Resolution  
 Error: Package: jenkins-2.303.1-1.1.noarch (jenkins)  
       Requires: daemonize  
  You could try using --skip-broken to work around the problem  
  You could try running: rpm -Va --nofiles --nodigest


Cause:-

Basically daemonize runs a command as a Daemon in the Centos. Since the package is missing in the version of the Centos you running thats why this error is coming. Think of it like a dependency which is required by the Jenkins to run but since you missing on the Daemonize thats why its giving the error.


Resolution:-

Daemonize doesn't ship in the default repository thats why yum is not able to resolve it. You will need to install the Daemonize from the Epel repository which is the extra package for enterprise linux as

 # yum install epel-release -y  
 # yum install daemonize -y  
 Than you can continue on installing the Jenkins as  
 # yum install jenkins -y



Posted by at 9/07/2021 10:47:00 PM
Labels: ,

29 comments:

  1. UnknownSeptember 18, 2021 at 8:52 PM

    Thanks your resolution steps

    ReplyDelete
  2. Paresh MaratheSeptember 28, 2021 at 4:25 PM

    Thanks for the resolution steps. It works..

    ReplyDelete
  3. UnknownOctober 7, 2021 at 10:40 PM

    Thanks your resolution steps

    ReplyDelete
  4. UnknownOctober 17, 2021 at 4:30 PM

    Its still not working

    ReplyDelete
    Replies
    1. Ankit MittalOctober 17, 2021 at 10:58 PM

      This works have tried this many times ? Can you share the error that you facing ? Before and after implementing the solution ?

      Delete
    2. UnknownOctober 17, 2021 at 11:08 PM

      Error: Package: jenkins-2.303.2-1.1.noarch (jenkins)
      Requires: daemonize
      You could try using --skip-broken to work around the problem
      You could try running: rpm -Va --nofiles --nodigest

      after doing those steps still getting same errors

      Delete
    3. Ankit MittalOctober 18, 2021 at 7:37 AM

      Can you share the output of

      # yum list installed daemonize

      Delete
    4. UnknownOctober 18, 2021 at 10:51 AM

      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      Error: No matching Packages to list

      Delete
    5. UnknownOctober 19, 2021 at 1:45 AM

      I am also getting same issue.

      sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key
      $ sudo yum install jenkins
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      amzn2-core | 3.7 kB 00:00:00
      Resolving Dependencies
      --> Running transaction check
      ---> Package jenkins.noarch 0:2.303.2-1.1 will be installed
      --> Processing Dependency: daemonize for package: jenkins-2.303.2-1.1.noarch
      --> Finished Dependency Resolution
      Error: Package: jenkins-2.303.2-1.1.noarch (jenkins)
      Requires: daemonize
      You could try using --skip-broken to work around the problem
      You could try running: rpm -Va --nofiles --nodigest
      $ yum list installed daemonize
      Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
      Error: No matching Packages to list
      $

      Delete
    6. Ankit MittalOctober 20, 2021 at 11:03 PM

      So Daemonize package is not installed please run following commands

      yum install epel-release -y
      yum install daemonize -y
      yum install jenkins -y

      After this the daemonize should be installed and jenkins should be installed just fine.
      You can verify by running

      yum list installed daemonize

      Delete
    7. Max WeberNovember 17, 2021 at 1:28 AM

      These cmds also did not work

      Delete
    8. Ankit MittalNovember 18, 2021 at 12:38 PM

      Please share execution of the cmds and output after execution along with error details.

      Delete
    9. UnknownNovember 28, 2021 at 4:47 PM

      if you are using AWS instance then use this steps,
      # amazon-liux-extrass install epel
      # yum install daemonize -y
      # yum install jenkins

      Delete
    10. UnknownDecember 1, 2021 at 7:31 PM

      Step1. Create the YumRepo File.

      vim /etc/yum.repos.d/epelfordaemonize.repo

      [daemonize]
      baseurl=https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/
      gpgcheck=no
      enabled=yes
      Step2. yum install daemonize -y

      Step3. yum install jenkins -y

      Delete
    11. UnknownFebruary 23, 2022 at 11:54 PM

      Try this command " sudo amazon-linux-extras install epel " , then execute yum install daemonize -y
      It worked for me.

      Delete
    12. AnonymousFebruary 24, 2022 at 12:03 PM

      tq dude

      Delete
    13. DevjeetMarch 4, 2022 at 12:00 PM

      It worked thanks a lot. Cheers.

      Delete
  5. AnonymousOctober 21, 2021 at 5:01 PM

    thank you bro it is working!!

    ReplyDelete
  6. UnknownNovember 1, 2021 at 1:54 PM

    [root@ip-172-31-1-166 opt]# yum install jenkins -y
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:19:14 ago on Mon 01 Nov 2021 08:01:44 AM UTC.
    Error:
    Problem: cannot install the best candidate for the job
    - nothing provides daemonize needed by jenkins-2.303.2-1.1.noarch
    (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
    [root@ip-172-31-1-166 opt]# yum install daemonize -y
    Updating Subscription Management repositories.
    Last metadata expiration check: 0:19:44 ago on Mon 01 Nov 2021 08:01:44 AM UTC.
    No match for argument: daemonize
    Error: Unable to find a match: daemonize
    can anybody help what is this error? and how i am going to clear this error.

    ReplyDelete
    Replies
    1. UnknownNovember 30, 2021 at 1:23 PM

      for the below errors pls find the solution its 100% working

      Error: Problem: cannot install the best candidate for the job - nothing provides daemonize needed by jenkins-2.303.3-1.1.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

      Solutions:
      link - https://lanedirt.tech/2021/11/install-daemonize-on-rhel-8-centos-8-almalinux-8/
      Commands:
      1.sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
      2.sudo dnf repolist
      3.sudo dnf install daemonize
      4.sudo yum install jenkins
      5.sudo systemctl start jenkins
      6.systemctl status jenkins

      Delete
  7. warisNovember 24, 2021 at 6:17 AM

    you will need to have that repo to run epel/demonize, make a repo of it and then install jenkins like below

    Step1. Create the YumRepo File.

    vim /etc/yum.repos.d/epelfordaemonize.repo

    [daemonize]
    baseurl=https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/
    gpgcheck=no
    enabled=yes
    Step2. yum install daemonize -y

    Step3. yum install jenkins java-1.8.0-openjdk-devel -y

    ReplyDelete
  8. UnknownNovember 30, 2021 at 1:21 PM

    for the below errors pls find the solution its 100% working

    Error: Problem: cannot install the best candidate for the job - nothing provides daemonize needed by jenkins-2.303.3-1.1.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

    Solutions:
    link - https://lanedirt.tech/2021/11/install-daemonize-on-rhel-8-centos-8-almalinux-8/
    Commands:
    1.sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
    2.sudo dnf repolist
    3.sudo dnf install daemonize
    4.sudo yum install jenkins
    5.sudo systemctl start jenkins
    6.systemctl status jenkins

    ReplyDelete
  9. UnknownDecember 1, 2021 at 6:27 PM

    thanks bro it worked

    ReplyDelete
  10. Emeris L.January 28, 2022 at 5:15 PM

    After I installed epel-release and daemonize, I was able to install Jenkins successfully but it is not running actively, it is showing active (exited). Please how do I resolve that?

    ReplyDelete
  11. UnknownFebruary 8, 2022 at 12:54 PM

    I am also getting the same error tried a lot but no luck.

    ReplyDelete

Subscribe to: Post Comments (Atom)