Chisel added a comment - 2021-08-13 11:05 We experienced the same thing this morning during our weekly maintenance for Jenkins. We took a punt and tried manually installing the `daemonize` package but the service didn't appear to even attempt to start (looking at /var/log/jenkins/*).   curl -LO 'https: //rpmfind.net/linux/epel/7/x86_64/Packages/d/daemonize-1.7.7-1.el7.x86_64.rpm' sudo rpm -Uvh ./daemonize-1.7.7-1.el7.x86_64.rpm

Mark Waite added a comment - 2021-08-13 12:42 The dependency is expressed in the rpm file, but the dependency is satisfied with the daemonize program from the `epel-release` repository. The installation instructions on www.jenkins.io have been updated to guide the user to enable the epel-release repository. When I enabled the epel-release repository and performed the install, the service started.

Chisel added a comment - 2021-08-13 13:07 - edited Any suggestions for AmazonLinux? # sudo wget -O /etc/yum.repos.d/jenkins.repo \ > https: //pkg.jenkins.io/redhat-stable/jenkins.repo --2021-08-13 13:04:07-- https: //pkg.jenkins.io/redhat-stable/jenkins.repo Resolving pkg.jenkins.io (pkg.jenkins.io)... 199.232.26.133, 2a04:4e42:43::645 Connecting to pkg.jenkins.io (pkg.jenkins.io)|199.232.26.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 85 Saving to: ‘/etc/yum.repos.d/jenkins.repo’ /etc/yum.repos.d/jenkins.repo 100%[=============================================================================================>] 85 --.-KB/s in 0s 2021-08-13 13:04:08 (4.21 MB/s) - ‘/etc/yum.repos.d/jenkins.repo’ saved [85/85] # sudo rpm -- import https: //pkg.jenkins.io/redhat-stable/jenkins.io.key # sudo yum upgrade Loaded plugins: priorities, update-motd, upgrade-helper amzn-main | 2.1 kB 00:00:00 amzn-updates | 3.8 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package jenkins.noarch 0:2.305-1.1 will be updated ---> Package jenkins.noarch 0:2.306-1.1 will be an update --> Processing Dependency: daemonize for package : jenkins-2.306-1.1.noarch --> Finished Dependency Resolution Error: Package: jenkins-2.306-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 [root@ip-10-2-10-8 ~]# sudo yum update Loaded plugins: priorities, update-motd, upgrade-helper Resolving Dependencies --> Running transaction check ---> Package jenkins.noarch 0:2.305-1.1 will be updated ---> Package jenkins.noarch 0:2.306-1.1 will be an update --> Processing Dependency: daemonize for package : jenkins-2.306-1.1.noarch --> Finished Dependency Resolution Error: Package: jenkins-2.306-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 # sudo yum install epel-release java-11-openjdk-devel Loaded plugins: priorities, update-motd, upgrade-helper Package epel-release-6-8.9.amzn1.noarch already installed and latest version No package java-11-openjdk-devel available. Nothing to do  

Mark Waite added a comment - 2021-08-13 13:10 I believe I used the Red Hat / CentOS instructions with Amazon Linux 2 yesterday while testing, but I don't have an Amazon Linux 1 instance. I'll need to double check to be sure. Maybe the directions at https://aws.amazon.com/premiumsupport/knowledge-center/ec2-enable-epel/ will help?

Robert Golden added a comment - 2021-08-13 14:15 Thanks all for your help! I was able to satisfy the daemonize dependency by enabling the EPEL repo on Amazon Linux. amazon-linux-extras install epel -y yum update -y