blender/flamenco
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Deploy: move old worker executable before overwriting

Browse Source 
Move the old worker out of the way. This should keep the old executable
as-is on disk, hopefully keeping currently-running processes happy.

I've noticed some workers crashing as soon as the executable got
replaced, which made me suspect that it's not 100% loaded to memory
before starting the execution. Let's see if this works better.
This commit is contained in:
Sybren A. Stüvel 2023-07-06 16:25:12 +02:00
parent 988cdf61ff
commit 2bc6c77e49
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
deploy.sh
View File

@ -2,6 +2,7 @@
MY_DIR="$(dirname "$(readlink -e "$0")")" MY_DIR="$(dirname "$(readlink -e "$0")")"
ADDON_ZIP="$MY_DIR/web/static/flamenco3-addon.zip" ADDON_ZIP="$MY_DIR/web/static/flamenco3-addon.zip"
WORKER_TARGET=/shared/software/flamenco3-worker/flamenco-worker
set -e set -e
@ -22,7 +23,12 @@ scp flamenco-manager flamenco.farm.blender:/home/flamenco3/
ssh -o ClearAllForwardings=yes flamenco.farm.blender -t sudo systemctl start flamenco3-manager ssh -o ClearAllForwardings=yes flamenco.farm.blender -t sudo systemctl start flamenco3-manager
prompt "Deploying Worker" prompt "Deploying Worker"
cp -f flamenco-worker /shared/software/flamenco3-worker if [ -e "$WORKER_TARGET" ]; then
# Move the old worker out of the way. This should keep the old executable
# as-is on disk, hopefully keeping currently-running processes happy.
mv "$WORKER_TARGET" "$WORKER_TARGET.old"
fi
cp -f flamenco-worker "$WORKER_TARGET"
prompt "Deploying Blender Add-on" prompt "Deploying Blender Add-on"
rm -rf /shared/software/addons/flamenco rm -rf /shared/software/addons/flamenco