Python Error when running supervisorctl

[gregpinero]

I just installed with pip but when I try to run it, I'm getting the strange error below. Any ideas what could be going on? Is it a bug?

$ sudo supervisorctl
error: <class 'socket.error'>, [Errno 97] Address family not supported by protocol: file: /usr/lib64/python2.6/socket.py line: 567

[msabramo]

What's in your supervisord.conf? Usually /etc/supervisor/supervisord.conf.

[mnaberez]

I'm going to close this due to lack of activity. If you're still having this issue and can provide more information, we can reopen.

[bbirand]

I get the exact same error on a freshly installed supervisor with the default configuration file as output by echo_supervisord_conf. I installed the configuration file locally, and am running it as a regular user and not root:

$ supervisorctl
error: <class 'socket.error'>, [Errno 97] Address family not supported by protocol: file: /usr/lib/python2.7/socket.py line: 571
supervisor>

[mcdonc]

@bbirand if you execute supervisorctl -c /explicit/path/to/config/file/echoed/out/supervisord.conf do you get the same error? If so, can you include the contents of that file in a separate comment?

[bbirand]

Yup, that fixed it. I didn't realize I had to pass the configuration file to the supervisorctl call as well, but of course it make sense.. Sorry for the wrong alarm.

(Although a more descriptive error message instead of the failed socket connection would be more helpful. I don't even have a /etc/supervisor.conf file, so I would have imagined supervisorctl would have failed with a "Configuration file not found" error or something.)

[mnaberez]

A specific "not found" error should be emitted if supervisord can't find a config file. In later versions, there's also a different "not readable" error if supervisord finds one but can't read it. When -c is not used to specify an explicit path to a config file, supervisord will search for one.

supervisorctl will also search for a config file. Before Supervisor 3.0b2, a config file was always required and it would give an error as described above. In 3.0b2 and later, supervisorctl can be used without a config file. In that case, the connection info should be given in command line options. I think if it can't find a config file, and you don't give the connection options, it defaults to http://localhost:9001 with no auth. I'm not certain about that.

It sounds like supervisorctl is searching for and finding another config file on your system, but that file contains a line that causes the Address family not supported by protocol error. It could also be that supervisorctl is using its default but the default causes this error on your system. It would be helpful if we could get more info. The last time this was reported we didn't find out.

Edit: Clarified supervisorctl behavior.

[bbirand]

Interesting. What was happening with me is that there was a supervisor.conf file in the current directory (the default one). When I run the command as supervisorctl I got the error, but when I switched to using supervisorctl -c supervisor.conf, I wouldn't get the error anymore. I should also note that this is from supervisor installed in a virtualenv.

From what I understand from your description, if a config file is found in the current directory, it should be used, and the behavior should be the same as running it explicitly with the -c switch. That's somehow not what happens on my end.

[mcdonc]

It appears that a commit in #95 introduced incorrect behavior (in particular, this commit: JensRantil@3385f17). It has been there since the end of 2011, and reverses the search order such that $CWD/etc/supervisord.conf will be found before $CWD/supervisord.conf.

I'll try to fix this in both the 3.1.X branch and master.

[mcdonc]

Oops, no, that commit is blameless. It just touched lines that were part of a preexisting bug, or at least a disagreement between the docs and the code.

[bbirand]

Great! But FWIW, I definitely didn't have a $CWD/etc/supervisor.conf file. So I'm not sure if this bug explains the discrepancy I observed when using the -c switch.

[ferrouswheel]

Not sure if there is a better issue to report this in, but seems related:

If I have a supervisord.conf in the current directory, but it has no supervisorctl section, then it's impossible to run supervisorctl with command line parameters:

$ supervisorctl -s "http://192.168.1.1:9001" -i
Error: .ini file does not include supervisorctl section
For help, use /usr/local/bin/supervisorctl -h

Running the same command in a different directory works fine.

I'd suggest either allowing explicit command line arguments to override the implicitly detected config file, or informing the user that they are ignored.

version 3.1.3