Discussion on how to use Jenkins and Jenkins plugins here.
1 Like
Hi there, i a newbie to the community. when ever i run the command
sudo service jenkins start
Starting jenkins (via systemctl): Job for jenkins.service failed. See “systemctl status jenkins.service” and “journalctl -xe” for details.
[FAILED]
jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sun 2022-07-17 12:32:39 UTC; 20s ago
Process: 4831 ExecStart=/usr/bin/jenkins (code=exited, status=0/SUCCESS)
Main PID: 4831 (code=exited, status=0/SUCCESS)
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: Failed to start Jenkins Continuous Integration Server.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: Unit jenkins.service entered failed state.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: jenkins.service failed.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: jenkins.service holdoff time over, scheduling restart.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: Stopped Jenkins Continuous Integration Server.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: start request repeated too quickly for jenkins.service
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: Failed to start Jenkins Continuous Integration Server.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: Unit jenkins.service entered failed state.
Jul 17 12:32:39 ip-172-31-2-212.ap-south-1.compute.internal systemd[1]: jenkins.service failed.
Check all jenkins related logs like console.log
Run that journalctl -xe command and see what it says.
Check what port is jenkins configured to open and if something is already running on that port - netstat -tulpn