Bug 112350
| Summary: | rndc dumpdb could not open dump file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Doug Palmer <doug.palmer> |
| Component: | bind | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED DUPLICATE | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 19:00:27 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: | |||
The problem is that we do not want to allow named to write to the /var/named directory, which is where the dumpfile is attempting to be created. You can create a subdirectory dump under /var/named or /var/chroot/var/named and change its owner ship to named.named. Then modify the /etc/named.conf file to include the following option dump-file "dump/named_dump.db"; Then it will work. Dan Since named chroots, the dump directory needs to be under /var/named/chroot/var/named and the /etc/named.conf files also needs to be copied to /var/named/chroot/etc I think that this should be fixed in the named RPM and in the configuration tools. *** This bug has been marked as a duplicate of 126638 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Opera/7.23 (X11; Linux i686; U) [en] Description of problem: Using rndc to produce a dump of the nameserver does not produce a dump file. Command (as root): rndc dumpdb An error appears in /var/log/messages: named[4939]: could not open dump file: permission denied Version-Release number of selected component (if applicable): 9.2.2.P3-9 How reproducible: Always Steps to Reproduce: 1. Login as root 2. Enter 'rndc dumpdb' 3. tail /var/log/messages Actual Results: Nothing, other than the error message. Expected Results: A dump file should appear somewhere. Additional info: