Bug 499793
Summary: | unbound fails on startup when called from init | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Noa Resare <noa> |
Component: | unbound | Assignee: | Paul Wouters <pwouters> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | el5 | CC: | pwouters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-20 16:13:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Noa Resare
2009-05-08 08:16:41 UTC
The real fix to this issue is suggested on http://www.nlnetlabs.nl/bugs/show_bug.cgi?id=251 and the upstream maintainer plans to implement it for unbound-1.3.1. The fact that the problem can be worked around by starting the service interactively in 1.2.1-4 is due to a bug that has been fixed in current unbound svn head. See http://www.nlnetlabs.nl/bugs/show_bug.cgi?id=250 In the interim, since this is an issue that probably causes some confusion to new users I would suggest that you patch the unbound.conf file that ships with the package to read "control-enable: no" in the remote-control section. This bypasses the startup failure originally described above (which definitely counts as non-obvious). Fixed in 1.2.1-1 for EL-5 and in 1.2.1-6 in rawhide. Also in next releases in F-* |