Supervisor socket error issue

Question

$ supervisorctl reread
error: <class 'socket.error'>, [Errno 111] Connection refused: file: /usr/lib64/python2.6/socket.py line: 567

I'm trying to configure supervisor on my production system, but am hitting this error. The supervisor log file is empty.

When I just type supervisorctl, it complains:

http://localhost:9001 refused connection

Nothing is currently listening on port 9001, AFACT: lsof | grep TCP returns nothing.

see this : https://stackoverflow.com/a/66931708/5999939 – Arash Younesi Apr 03 '21 at 13:30 — Arash Younesi, Apr 03 '21 at 13:30

score 189 · Accepted Answer · answered Sep 17 '13 at 21:43

189

You have to start supervisord before you can use supervisorctl. In my case:

sudo supervisord -c /etc/supervisor/supervisord.conf
sudo supervisorctl -c /etc/supervisor/supervisord.conf

answered Sep 17 '13 at 21:43

kelorek

6,042
6
29
32

3

You shouldn't have to sudo supervisorctl, but I ran into permissions issues that caused me to give up on solving that problem – kelorek Oct 03 '13 at 21:08
1

I have same issued as kelorek but above command did not work on me. – Charlesliam May 23 '14 at 08:40
What returns when you hit enter? – kelorek May 24 '14 at 19:13
6

http://192.168.111.100:9001 refused connection – Charlesliam Jun 05 '14 at 08:08
You shouldn't have to specify the conf path. Both tools should be using the same default path. If they're not, then you may have a corrupted installation. – Cerin Feb 04 '17 at 16:59
This didnt fix the issue but showed me the exact error which was actually a log file not being created for a supervisor config of Django. – Pranaysharma Jan 05 '22 at 15:39

Jonathan · Answer 2 · 2015-03-30T15:24:47.963

42

If you started supervisord with a custom path, like this:

sudo supervisord -c /mypath/supervisord.conf

Then you should also start supervisorctl with the same parameter, like this:

sudo supervisorctl -c /mypath/supervisord.conf

edited Mar 30 '15 at 15:24

answered Dec 21 '14 at 03:52

Jonathan

13,947
17
94
123

score 13 · Answer 3 · answered Nov 10 '14 at 08:01

You can get this issue if you start supervisor with a relative url for -c and then try run supervisorctl from a different directory.

For example:

supervisord -c supervisord.conf
supervisorctl start someapp ## works 
cd somedirectory
supervisorctl restart someapp ## http://localhost:9001 refused connection

Solution would be to always use the absolute path. e.g.:

Good:

supervisord -c /etc/supervisor/supervisord.conf

Bad:

supervisord -c supervisord.conf

score 5 · Answer 4 · answered Sep 22 '16 at 18:34

This issue also occurs when an old vesion of supervisord.conf file is used. Newer version of supervisor uses different configuration file. The above solutions don't work. In this case you just have to regenerate the configuration file with

echo_supervisord_conf > /etc/supervisord.conf

Hope it helps someoone.

score 5 · Answer 5 · answered Jan 04 '17 at 18:19

5

please do the following :

sudo service supervisor start

post which everything is normal as b4 - there is a problem with 1b version

sudo supervisorctl reload

answered Jan 04 '17 at 18:19

VKB

59
1
3

score 2 · Answer 6 · edited Jun 20 '20 at 09:12

In Ubuntu 18.04 with distribution's package

You probably did the same mistake as me an created the config file /etc/supervisord.conf while my service manager (systemd) was using the config file /etc/supervisor/supervisord.conf

sudo rm /etc/supervisord.conf

Or

sudo mv /etc/supervisord.conf /etc/supervisor/supervisord.conf

if you want to keep it

Now you can run sudo supervisorctl

Why?

when you run supervisorctl it first searches for the config file located at /etc/supervisord.conf, if it's not present, it will search for the package's default file /etc/supervisor/supervisord.conf this is the one systemd actually runs.

Systemd always use the file /etc/supervisor/supervisord.conf regardless of the other file's existence.

You can check which file is using systemd by running sudo systemctl status supervisor

You can see in the last line the command where the config file is hardcoded

zhengquan · Answer 7 · 2020-01-14T14:09:21.810

-1

both supervisord and supervisorctl use -c with absolute config file path, make sure both commands startup with same config.

edited Jan 14 '20 at 14:09

answered Sep 04 '16 at 11:20

zhengquan

39
8

Supervisor socket error issue

7 Answers7

In Ubuntu 18.04 with distribution's package

Why?