Question

App platform supervisor error

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.


Submit an answer


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!

Sign In or Sign Up to Answer

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.

Bobby Iliev
Site Moderator
Site Moderator badge
April 21, 2024
Accepted Answer

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:

RUN rm -f /var/run/supervisor.sock
CMD ["supervisord", "-c", "/etc/supervisor/conf.d/supervisord.conf"]

That way the stale socket file is removed each time the container starts, preventing the error from occurring.

Best,

Bobby

I had the same problem so I contacted DO support and they helped me:

It seems like something in supervisord’s management HTTP server is incompatible with updated versions of gVisor security isolation runtime we use. We’ve found a minimal reproducer and are working with the gVisor team to get the issue fixed. In the meantime, you can likely work around this by disabling the unix_http_server configuration in their supervisors.conf.

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.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Become a contributor for community

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

DigitalOcean Documentation

Full documentation for every DigitalOcean product.

Resources for startups and SMBs

The Wave has everything you need to know about building a business, from raising funding to marketing your product.

Get our newsletter

Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

New accounts only. By submitting your email you agree to our Privacy Policy

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.