The problem that the supervisor adds a new configuration does not take effect, the supervisor prompts: xxx: ERROR (no such process)

After adding a new configuration file xxx.conf, use supervisorctl start xxx to prompt “xxx: ERROR (no such process)”.

Using supervisorctl start all does not work either.

solve:

After adding a configuration file, use

supervisorctl reread

supervisorctl reload (not running this step will cause it to fail to start)

The supervisorctl update command will automatically load the new configuration and start the process after using this command.