Bug 738523
| Summary: | bind refuses to start in latest update. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Jones <davej> |
| Component: | bind | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | atkac, jesus, ovasik, pfrields |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-02 11:30:13 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
Dave Jones
2011-09-15 05:12:13 UTC
This is weird, I'm not sure how can this happen. Do you use chroot? Can you please post me perms of the /var/named, /var/named/data and /var/named/data/named.run directories/files (ls -lZ)? Thank you in advance. bind-chroot is installed. Stuff looks to be appearing in the chroot correctly. # ll -Z /var/ drwxr-x---. root named system_u:object_r:named_zone_t:s0 named/ # ll -Z /var/named/ drwxr-x---. root named system_u:object_r:named_conf_t:s0 chroot/ drwxrwx---. named named system_u:object_r:named_cache_t:s0 data/ lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 db.192.168.42 -> /var/named/chroot/var/named/db.192.168.42 lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 db.kernelslacker.org -> /var/named/chroot/var/named/db.kernelslacker.org drwxrwx---. named named system_u:object_r:named_cache_t:s0 dynamic/ lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 localdomain.zone -> /var/named/chroot/var/named/localdomain.zone lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 localhost.zone -> /var/named/chroot/var/named/localhost.zone lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.broadcast -> /var/named/chroot/var/named/named.broadcast -rw-r-----. root named system_u:object_r:named_conf_t:s0 named.ca lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.ca.rpmsave -> /var/named/chroot/var/named/named.ca -rw-r-----. root named system_u:object_r:named_zone_t:s0 named.empty lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.empty.rpmsave -> /var/named/chroot/var/named/named.empty lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.ip6.local -> /var/named/chroot/var/named/named.ip6.local lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.local -> /var/named/chroot/var/named/named.local -rw-r-----. root named system_u:object_r:named_zone_t:s0 named.localhost lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.localhost.rpmsave -> /var/named/chroot/var/named/named.localhost -rw-r-----. root named system_u:object_r:named_zone_t:s0 named.loopback lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.loopback.rpmsave -> /var/named/chroot/var/named/named.loopback lrwxrwxrwx. root root unconfined_u:object_r:named_zone_t:s0 named.zero -> /var/named/chroot/var/named/named.zero drwxrwx---. named named system_u:object_r:named_cache_t:s0 slaves/ /var/named/data/ is empty. (also setenforce 0 was tried, made no difference, so not selinux related) Anything else I can provide to diagnose this ? Can you please attach (or send me) your named.conf? I'm still unable to reproduce this issue... Also please run `rpm -qV bind` and `rpm -qV bind-chroot` to ensure your installation is correct. Thanks in advance! sent in email. The solution for me was to create the directory under the chroot path: cd /var/named mkdir chroot/var/named/data chown named:named chroot/var/named/data them verify in /var/log/messages the selinux alert and follow instructions to adapt selinux to this new directory under named control. (In reply to comment #6) > The solution for me was to create the directory under the chroot path: > > cd /var/named > mkdir chroot/var/named/data > chown named:named chroot/var/named/data > > them verify in /var/log/messages the selinux alert and follow instructions to > adapt selinux to this new directory under named control. Yes, this was also the solution for Dave Jones but I forgot to update this ticket, thanks for your post. Closing. |