Bug 1000190

Summary: Supervisor unix HTTP server socket doesn't get created
Product: [Fedora] Fedora EPEL Reporter: Andy Shinn <andys+redhat>
Component: supervisorAssignee: Francisco Javier Tsao Santín <tsao>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: a.badger, nphilipp, steve.traylen, tsao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-30 18:55:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andy Shinn 2013-08-22 22:00:48 UTC 
Description of problem:

Running older version of supervisor which has a broken unix HTTP server socket.


Version-Release number of selected component (if applicable):

2.1-8.el6


How reproducible:

Install supervisor and try to use the supervisorctl command.


Steps to Reproduce:
1. Install supervisor (sudo yum install supervisor)
2. Ensure the /etc/supervisord.conf has a configuration for unix HTTP server:

[unix_http_server]
file=/var/run/supervisor.sock

3. Start supervisor (sudo service supervisord start)
4. Attempt to invoke the supervisorctl utility (sudo supervisorctl status)

Actual results:

error: <class 'socket.error'>, [Errno 2] No such file or directory: file: <string> line: 1


Expected results:

worker1                RUNNING
worker2                STARTING
worker3                STOPPED

Additional info:

The socket file doesn't appear to get created for the unix HTTP server:

[vagrant@worker-vagrant ~]$ sudo ls /var/run/supervisor.sock
ls: cannot access /var/run/supervisor.sock: No such file or directory

There does not appear to be any major functional differences from 2.1 to 3.0 other than many added configuration options (I'm using 2.1 configurations on 3.0). Can we upgrade the EPEL package to the recently released 3.0 version?

I was able to rebuild the RPM to the 3.0 version with minimal changes (added explicit /etc/supervisord.conf to init script, require python-setuptools).
Comment 1 Francisco Javier Tsao Santín 2020-03-30 18:55:59 UTC 
The [unix_http_server] section is part of supervisor 3:
http://supervisord.org/upgrading.html#upgrading-supervisor-2-to-3

You must configure the http_port option in the [supervisord] section of the config file. The default config file:

[supervisord]
http_port=/var/tmp/supervisor.sock ; (default is to run a UNIX domain socket server)

Closing this ticket... 7 years later :-D