Bug 527384
Summary: | SELinux policy missing for /etc/init.d/named | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Ruben Saar <rsaar> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE <qe-baseos-auto> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | dwalsh, mykleb, rsaar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-07 17:06: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
Ruben Saar
2009-10-06 07:39:53 UTC
Is the ownership correct in the /var/chroot directory. dac_read_search means that root is trying to read files that it does not have read access to. I'm wondering if it might be the difference between running "/etc/init.d/named start" and "service named start". I've asked Ruben to try if the service command works, as that should execute the script with a sane environment (from "/" as working directory, instead of wherever $cwd was when he ran the script). BTW: these are the ownerships dwalsh asked for: [janfrode@ns1ext ~]$ sudo ls -ldZ /var/named drwxr-x--- named hostmaster system_u:object_r:named_zone_t /var/named [janfrode@ns1ext ~]$ sudo ls -ldZ /var/named/chroot drwxr-x--- named hostmaster system_u:object_r:named_conf_t /var/named/chroot Group "hostmaster" is a local modification, so not what standard RHEL5 would use for these. I think the default is group "named". Answer to comment#2: With "sudo service named start" the same error occurs. BTW: /var/named/chroot is a separate volume/fs: [janfrode@ns1ext ~]$ df -h /var/named/chroot Filesystem Size Used Avail Use% Mounted on /dev/mapper/rootvg-chrootlv 6.9G 518M 6.1G 8% /var/named/chroot that might be relevant... Since you changed the ownership of the directories from root to named you need to add this additional access. Great, thanks! I have no idea why we've changed this permission, so we should probably change it back to the default. Especially since the bind-chroot package quite often will reset permissions on upgrades anyway.. |