Supervisor/supervisor — Issue #62: Cannot use supervisorctl remotely without an empty config file
Author: JensRantil
Created: 2011-12-02 10:03:28+00:00
State: open

This issue came out of a discussion[1,2] on the supervisor-users mailing list.

When trying to connect remotely using `supervisorctl` I get

$ supervisorctl -s http://myserver:9001
Error: No config file found at default paths (/usr/local/etc/supervisord.conf, /usr/local/supervisord.conf, supervisord.conf, etc/supervisord.conf, /etc/supervisord.conf); use the -c option to specify a config file at a different path
For help, use /usr/local/bin/supervisorctl -h

My server does not have any password or anything like that, and I can access the server through my web browser.

To overcome this problem I need to create an empty configuration file with the following content:

[supervisorctl]

and then use it when invoking `supervisorctl`:

$ supervisorctl -c mysupervisor.conf -s http://myserver:9001
my_process RUNNING pid 7385, uptime 2 days, 15:45:40
supervisor>

My proposal is to not require a configuration file when server is given by command line. I consider this a bug.

[1] http://lists.supervisord.org/pipermail/supervisor-users/2011-December/000991.html
[2] http://lists.supervisord.org/pipermail/supervisor-users/2011-December/000993.html