handle script failure

ChainSafe · Jul 2, 2024 · 016a9d3 · 016a9d3
1 parent 80a9c30
commit 016a9d3
Show file tree

Hide file tree

Showing 2 changed files with 25 additions and 2 deletions.
diff --git a/ansible/archival-snapshots/resources/init.sh b/ansible/archival-snapshots/resources/init.sh
@@ -31,3 +31,16 @@ fi
 
 # Trigger main script
 ./main.sh
+
+EXIT_STATUS=$?
+
+# Notify on slack channel
+if [ "$EXIT_STATUS" -eq 0 ]; then
+    echo "Script executed successfully"
+    ruby notify.rb success
+else
+    echo "Script execution failed"
+    ruby notify.rb failure
+fi
+
+exit "$EXIT_STATUS"
diff --git a/ansible/archival-snapshots/resources/main.sh b/ansible/archival-snapshots/resources/main.sh
@@ -28,13 +28,25 @@ else
     echo "$LAST_FULL_SNAPSHOT_PATH snapshot exists."
 fi
 
+# Clean forest db
+$FOREST_TOOL db destroy --force
+
 echo "Starting forest daemon"
 nohup $FOREST --no-gc --config ./config.toml --save-token ./admin_token --rpc-address 127.0.0.1:3456 --metrics-address 127.0.0.1:5000 --import-snapshot "$LAST_FULL_SNAPSHOT_PATH" > forest.log 2>&1 &
 FOREST_NODE_PID=$!
 
 sleep 30
 echo "Forest process started with PID: $FOREST_NODE_PID"
 
+# Function to kill Forest daemon
+function kill_forest_daemon {
+    echo "Killing Forest daemon with PID: $FOREST_NODE_PID"
+    kill -KILL $FOREST_NODE_PID
+}
+
+# Set trap to kill Forest daemon on script exit or error
+trap kill_forest_daemon EXIT
+
 # Set required env variables
 function set_fullnode_api_info {
     ADMIN_TOKEN=$(cat admin_token)
@@ -98,5 +110,3 @@ while ((LATEST_EPOCH - LAST_EPOCH > 30000)); do
 
    LAST_EPOCH=$NEW_EPOCH
 done
-
-kill -KILL $FOREST_NODE_PID