[GH-ISSUE #238] jenkins installation issue on linux ec2 #68

Closed
opened 2026-03-03 13:58:53 +03:00 by kerem · 4 comments
Owner

Originally created by @azharism on GitHub (Feb 11, 2023).
Original GitHub issue: https://github.com/konstruktoid/hardening/issues/238

Originally assigned to: @konstruktoid on GitHub.

Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details.

jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sat 2023-02-11 20:34:49 UTC; 10s ago
Process: 25165 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE)
Main PID: 25165 (code=exited, status=1/FAILURE)

jenkins.service: main process exited, code=exited, status=1/FAILURE
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Failed to start Jenkins Continuous Integration Server.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Unit jenkins.service entered failed state.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service failed.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service holdoff time over, scheduling restart.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Stopped Jenkins Continuous Integration Server.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: start request repeated too quickly for jenkins.service
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Failed to start Jenkins Continuous Integration Server.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Unit jenkins.service entered failed state.
Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service failed.

please help sir to find the solution

Originally created by @azharism on GitHub (Feb 11, 2023). Original GitHub issue: https://github.com/konstruktoid/hardening/issues/238 Originally assigned to: @konstruktoid on GitHub. Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. jenkins.service - Jenkins Continuous Integration Server Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sat 2023-02-11 20:34:49 UTC; 10s ago Process: 25165 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE) Main PID: 25165 (code=exited, status=1/FAILURE) jenkins.service: main process exited, code=exited, status=1/FAILURE Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Failed to start Jenkins Continuous Integration Server. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Unit jenkins.service entered failed state. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service failed. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service holdoff time over, scheduling restart. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Stopped Jenkins Continuous Integration Server. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: start request repeated too quickly for jenkins.service Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Failed to start Jenkins Continuous Integration Server. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: Unit jenkins.service entered failed state. Feb 11 20:34:49 ip-172-31-57-17.ec2.internal systemd[1]: jenkins.service failed. please help sir to find the solution
kerem closed this issue 2026-03-03 13:58:53 +03:00
Author
Owner

@konstruktoid commented on GitHub (Feb 11, 2023):

How is this issue related to this repository?

<!-- gh-comment-id:1426876803 --> @konstruktoid commented on GitHub (Feb 11, 2023): How is this issue related to this repository?
Author
Owner

@azharism commented on GitHub (Feb 11, 2023):

i am installing jenkinns on ec2 linux machine and facing this isuue

<!-- gh-comment-id:1426877894 --> @azharism commented on GitHub (Feb 11, 2023): i am installing jenkinns on ec2 linux machine and facing this isuue
Author
Owner

@azharism commented on GitHub (Feb 11, 2023):

sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo
sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key
amazon-linux-extras install epel
amazon-linux-extras install java-openjdk11

using the above command facing issue kindly help to fix it

<!-- gh-comment-id:1426878229 --> @azharism commented on GitHub (Feb 11, 2023): sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key amazon-linux-extras install epel amazon-linux-extras install java-openjdk11 using the above command facing issue kindly help to fix it
Author
Owner

@konstruktoid commented on GitHub (Feb 11, 2023):

Sorry, this hasn't got anything to do with this repository.

<!-- gh-comment-id:1426878850 --> @konstruktoid commented on GitHub (Feb 11, 2023): Sorry, this hasn't got anything to do with this repository.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hardening#68
No description provided.