Hide Forgot
Description of problem: SELinux is preventing /usr/bin/timeout from using the 'setpgid' accesses on a process. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that timeout should be allowed setpgid access on processes labeled sosreport_t 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 timeout /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:sosreport_t:s0-s0:c0.c1023 Target Context system_u:system_r:sosreport_t:s0-s0:c0.c1023 Target Objects [ process ] Source timeout Source Path /usr/bin/timeout Port <Unknown> Host (removed) Source RPM Packages coreutils-8.21-14.el7.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-105.el7.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.0-54.el7.x86_64 #1 SMP Thu Nov 21 15:34:15 EST 2013 x86_64 x86_64 Alert Count 60 First Seen 2013-12-02 08:34:18 MST Last Seen 2013-12-02 08:35:59 MST Local ID f766544e-54f0-46dc-b761-3ef5554a8c46 Raw Audit Messages type=AVC msg=audit(1385998559.717:17638): avc: denied { setpgid } for pid=28815 comm="timeout" scontext=system_u:system_r:sosreport_t:s0-s0:c0.c1023 tcontext=system_u:system_r:sosreport_t:s0-s0:c0.c1023 tclass=process type=SYSCALL msg=audit(1385998559.717:17638): arch=x86_64 syscall=setpgid success=no exit=EACCES a0=0 a1=0 a2=7fff38368eb3 a3=7fff38366f90 items=0 ppid=27620 pid=28815 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=timeout exe=/usr/bin/timeout subj=system_u:system_r:sosreport_t:s0-s0:c0.c1023 key=(null) Hash: timeout,sosreport_t,sosreport_t,process,setpgid Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.10.0-54.el7.x86_64 type: libreport
I believe this bug is a duplicate of bz#1035779.
*** This bug has been marked as a duplicate of bug 1035779 ***
Hi, I cannot view the details of this bug, but can someone share what was the fix for this? I'm seeing similar issue on my system as well.