Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Let's say I have a number of existing workers running in supervisord. I want to add a new worker to the group as well as start the new worker. I perform the following steps:

  1. I modify the file /etc/supervisor/supervisord.conf and add the new worker config
  2. Back on the command line, I enter sudo supervisorctl
  3. I run reread to read the new configuration file settings.
  4. Attempting to run start workers:exampleWorkerName gives the error workers:"exampleWorkerName": ERROR (no such process)

So, my question is, how can I start this new worker process without affecting my other existing workers? I'd rather not perform a supervisorctl reload or /etc/init.d/supervisord restart command.

share|improve this question
up vote 1 down vote accepted

You also need to run supervisorctl update.

share|improve this answer
Running supervisorctl update will unfortunately restart all workers. Here's a sample of the output: workers: stopped followed by workers: updated process group. The worker status shows they were all restarted. – cballou Aug 2 '13 at 14:58
I should probably also say that I am using groups allowing me to restart all workers at once, so this might be the cause. – cballou Aug 2 '13 at 15:22

If you are still interested, after running

supervisorctl reread

you can try running

supervisorctl add <newWorker>
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.