Newly installed Jenkins 2.387 with java-11, jenkins service failed to start

hollychen · May 12, 2023, 10:19pm

need help: environment Redhat 8

Installed java-11-openjdk-11.0.19.0.7-1.el7_9.x86_64 with “sudo yum install fontconfig java-11-openjdk”;
Installed jenkins 2.387.3-1.1, set up JAVA_HOME,3. failed to start,
no log found.
error mesage as:
:/usr/lib/jenkins>sudo systemctl enable jenkins
Created symlink from /etc/systemd/system/multi-user.target.wants/jenkins.service to /usr/lib/systemd/system/jenkins.service.
/home/oraamp>sudo service jenkins start
Starting jenkins (via systemctl): Job for jenkins.service failed because the control process exited with error code. See “systemctl status jenkins.service” and “journalctl -xe” for details.

Thanks, in advance.

Holly

slide_o_mix · May 12, 2023, 10:25pm

You’ll want to run one of the two commands mentioned in the error message to see the logs. The last line of the error message shows the two commands.

hollychen · May 12, 2023, 10:49pm

Thank you for the reply.
when check error message:
:/var/log>systemctl status jenkins.service
● jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Fri 2023-05-12 14:26:07 PDT; 1h 21min ago
Process: 19077 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE)
Main PID: 19077 (code=exited, status=1/FAILURE)

May 12 14:26:06 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 12 14:26:06 mcdasatest07 systemd[1]: Failed to start Jenkins Continuous Integration Server.
May 12 14:26:06 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 12 14:26:06 mcdasatest07 systemd[1]: jenkins.service failed.
May 12 14:26:07 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 12 14:26:07 mcdasatest07 systemd[1]: Stopped Jenkins Continuous Integration Server.
May 12 14:26:07 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 12 14:26:07 mcdasatest07 systemd[1]: Failed to start Jenkins Continuous Integration Server.
May 12 14:26:07 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 12 14:26:07 mcdasatest07 systemd[1]: jenkins.service failed.

when run: journalctl -xe
Unit redcloak.service has begun starting up.
May 12 15:41:17 mcdasatest07 systemd[1]: redcloak.service: control process exited, code=exited status=127
May 12 15:41:17 mcdasatest07 sh[16705]: /bin/sh: /opt/secureworks/redcloak/bin/redcloak_start.sh: No such file or directory
May 12 15:41:17 mcdasatest07 systemd[1]: Failed to start Redcloak Security monitoring service.
– Subject: Unit redcloak.service has failed

hollychen · May 12, 2023, 10:50pm

checked, there is no content under /opt/secureworks/redcloak/

hollychen · May 12, 2023, 10:53pm

My installation command followed:

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-2023.key
sudo yum install fontconfig java-11-openjdk.
sudo yum install jenkins

Thank you.

Holly

hollychen · May 12, 2023, 10:56pm

Is this log location?
:/var/log>cd jenkins
:/var/log/jenkins>ls -ltr
total 0

slide_o_mix · May 12, 2023, 11:58pm

Can you try the journalctl command and add -u jenkins?

hollychen · May 13, 2023, 12:13am

journalctl -u jenkins
– Logs begin at Sat 2023-04-08 07:03:02 PDT, end at Fri 2023-05-12 17:11:44 PDT. –
May 03 16:04:48 mcdasatest07 systemd[1]: Starting Jenkins Continuous Integration Server…
May 03 16:04:48 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 03 16:04:48 mcdasatest07 systemd[1]: Failed to start Jenkins Continuous Integration Server.
May 03 16:04:48 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 03 16:04:48 mcdasatest07 systemd[1]: jenkins.service failed.
May 03 16:04:49 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 03 16:04:49 mcdasatest07 systemd[1]: Stopped Jenkins Continuous Integration Server.

slide_o_mix · May 13, 2023, 1:12am

Hmmm, that didn’t help much at all. Do you have another Java installed on the machine already that might be set as the default? Can you look at the overrides file using the commands detailed here (Managing systemd services) to see if the path to Java is being overridden to a Java 8 install?

halkeye · May 13, 2023, 2:00pm

How did you setup JAVA_HOME? I don’t think systems reads from anywhere but the systemd service files.

hollychen · May 16, 2023, 6:52pm

Thanks slide_o_mix and halkeye.
Went through the document, didn’t see override.conf file is stored at /etc/systemd/system/jenkins.service.d/override.conf, but found /etc/systemd/system/jenkins.service.
Can I edit and add changes to jenkins.service?

[Unit]
Description=My Company Jenkins Controller

[Service]
# Add JVM configuration options
Environment="JAVA_OPTS=-Djava.awt.headless=true -XX:+UseStringDeduplication"

# Arbitrary additional arguments to pass to Jenkins.
# Full option list: java -jar jenkins.war --help
Environment="JENKINS_OPTS=--prefix=/jenkins --JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.19.0.7-1.el7_9.x86_64"

# Configuration as code directory
Environment="CASC_JENKINS_CONFIG=/var/lib/jenkins/configuration-as-code/"

In my case, JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.19.0.7-1.el7_9.x86_64

mcdasatest07:/home/oraamp>java -version
openjdk version "11.0.19" 2023-04-18 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.19.0.7-1.el7_9) (build 11.0.19+7-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.19.0.7-1.el7_9) (build 11.0.19+7-LTS, mixed mode, sharing)

hollychen · May 16, 2023, 8:19pm

Made change in jenkins.service, same fail:
:/usr/lib/systemd/system>sudo service jenkins start
Starting jenkins (via systemctl): Job for jenkins.service failed because the control process exited with error code. See “systemctl status jenkins.service” and “journalctl -xe” for details.
[FAILED]
:/usr/lib/systemd/system>systemctl status jenkins.service
● jenkins.service - My Company Jenkins Controller
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2023-05-16 13:12:06 PDT; 16s ago
Process: 27540 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE)
Main PID: 27540 (code=exited, status=1/FAILURE)

May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service failed.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 16 13:12:06 mcdasatest07 systemd[1]: Stopped My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service failed.

hollychen · May 16, 2023, 8:19pm

:/usr/lib/systemd/system>journalctl -xe
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 16 13:12:05 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
– Subject: Unit jenkins.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit jenkins.service has failed.

– The result is failed.
May 16 13:12:05 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service failed.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 16 13:12:06 mcdasatest07 systemd[1]: Stopped My Company Jenkins Controller.
– Subject: Unit jenkins.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit jenkins.service has finished shutting down.

hollychen · May 16, 2023, 8:21pm

May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
– Subject: Unit jenkins.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit jenkins.service has failed.

– The result is failed.
May 16 13:12:06 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service failed.
May 16 13:12:50 mcdasatest07 goferd[1479]: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://subs
May 16 13:12:50 mcdasatest07 goferd[1479]: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://su
May 16 13:12:50 mcdasatest07 goferd[1479]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://subscr
May 16 13:12:50 mcdasatest07 goferd[1479]: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 106 seconds
May 16 13:12:56 mcdasatest07 systemd[1]: redcloak.service holdoff time over, scheduling restart.
May 16 13:12:56 mcdasatest07 systemd[1]: Stopped Redcloak Security monitoring service.
– Subject: Unit redcloak.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit redcloak.service has finished shutting down.

halkeye · May 16, 2023, 9:20pm

I would recommend doing journalctl -u jenkins.service -e -n 100 to get the last 100 lines (-e) and goto the end of the log (e) of the jenkins service (-u) since you have lots of other noise in what you posted.

hollychen · May 16, 2023, 9:24pm

May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.Net.bind(Net.java:448)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:339)
May 16 13:12:05 mcdasatest07 jenkins[27540]: … 21 more
May 16 13:12:05 mcdasatest07 jenkins[27540]: 2023-05-16 20:12:05.881+0000 [id=1] SEVERE winstone.Logger#logInternal: Container startup fa
May 16 13:12:05 mcdasatest07 jenkins[27540]: java.net.BindException: Address already in use
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.Net.bind0(Native Method)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.Net.bind(Net.java:459)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.Net.bind(Net.java:448)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:339)
May 16 13:12:05 mcdasatest07 jenkins[27540]: Caused: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8080
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:304)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.Server.lambda$doStart$0(Server.java:402)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.server.Server.doStart(Server.java:398)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:93)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at winstone.Launcher.(Launcher.java:168)
May 16 13:12:05 mcdasatest07 jenkins[27540]: Caused: java.io.IOException: Failed to start Jetty
May 16 13:12:05 mcdasatest07 jenkins[27540]: at winstone.Launcher.(Launcher.java:172)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at winstone.Launcher.main(Launcher.java:390)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43
May 16 13:12:05 mcdasatest07 jenkins[27540]: at java.base/java.lang.reflect.Method.invoke(Method.java:566)
May 16 13:12:05 mcdasatest07 jenkins[27540]: at executable.Main.main(Main.java:347)
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 16 13:12:05 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
May 16 13:12:05 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service failed.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 16 13:12:06 mcdasatest07 systemd[1]: Stopped My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service failed.

hollychen · May 16, 2023, 9:24pm

journalctl -u jenkins.service -e -n 100

hollychen · May 16, 2023, 9:26pm

:/usr/lib/systemd/system>systemctl status jenkins.service
● jenkins.service - My Company Jenkins Controller
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2023-05-16 13:12:06 PDT; 16s ago
Process: 27540 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE)
Main PID: 27540 (code=exited, status=1/FAILURE)

May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service failed.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service holdoff time over, scheduling restart.
May 16 13:12:06 mcdasatest07 systemd[1]: Stopped My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
May 16 13:12:06 mcdasatest07 systemd[1]: Unit jenkins.service entered failed state.
May 16 13:12:06 mcdasatest07 systemd[1]: jenkins.service failed.
:/usr/lib/systemd/system>journalctl -xe
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 16 13:12:05 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.

hollychen · May 16, 2023, 9:29pm

:/usr/lib/systemd/system>journalctl -xe
May 16 13:12:05 mcdasatest07 systemd[1]: jenkins.service: main process exited, code=exited, status=1/FAILURE
May 16 13:12:05 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
– Subject: Unit jenkins.service has failed
– Defined-By: systemd
– Support:
– Unit jenkins.service has failed.
May 16 13:12:57 mcdasatest07 systemd[1]: Unit redcloak.service entered failed state.
May 16 13:12:57 mcdasatest07 systemd[1]: redcloak.service failed.
lines 1215-1272/1272 (END)
:/usr/lib/systemd/system>cd /opt/secureworks/redcloak/bin/
bash: cd: /opt/secureworks/redcloak/bin/: No such file or directory

MarkEWaite · May 16, 2023, 9:29pm

There is already something on that computer that is using network port 8080. You will need to find the thing that is using port 8080 and stop it.

Topic		Replies	Views
Jenkins failed to start Ask a question	4	4804	May 18, 2023
Just installed Jenkins 2.452.3 LTS for my Ubuntu 22 but encountered some issue like service failed to start Using Jenkins question	9	622	July 19, 2024
About the Using Jenkins category Using Jenkins	2	1678	July 1, 2024
Jenkins Installation error Ask a question	3	2017	July 9, 2024
Startup failed - status=217/USER Ask a question	2	802	June 23, 2023

Newly installed Jenkins 2.387 with java-11, jenkins service failed to start

– Unit jenkins.service has failed.

May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller. – Subject: Unit jenkins.service has failed – Defined-By: systemd – Support: systemd-devel Info Page

– Unit jenkins.service has failed.

Related topics

May 16 13:12:06 mcdasatest07 systemd[1]: start request repeated too quickly for jenkins.service
May 16 13:12:06 mcdasatest07 systemd[1]: Failed to start My Company Jenkins Controller.
– Subject: Unit jenkins.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page