Description of problem: When trying to start unbound with `service unbound start` and it fails for one reason or another (e.g. address already in use), even though the error and FAILED message is clearly printed, the exit status of the initscript is still 0: the error is not reported in the exit status. Among other, this tricks management scripts into wrongly believing that the service was started successfully, etc. Indeed, there is no provision in the initscript such as `set -e` or `exit $?` to report error codes. Version-Release number of selected component (if applicable): 1.4.19-1.el6
Non-fatal POSTIN scriptlet failure in rpm package unbound-libs-1.4.21-1.el6.x86_64 warning: %post(unbound-libs-1.4.21-1.el6.x86_64) scriptlet failed, exit status 1
unbound-1.5.1-2.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9fdb5f90e7
please test?
unbound-1.5.1-2.el6 has been pushed to the Fedora EPEL 6 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-2016-9fdb5f90e7
unbound-1.5.1-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
I long stopped administrating these systems, I'll be unable to test.