Red Hat Bugzilla – Bug 1255159
supervisord fails to start due to inability to create its socket
Last modified: 2015-08-23 22:52:42 EDT
Description of problem:
supervisord fails to start with the message:
supervisord: Error: Cannot open an HTTP server: socket.error reported errno.ENOENT (2)
Version-Release number of selected component (if applicable):
It appears that after a recent update, the socket path has been changed from:
This seems to be happening because the `/var/run/supervisor` directory does not exist. If the aforementioned directory is created before running supervisord, the service starts normally.
Please include a tmpfiles configuration so that the needed directory is auto-created.
Bah. I thought I had. ;(
will try and correct this soon...
Can you test this scratch build and see if it works in your testing:
Thanks for looking into this. I've updated to supervisor-3.1.3-3.el7.noarch and it seems to fix the issue. supervisord starts without problems and also supervisorctl works as expected (as root).
Yes, that fixes the issue we're seeing here as well.
supervisor-3.1.3-3.el7 has been submitted as an update to Fedora EPEL 7. https://bugzilla.redhat.com/show_bug.cgi?id=1255159
supervisor-3.1.3-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update supervisor'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7728
supervisor-3.1.3-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.