Bug 1000190 - Supervisor unix HTTP server socket doesn't get created
Supervisor unix HTTP server socket doesn't get created
Status: NEW
Product: Fedora EPEL
Classification: Fedora
Component: supervisor (Show other bugs)
el6
All Linux
unspecified Severity low
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-22 18:00 EDT by Andy Shinn
Modified: 2015-11-03 08:54 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andy Shinn 2013-08-22 18:00:48 EDT
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).

Note You need to log in before you can comment on or make changes to this bug.