Red Hat Bugzilla – Bug 1017342
SELinux policy denies write access to lock file upon dirsrv upgrade
Last modified: 2015-02-17 12:35:14 EST
Description of problem:
as part of FreeIPA, DS fails to restart upon upgrade.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install F19 and run freeipa server
2. Yum update and Reboot machine
Upgrade was to this version:
Log file shows
[09/Oct/2013:16:19:45 +0000] - Shutting down due to possible conflicts with other slapd processes
[09/Oct/2013:16:22:25 +0000] - Error - Unable to create /var/lock/dirsrv/slapd-OPENSTACK-FREEIPA-ORG/imports, Netscape Portable Runtime error -5966 (Access Denied.)
Was able to work around the problem with:
ausearch -m avc -ts recent | audit2allow -M ds-lock
semodule -i ds-lock.pp
the AVC shown by
ausearch -m avc -ts recent | audit2allow
allow dirsrv_t var_lock_t:dir create;
Is this something we need to add to the selinux policy, to allow ns-slapd to create/write to the /var/lock/dirsrv symlinked directories?
I'm not sure why the lock directory is var_lock_t. It should be dirsrv_var_lock_t:
[root@localhost ~]# ls -lZ /var/lock/dirsrv
drwxrwx---. nobody nobody unconfined_u:object_r:dirsrv_var_lock_t:s0 slapd-localhost
What is the status of this bug? Do we need to clone it for selinux-policy?
(In reply to Rich Megginson from comment #4)
> What is the status of this bug? Do we need to clone it for selinux-policy?
I think we need to see if it is reproducible first.
It's possible that this is related to the recent tmpfiles.d changes where we create /run/lock/dirsrv instead of /var/lock/dirsrv. This might require an additional fcontext setting.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.