Add signal handling to agbot/css_start.sh

When run in a container anax is run via a shell script that does not
handle SIGTERM and hence when the container is stopped this signal does
not arrive to the binary for graceful exit. A consequence of this is
when run via docker compose up, docker compose down will have to wait
until the timeout in order to kill the process.

The same happens for the ccs-api.

This change adds proper SIGTERM handling to agbot_start.sh and
css_start.sh.

Signed-off-by: Leonardo Bergesio <[email protected]>

anax-in-container/script/agbot_start.sh

@@ -2,10 +2,19 @@
 
 # Script to start agbot from inside the container
 
-if [ -z "$ANAX_LOG_LEVEL" ]; then
+if [ -z "${ANAX_LOG_LEVEL}" ]; then
 	ANAX_LOG_LEVEL=3
 fi
 
 /usr/bin/envsubst < /etc/horizon/anax.json.tmpl > /etc/horizon/anax.json
-/usr/horizon/bin/anax -v $ANAX_LOG_LEVEL -logtostderr -config /etc/horizon/anax.json
+/usr/horizon/bin/anax -v "${ANAX_LOG_LEVEL}" -logtostderr -config /etc/horizon/anax.json &
+ANAX_PID=$!
 
+# If we receive SIGTERM, forward it to anax to start graceful termination
+send_sigterm() {
+        kill "${ANAX_PID}" 2>/dev/null
+}
+trap send_sigterm TERM
+
+# Wait for anax termination
+wait "${ANAX_PID}"

css/script/css_start.sh

@@ -1,4 +1,14 @@
 #!/bin/bash
 
 /usr/bin/envsubst < /etc/edge-sync-service/sync.conf.tmpl > /etc/edge-sync-service/sync.conf
-/home/cssuser/cloud-sync-service
+/home/cssuser/cloud-sync-service &
+CSS_PID=$!
+
+# If we receive SIGTERM, forward it to css to start graceful termination
+send_sigterm() {
+        kill "${CSS_PID}" 2>/dev/null
+}
+trap send_sigterm TERM
+
+# Wait for css termination
+wait "${CSS_PID}"