<p>Supervisorctl unix:///var/run/supervisor.sock verweigerte Verbindung</p>

Beim Ausführen von supervisorctl erhalte ich unix:///var/run/supervisor.sock refused connection .

Vielleicht ist es relevant, ich führe Supervisor in einem Debian-Docker-Container in CoreOS in Virtualbox aus. Ich führe supervisorctl aus dem Container aus.

supervisord -v : 3.0
ls -al /var/run/supervisor.sock : srwxrwxrwx. 1 root root 0 Sep 2 09:34 /var/run/supervisor.sock

Konfiguration:

; supervisor config file

[unix_http_server]
file=/var/run/supervisor.sock   ; (the path to the socket file)
chmod=0777                       ; sockef file mode (default 0700)

[supervisord]
logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)

; the below section must remain in the config file for RPC
; (supervisorctl/web interface) to work, additional interfaces may be
; added by defining them in separate rpcinterface: sections
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

[supervisorctl]
serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket

; The [include] section can just contain the "files" setting.  This
; setting can list multiple files (separated by whitespace or
; newlines).  It can also contain wildcards.  The filenames are
; interpreted as relative to this file.  Included files *cannot*
; include files themselves.

[include]
files = /etc/supervisor/conf.d/*.conf