Description of problem: I'm not sure of the details of the problem. However, they started occurring after I rebooted with a freshly compiled/installed kernel version 3.2.44. SELinux is preventing /usr/bin/ps from using the 'sys_ptrace' capabilities. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that ps should have the sys_ptrace capability by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep ps /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:ksmtuned_t:s0 Target Context system_u:system_r:ksmtuned_t:s0 Target Objects [ capability ] Source ps Source Path /usr/bin/ps Port <Unknown> Host (removed) Source RPM Packages procps-ng-3.3.3-4.20120807git.fc18.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-92.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 3.2.44 #1 SMP Tue May 7 06:40:12 CDT 2013 x86_64 x86_64 Alert Count 3 First Seen 2013-05-07 07:27:08 CDT Last Seen 2013-05-07 07:42:08 CDT Local ID d2191a11-cb90-48ef-b127-f02bddd9bc1c Raw Audit Messages type=AVC msg=audit(1367930528.669:340): avc: denied { sys_ptrace } for pid=2443 comm="ps" capability=19 scontext=system_u:system_r:ksmtuned_t:s0 tcontext=system_u:system_r:ksmtuned_t:s0 tclass=capability type=SYSCALL msg=audit(1367930528.669:340): arch=x86_64 syscall=read success=yes exit=226 a0=6 a1=367f811d20 a2=fff a3=4 items=0 ppid=2442 pid=2443 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=ps exe=/usr/bin/ps subj=system_u:system_r:ksmtuned_t:s0 key=(null) Hash: ps,ksmtuned_t,ksmtuned_t,capability,sys_ptrace audit2allowunable to open /sys/fs/selinux/policy: Permission denied audit2allow -Runable to open /sys/fs/selinux/policy: Permission denied Additional info: hashmarkername: setroubleshoot kernel: 3.2.44 type: libreport Potential duplicate: bug 800348
This is allowed in F19.
also back ported to f18 branch. [f18-contrib 6ae7c5b] Allow sys_ptrace in ksmtuned policy 1 file changed, 1 insertion(+), 1 deletion(-)
selinux-policy-3.11.1-108.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-108.fc18
Package selinux-policy-3.11.1-108.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-108.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23716/selinux-policy-3.11.1-108.fc18 then log in and leave karma (feedback).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
selinux-policy-3.11.1-108.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.