Bug 966278 - SELinux is preventing /usr/libexec/postfix/cleanup from 'lock' accesses on the file /var/spool/postfix/pid/unix.cleanup.
SELinux is preventing /usr/libexec/postfix/cleanup from 'lock' accesses on th...
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-05-22 18:21 EDT by Eric Christensen
Modified: 2013-05-22 18:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-22 18:38:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eric Christensen 2013-05-22 18:21:27 EDT
Description of problem:
SELinux is preventing /usr/libexec/postfix/cleanup from 'lock' accesses on the file /var/spool/postfix/pid/unix.cleanup.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that cleanup should be allowed lock access on the unix.cleanup file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep cleanup /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:postfix_cleanup_t:s0
Target Context                system_u:object_r:postfix_var_run_t:s0
Target Objects                /var/spool/postfix/pid/unix.cleanup [ file ]
Source                        cleanup
Source Path                   /usr/libexec/postfix/cleanup
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           postfix-2.9.6-4.fc18.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-95.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 3.9.2-200.fc18.x86_64 #1 SMP Mon
                              May 13 13:59:47 UTC 2013 x86_64 x86_64
Alert Count                   5
First Seen                    2013-05-22 11:42:31 EDT
Last Seen                     2013-05-22 15:25:18 EDT
Local ID                      a0f8379e-390c-46e5-8803-9db7b9e2f0d0

Raw Audit Messages
type=AVC msg=audit(1369250718.811:570): avc:  denied  { lock } for  pid=10232 comm="cleanup" path="/var/spool/postfix/pid/unix.cleanup" dev="dm-2" ino=2229996 scontext=system_u:system_r:postfix_cleanup_t:s0 tcontext=system_u:object_r:postfix_var_run_t:s0 tclass=file

type=SYSCALL msg=audit(1369250718.811:570): arch=x86_64 syscall=flock success=yes exit=0 a0=8 a1=2 a2=2 a3=7fffb1c2fbb0 items=0 ppid=3411 pid=10232 auid=4294967295 uid=89 gid=89 euid=89 suid=89 fsuid=89 egid=89 sgid=89 fsgid=89 ses=4294967295 tty=(none) comm=cleanup exe=/usr/libexec/postfix/cleanup subj=system_u:system_r:postfix_cleanup_t:s0 key=(null)

Hash: cleanup,postfix_cleanup_t,postfix_var_run_t,file,lock


#============= postfix_cleanup_t ==============
allow postfix_cleanup_t postfix_var_run_t:file lock;

audit2allow -R
require {
	type postfix_cleanup_t;
	type postfix_var_run_t;
	class file lock;

#============= postfix_cleanup_t ==============
allow postfix_cleanup_t postfix_var_run_t:file lock;

Additional info:
hashmarkername: setroubleshoot
kernel:         3.9.2-200.fc18.x86_64
type:           libreport

Potential duplicate: bug 960900
Comment 1 Eric Christensen 2013-05-22 18:38:04 EDT
Package selinux-policy-3.11.1-96.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-96.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Note You need to log in before you can comment on or make changes to this bug.