We are using zero downtime deployments for our project (Deployer). When deploying some new code the worker seems to run into problems. All jobs continuously fail with the message "Failed to shutdown worker.". I figure this has something to do with with paths/symlink changing when a new deployment is executed.
The only fix I found for now is to stop the supervisor job completely en restart it again, I was wondering if this is a known problem and if there would be a more low level solution. As restarting supervisor requires root and is therefor a pain to integrate in our deployment logic.
Hi,
We are using zero downtime deployments for our project (Deployer). When deploying some new code the worker seems to run into problems. All jobs continuously fail with the message "Failed to shutdown worker.". I figure this has something to do with with paths/symlink changing when a new deployment is executed.
The only fix I found for now is to stop the supervisor job completely en restart it again, I was wondering if this is a known problem and if there would be a more low level solution. As restarting supervisor requires root and is therefor a pain to integrate in our deployment logic.
Thanks in advance.