Jetty start script failure

[jo-elimu]

Description

An error prevents the server from launching:

systemctl start jetty

× jetty.service - LSB: Jetty start script.
     Loaded: loaded (/etc/rc.d/init.d/jetty; generated)
     Active: failed (Result: exit-code) since Sun 2025-01-12 12:12:29 UTC; 3s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 6311 ExecStart=/etc/rc.d/init.d/jetty start (code=exited, status=1/FAILURE)
        CPU: 26.224s

Jan 12 12:12:27 srv583801.hstgr.cloud jetty[6311]: .............................................
Jan 12 12:12:27 srv583801.hstgr.cloud jetty[6356]: 2025-01-12 12:12:27.677:INFO :oejshC.webapp_TGL_xml:main: Initializing Spring CustomDispatcherServlet 'd>
Jan 12 12:12:27 srv583801.hstgr.cloud jetty[6311]:  timeout
Jan 12 12:12:27 srv583801.hstgr.cloud jetty[6311]: INFO: Server process is running
Jan 12 12:12:27 srv583801.hstgr.cloud jetty[6311]: FAILED Sun Jan 12 12:12:27 PM UTC 2025
Jan 12 12:12:29 srv583801.hstgr.cloud jetty[6311]: .Killed 6356
Jan 12 12:12:29 srv583801.hstgr.cloud systemd[1]: jetty.service: Control process exited, code=exited, status=1/FAILURE
Jan 12 12:12:29 srv583801.hstgr.cloud systemd[1]: jetty.service: Failed with result 'exit-code'.
Jan 12 12:12:29 srv583801.hstgr.cloud systemd[1]: Failed to start LSB: Jetty start script..
Jan 12 12:12:29 srv583801.hstgr.cloud systemd[1]: jetty.service: Consumed 26.224s CPU time.

Why?

A fix is needed so that content creators can access the webapp.

---

• Possibly related to Upgrade from Jetty 10 to 11 #1797

[jo-elimu]

# journalctl -xeu jetty

Jan 12 14:26:41 srv583801.hstgr.cloud jetty[7178]: .
Jan 12 14:26:41 srv583801.hstgr.cloud jetty[7224]: 2025-01-12 14:26:41.763:INFO :oejshC.webapp_xml:main: No Spring WebApplicationInitializer types detected>
Jan 12 14:26:41 srv583801.hstgr.cloud jetty[7224]: 2025-01-12 14:26:41.867:INFO :oejshC.webapp_xml:main: Initializing Spring root WebApplicationContext
Jan 12 14:26:43 srv583801.hstgr.cloud jetty[7178]: . timeout
Jan 12 14:26:43 srv583801.hstgr.cloud jetty[7178]: INFO: Server process is running
Jan 12 14:26:43 srv583801.hstgr.cloud jetty[7178]: FAILED Sun Jan 12 02:26:43 PM UTC 2025
Jan 12 14:26:44 srv583801.hstgr.cloud jetty[7178]: .Killed 7224
Jan 12 14:26:44 srv583801.hstgr.cloud systemd[1]: jetty.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ An ExecStart= process belonging to unit jetty.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 12 14:26:44 srv583801.hstgr.cloud systemd[1]: jetty.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit jetty.service has entered the 'failed' state with result 'exit-code'.
Jan 12 14:26:44 srv583801.hstgr.cloud systemd[1]: Failed to start LSB: Jetty start script..
░░ Subject: A start job for unit jetty.service has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit jetty.service has finished with a failure.
░░
░░ The job identifier is 3943 and the job result is failed.
Jan 12 14:26:44 srv583801.hstgr.cloud systemd[1]: jetty.service: Consumed 38.969s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit jetty.service completed and consumed the indicated resources.