Heinzi's avatar

Supervisor Unlinking stale socket /tmp/supervisor.sock

I have my Larvel project on a shared server which is a Debian Linux OS. I don`t have "sudo rights", but I managed to install supervisor. My supervisord.conf:

[unix_http_server]
file=/tmp/supervisor.sock    
[supervisord]
logfile=/tmp/supervisord.log 
logfile_maxbytes=50MB        
logfile_backups=10      
pidfile=/tmp/supervisord.pid 
nodaemon=false           
minfds=1024                 
minprocs=200               
[supervisorctl]
serverurl=unix:///tmp/supervisor.sock 
[program:laravel-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /path/to/app/artisan queue:work  --sleep=3 --tries=3
autostart=true
autorestart=true
;user=
numprocs=8
redirect_stderr=true
stdout_logfile=/path/to/app/worker.log

When I start:

supervisord -c supervisord.conf

I get permanently this error message:

Unlinking stale socket /tmp/supervisor.sock

supervisorctl status give my this answer:

unix:///tmp/supervisor.sock no such file

I did the same thing on my macOS Mojave OS and everything works fine. There is one different behavior on the shared Debian server; when I cd into my /tmp folder the sockets file looks like this: supervisor.sock.806621. The taling six-digit number gets generated randomly after entering supervisord -c supervisord.conf, so I can`t reflect it in my supervisord.conf. Can this be the source of the error, and I case it is, how do I use a wild card to reflect those digits for the socket name in my config file? Thx in advance

0 likes
0 replies

Please or to participate in this conversation.