Hello @jenkinscommunity, I know upgrading jenkins just by replacing .war file is bypassing configuration process and wont be work perfectly in some cases.
One of my colleague done the same, he messed jenkins service using .war file and its throwing failed error always. I am sharing logs. and Using RHL-7
systemd-analyze verify jenkins.service
[/usr/lib/systemd/system/asr-installga.service:11] Support for option SysVStartPriority= has been removed and it is ignored
Cannot add dependency job for unit waagent-network-setup.service, ignoring: Unit not found.
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 Mon 2023-08-14 16:16:03 CEST; 29min ago
Process: 4109 ExecStart=/usr/bin/jenkins (code=exited, status=203/EXEC)
Main PID: 4109 (code=exited, status=203/EXEC)
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: jenkins.service: main process exited, code=exited, status=…EXEC
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: Failed to start Jenkins Continuous Integration Server.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: Unit jenkins.service entered failed state.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: jenkins.service failed.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: jenkins.service holdoff time over, scheduling restart.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: Stopped Jenkins Continuous Integration Server.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: start request repeated too quickly for jenkins.service
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: Failed to start Jenkins Continuous Integration Server.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: Unit jenkins.service entered failed state.
Aug 14 16:16:03 shhlsr2040.global.schindler.com systemd[1]: jenkins.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
I don’t want to go with latest version 2.401 LTS right now using
*#yum update jenkins*
Following is the logs /var/log/jenkins.log
Running from: /usr/share/java/jenkins.war
2023-08-14 06:47:14.196+0000 [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMax is now deprecated
2023-08-14 06:47:14.218+0000 [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMaxIdle is now deprecated
2023-08-14 06:47:14.225+0000 [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @532ms to org.eclipse.jetty.util.log.JavaUtilLog
2023-08-14 06:47:14.292+0000 [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file
2023-08-14 06:47:14.332+0000 [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
2023-08-14 06:47:14.404+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.43.v20210629; built: 2021-06-30T11:07:22.254Z; git: 526006ecfa3af7f1a27ef3a288e2bef7ea
9dd7e8; jvm 1.8.0_352-b08
2023-08-14 06:47:14.759+0000 [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2023-08-14 06:47:14.812+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0
2023-08-14 06:47:14.813+0000 [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults
2023-08-14 06:47:14.814+0000 [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 660000ms
2023-08-14 06:47:15.379+0000 [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/lib/jenkins found at: SystemProperties.getProperty(“JENKINS_HOME”)
2023-08-14 06:47:15.553+0000 [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@495ee280{Jenkins v2.332.1,/,file:///var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenki
ns/war}
2023-08-14 06:47:15.633+0000 [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@34b7bfc0{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2023-08-14 06:47:15.634+0000 [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @1941ms
2023-08-14 06:47:15.637+0000 [id=21] INFO winstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled
2023-08-14 06:47:17.324+0000 [id=27] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization
2023-08-14 06:47:18.116+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins
2023-08-14 06:47:38.428+0000 [id=30] WARNING o.j.r.u.AnonymousClassWarnings#warn: Attempt to (de-)serialize anonymous class hudson.plugins.disk_usage.DiskUsageProjectActionFactory$De
scriptorImpl$1 in file:/var/lib/jenkins/plugins/disk-usage/WEB-INF/lib/disk-usage.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
2023-08-14 06:47:38.447+0000 [id=30] WARNING o.j.r.u.AnonymousClassWarnings#warn: Attempt to (de-)serialize anonymous class hudson.plugins.disk_usage.DiskUsageOvearallGraphGenerator$
DiskUsageRecord$1 in file:/var/lib/jenkins/plugins/disk-usage/WEB-INF/lib/disk-usage.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
2023-08-14 06:47:41.691+0000 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins
2023-08-14 06:47:42.780+0000 [id=29] WARNING o.j.p.s.scripts.ScriptApproval#: There are 17 deprecated approved script hashes and 0 deprecated approved classpath hashes. They will be rehashed upon next use and that may cause performance issues until all of them are converted or removed.
My question is ,can it possible to upgrade 2.235.1 to 2.332.1 ?
if yes please give me hint, so that I could go with.
using .war it cannot work for me. Please suggest me if is there any way to upgrade to 2.332.1 using RPM…