Rudder

In 7.0.3 I ended up with a rudder-jetty that did not want to start properly.
The status of the service was always "failed" and the logs were the following:

root@server:/var/log/rudder# systemctl status rudder-jetty
● rudder-jetty.service - Jetty Web Application Server
     Loaded: loaded (/lib/systemd/system/rudder-jetty.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-06-09 08:22:25 UTC; 1min 33s ago
    Process: 556 ExecStart=/opt/rudder/bin/rudder-jetty.sh start (code=exited, status=1/FAILURE)
        CPU: 173ms
root@server:/var/log/rudder# journalctl -u rudder-jetty
Jun 09 08:13:40 server rudder-jetty.sh[4416]: . . . . . . . . . . . . . . . FAILED Thu Jun  9 08:13:40 UTC 2022
Jun 09 08:13:40 server systemd[1]: rudder-jetty.service: Control process exited, code=exited, status=1/FAILURE
Jun 09 08:13:40 server systemd[1]: rudder-jetty.service: Failed with result 'exit-code'.
Jun 09 08:13:40 server systemd[1]: Failed to start Jetty Web Application Server.
Jun 09 08:15:02 server systemd[1]: Starting Jetty Web Application Server...
Jun 09 08:15:03 server rudder-jetty.sh[5130]: Setting umask to 0007
Jun 09 08:15:03 server rudder-jetty.sh[5130]: Starting Jetty:
Jun 09 08:15:03 server rudder-jetty.sh[5192]: process already running.
Jun 09 08:16:03 server rudder-jetty.sh[5130]: . . . . . . . . . . . . . . . FAILED Thu Jun  9 08:16:03 UTC 2022
Jun 09 08:16:03 server systemd[1]: rudder-jetty.service: Control process exited, code=exited, status=1/FAILURE
Jun 09 08:16:03 server systemd[1]: rudder-jetty.service: Failed with result 'exit-code'.
Jun 09 08:16:03 server systemd[1]: Failed to start Jetty Web Application Server.

The "process already running" made me run and kill the process found using ps:

root@server:/var/log/rudder# ps -afux | grep jetty
root        5126  0.0  0.0   2420   576 ?        S    08:15   0:00              |   \_ sh -c /bin/systemctl --no-ask-password start rudder-jetty.service
root        5128  0.0  0.0   7104  1160 ?        S    08:15   0:00              |       \_ /bin/systemctl --no-ask-password start rudder-jetty.service
root        5226  0.0  0.0   5204   708 pts/0    S+   08:15   0:00                      \_ grep jetty
root        5130  0.0  0.1   5860  3572 ?        Ss   08:15   0:00 bash /opt/rudder/bin/rudder-jetty.sh start
root@server:/var/log/rudder# pkill -9 5126

But even then the server could not start. I had to reboot the server and redo this procedure like 4 times before the webapp was accessible.
Also, after the reboot the service was well started, but the webapp was not accessible and only showed the loading page.