Jenkins service is not starting

The Jenkins service was working upto October 26 , No patches or update/upgrade was done on the server recently before the issue started.
we tried to start the service but it wont start,. When I check the status of the Jenkins service, below is the status that I am getting.
I have also uploaded a screenshot of the error I received when I start the service.

jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/usr/lib/systemd/system/jenkins.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/jenkins.service.d
└─override.conf
Active: deactivating (stop-sigterm) (Result: timeout)
Main PID: 14419 (java)
Status: “Stopping Jenkins”
CGroup: /system.slice/jenkins.service
└─14419 /usr/bin/java -Djava.awt.headless=true -jar /usr/share/java/jenkins.war --webroot=%C/jenkins/war --httpPort=8080 --httpsPort=8443 --httpsListenAddress=0.0.0.0 --httpsKeyStore=/etc/jenkins/xxxxxx.jks–httpsKeyStorePassword=xxxxxxxxxx

Oct 27 11:34:26 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:26.509+0000 [id=105] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished Download metadata. 94 ms
Oct 27 11:34:26 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:26.536+0000 [id=62] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.370+0000 [id=109] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Started DockerContainerWatchdog Asynchronous Periodic Work
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.370+0000 [id=109] INFO c.n.j.p.d.DockerContainerWatchdog#execute: Docker Container Watchdog has been triggered
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.372+0000 [id=109] INFO c.n.j.p.d.DockerContainerWatchdog$Statistics#writeStatisticsToLog: Watchdog Statistics: Number of overall executions: 0, Executions with processing timeout: 0, Containers removed gracefully: 0, Containers removed with force: 0, Containers removal failed: 0, Nodes removed successfully: 0, Nodes removal failed: 0, Container removal average duration (gracefully): 0 ms, Container removal average duration (force): 0 ms, Average overall runtime of watchdog: 0 ms, Average runtime of container retrieval: 0 ms
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.372+0000 [id=109] INFO c.n.j.p.d.DockerContainerWatchdog#loadNodeMap: We currently have 0 nodes assigned to this Jenkins instance, which we will check
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.372+0000 [id=109] INFO c.n.j.p.d.DockerContainerWatchdog#execute: Docker Container Watchdog check has been completed
Oct 27 11:34:43 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:34:43.373+0000 [id=109] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$1: Finished DockerContainerWatchdog Asynchronous Periodic Work. 2 ms
Oct 27 11:35:42 dol-uim-devops-jen-x-01 systemd[1]: jenkins.service start operation timed out. Terminating.
Oct 27 11:35:42 dol-uim-devops-jen-x-01 jenkins[14419]: 2022-10-27 15:35:42.539+0000 [id=50] INFO winstone.Logger#logInternal: JVM is terminating. Shutting down Jetty

That seems unlikely given your screenshot.

Looks like a plugin is trying to access a class that can’t be found. Maybe a plugin was installed that depends on another plugin that wasn’t upgraded or something.

Search · org:jenkinsci com.github.fge.jsonschema.tree.JsonTree · GitHub doesn’t return anything, so I’m not sure what plugin would be trying to use that class. Maybe try searching the xml files in $JENKINS_HOME/jobs for that class name? maybe some old temporary file or something.

1 Like