Im trying to make automatic deployment including supervisord and confused by default settings path.
Every deployment scheme I found use /etc/supervisor/supervisor
You may have installed supervisor via pip and therefore have the unpatched version in
/usr/local/lib/python2.7/dist-packages/supervisor/
taking precedance over the patched version in
/usr/lib/pymodules/python2.7/supervisor
See Martjin's answer for details on the patch. The simple solution is to:
pip uninstall supervisor
Then rerun the package install in case it was only partially installed:
apt-get install supervisor
Also make sure your /etc/supervisor/supervisord.conf
is present. If not, you may need to manually recreate it, mine looks like this:
; supervisor config file
[unix_http_server]
file=/var/run//supervisor.sock ; (the path to the socket file)
chmod=0700 ; 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