Description of problem: Default configuration file of supervisor contains a UNIX socket binding for an RPC interface: cat /etc/supervisord.conf ; Sample supervisor config file. [unix_http_server] file=/run/supervisor/supervisor.sock ; (the path to the socket file) But directory /run/supervisor is not part of a package (I've created it manually) rpm -qf /run/supervisor/ file /run/supervisor is not owned by any package Version-Release number of selected component (if applicable): rpm -qv supervisor supervisor-4.0.4-2.el8.noarch How reproducible: Install supervisor and run "supervisord -n -u root -c /etc/supervisord.conf" following will be shown: 2019-11-09 11:45:18,311 INFO Included extra file "/etc/supervisord.d/nginx.ini" during parsing 2019-11-09 11:45:18,312 INFO Set uid to user 0 succeeded Error: Cannot open an HTTP server: socket.error reported errno.ENOENT (2) For help, use /usr/bin/supervisord -h Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Supervisord will start and create a UNIX socket for the supervisorctl to use. Additional info:
FEDORA-EPEL-2019-1aaa997031 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1aaa997031
supervisor-4.0.4-3.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1aaa997031
supervisor-4.0.4-3.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.
Please note that this fix does not resolve the problem. The /var/run/supervisor directory should be included in the RPM as it is likely that it will be run inside docker which does NOT run systemd to create that directory as tmpfile. Is is possible to reopen this issue or should I submit a new one?
Please disregard the comment above, I created a new issue #1898106