I've been using supervisor for over a year now. It is installed from a Debian package. When I upgraded the package the other day, something break and I can't seem to figure out what.
~> sudo supervisorctl status http://localhost:9001 refused connection ~> cd /etc/supervisor ~> sudo supervisorctl status # Works
/etc/supervisor/supervisord.conf, I told supervisor to use a unix socket like this :
It looks like that when I'm not inside the
/etc/supervisor folder, the configuration is just not loaded and supervisor uses the defaults (http://localhost:9001 being the default for
I checked out the way the Debian package starts supervisor and it seems the path to the configuration file is absolute so I don't understand why it doesn't work.
/usr/bin/python /usr/bin/supervisord -c /etc/supervisor/supervisord.conf
Anyone having the same issue or a solution ? It's quite annoying as it breaks my ansible recipes. Thanks
Here is the full content of /etc/supervisor/supervisord.conf :
[unix_http_server] file=/var/run/supervisor.sock chmod=0700 [supervisord] logfile=/var/log/supervisor/supervisord.log pidfile=/var/run/supervisord.pid childlogdir=/var/log/supervisor [rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface [supervisorctl] serverurl=unix:///var/run/supervisor.sock [include] files = /etc/supervisor/conf.d/*.conf
And here are the requested variables :
~> which supervisorctl /usr/bin/supervisorctl ~> which supervisord /usr/bin/supervisord ~> supervisord --version 3.1.3