You've probably hit a bug in the SELinux policy, it was fixed in selinux-policy-targeted-1.17.30-2.80. Therefore you can either update your selinux-policy-targeted rpm to the latest version or disable SELinux with system-config-security level. -- John Dennis <jdennis at redhat.com>