Description of problem: This refers to the 1.13 package in EPEL. The systemd unit file will not start the service because the systemd support flag was not used at compile time. The notify type was used, which is a puzzling choice given the lack of systemd support. From the pgbouncer install notes: "To enable systemd integration, use the configure option --with-systemd. This allows using Type=notify service units as well as socket activation." This unit file has no chance of working. Also, I tried every other type and none of them worked, which suggests there's more wrong with the systemd side of the packaging than just the service type. I think the packaging scripts used by the postgresql folks should be used for the EPEL package, since there's some testing already behind those packages, and it should be placed in the testing area for awhile before being moved to stable EPEL. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: Try to start the service with systemctl Actual results: Expected results: Additional info:
If the program is not forking (like pgbouncer) you can just remove the type line and it will just work. The notify line was an unfortunate last minute addition. I've updated the package.
FEDORA-EPEL-2020-06912b5f25 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-06912b5f25
FEDORA-2020-ee3cba948a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee3cba948a
FEDORA-2020-8d91442bf5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8d91442bf5
FEDORA-EPEL-2020-f76ab6075a has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76ab6075a
FEDORA-EPEL-2020-f76ab6075a has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76ab6075a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-ee3cba948a has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ee3cba948a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee3cba948a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-8d91442bf5 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8d91442bf5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8d91442bf5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-06912b5f25 has been pushed to the Fedora EPEL 6 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-06912b5f25 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-ee3cba948a has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-8d91442bf5 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-f76ab6075a has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-06912b5f25 has been pushed to the Fedora EPEL 6 stable repository. If problem still persists, please make note of it in this bug report.