Supervisor not loading new configuration files
Solution 1:
The correct answer is that supervisor requires you to re-read and update when you place a new configuration file. Restarting is not the answer, as that will affect other services. Try:
supervisorctl reread
supervisorctl update
Solution 2:
I had the same issue, a
sudo service supervisord reload
did the trick, though I don't know if that is the answer to your question.
Solution 3:
Make sure your supervisor conf files end in .conf
Took me a while to figure that one out. Hopefully it helps the next person.
Solution 4:
Reloading the master supervisor process may work, but it will have unintended side effects if you have more than one process being monitored by supervisor.
The correct way to do it is to issue supervisorctl reread which causes it to scan configuration files for any changes:
root@debian:~# supervisorctl reread
gunicorn: changed
Then, simply reload that app:
root@debian:~# supervisorctl restart gunicorn
gunicorn: stopped
gunicorn: started
Solution 5:
I had a similar problem ( myapp_live: ERROR (no such process) ) and it was because my process definition was
[program: myapp_live]
when it should have been
[program:myapp_live]
While this doesn't address the question that was asked, I was lead here by the Search that Be looking for a solution to my problem, so hopefully other people find it here, too.