This feature has been added to Supervisor back in 2014 environment=PATH=”/home/site/environments/master/bin:%(ENV_PATH)s” see https://github.com/Supervisor/supervisor/blob/95ca0bb6aec582885453899872c60b4174ccbd58/supervisor/skel/sample.conf#L7 See also https://stackoverflow.com/questions/12900402/supervisor-and-environment-variables
You’re probably missing the [supervisord] section in the file. See this. For example, [supervisord] logfile = /tmp/supervisord.log logfile_maxbytes = 50MB logfile_backups=10 loglevel = info pidfile = /tmp/supervisord.pid nodaemon = false minfds = 1024 minprocs = 200 umask = 022 user = chrism identifier = supervisor directory = /tmp nocleanup = true childlogdir = /tmp strip_ansi … Read more
Ah, you use supervisorctl start groupname:* I discovered this by typing just supervisorctl start and being told: Error: start requires a process name start <name> Start a process start <gname>:* Start all processes in a group start <name> <name> Start multiple processes or groups start all Start all processes …similarly for stop and restart.
There is a plugin called superlance. You install it with pip install superlance or download it at: http://pypi.python.org/pypi/superlance The next thing you do is you go into your supervisord.conf and add the following lines: [eventlistener:crashmail] command=/usr/local/bin/crashmail -a -m email1@example.com events=PROCESS_STATE This should be followed by a “supervisorctl update”. When a process “exits” you will now … Read more
Actually, I found one that works here http://gist.github.com/176149. To install it: sudo curl https://gist.github.com/howthebodyworks/176149/raw/88d0d68c4af22a7474ad1d011659ea2d27e35b8d/supervisord.sh > /etc/init.d/supervisord to run it sudo chmod +x /etc/init.d/supervisord and to automatically schedule it, do sudo update-rc.d supervisord defaults Make ensure correct pid in /etc/supervisord.conf which is mapped in /etc/init.d/supervisord example: pidfile=/var/run/supervisord.pid Stop and Start work properly service supervisord stop service … Read more
Just ran into this as well. I fixed it by doing either of these: sudo unlink /tmp/supervisor.sock sudo unlink /var/run/supervisor.sock This .sock file is defined in /etc/supervisord.conf [unix_http_server] file config value (default is /tmp/supervisor.sock or /var/run/supervisor.sock). Hope this helps someone in the future.