fix: JVM apps stopping to differ from failure #15632

antobinary · 2022-09-02T02:08:02Z

What does this PR do?

sets SuccessExitStatus on JVM applications to 143 so that when we stop these services (intentionally) they don't count it as a failure
Intructed bbb-fsesl-akka to only start once freeswitch is running and bbb-apps-akka to only start once bbb-fsesl-akka is running. This should avoid some rare-ish cases where slow freeswitch launch would cause a few BBB components ot fail launching

Closes Issue(s)

Closes #none

Motivation

https://serverfault.com/a/695863 for 143

It looked like this before when triggering bbb-conf --stop

root@droplet-1070:~# journalctl -f | grep -i "failed with result"


Sep 01 13:56:48 droplet-1070 systemd[1]: bbb-fsesl-akka.service: Failed with result 'exit-code'.
Sep 01 13:56:48 droplet-1070 systemd[1]: bbb-apps-akka.service: Failed with result 'exit-code'.
Sep 01 13:56:49 droplet-1070 systemd[1]: bbb-web.service: Failed with result 'exit-code'.
Sep 01 13:56:52 droplet-1070 systemd[1]: bbb-rap-resque-worker.service: Failed with result 'exit-code'.

And after these changes:

root@droplet-1070:~# journalctl -f | grep -i "failed with result"
Sep 01 13:56:52 droplet-1070 systemd[1]: bbb-rap-resque-worker.service: Failed with result 'exit-code'.

The remaining one is a bit more complex to resolve and not really causing much noise right now.