Hello, I have a Dockerfile
where I have configured a supervisor
for workers, but after deploying the application my workers did not start taking tasks from SQS
. I already checked the runtime logs
section and this log keeps repeating Unlinking stale socket /var/run/supervisor.sock
. I did check var/run
directory and there no one supervisor.sock
file only supervisor.sock.9
. I don’t know how to fix it, everything was working fine yesterday. I didn’t make any changes to my “Dockerfile”. I would appreciate your help, thank you.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
Would you mind sharing your Dockerfile here if possible so I could take a quick look and see if I can identify what might be causing the problem.
One thing that you could try out is to add a command in your
Dockerfile
to remove the stale socket before starting the supervisor:That way the stale socket file is removed each time the container starts, preventing the error from occurring.
Best,
Bobby
I’m having the same problem. Our deployments to app platform stopped working on the April 8. maintenance deployment. A deployment about four hours before the maintenance deployment was deployed without a hitch.
Now I’m getting the
Unlinking stale socket /var/run/supervisor.sock
message during deployment until it times out.Had the same issue, but my builds started working again randomly last night. I guess something was fixed as I haven’t made any changes.
EDIT: No never mind, it still doesn’t work.