Description of problem: restart loop with each start failing with RTNETLINK answers: File exists Version-Release number of selected component (if applicable): cjdns-21.1-3 How reproducible: Always Steps to Reproduce: 1. Add a script to /etc/cjdns/up.d that fails, e.g. by adding a dup route 2. start/restart cjdns 3. Actual results: systemd sees up failure as startup failure and restart, rinse, repeat Expected results: up scripts execution should be logged, and failure should probably be ignore, or cjdns-up moved to one-shot service that starts after cjdns. Additional info: I've already pushed up script logging to epel8 and rawhide.
Pushed to epel7.
FEDORA-EPEL-2022-3c2dcad1af has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3c2dcad1af
FEDORA-EPEL-2022-50bff7a126 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-50bff7a126
FEDORA-EPEL-2022-50bff7a126 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-50bff7a126 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-3c2dcad1af 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-2022-3c2dcad1af See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-50bff7a126 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-3c2dcad1af has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.