Hide Forgot
Description of problem: SELinux is preventing /usr/lib/systemd/systemd-journald from 'sys_ptrace' accesses on the cap_userns /proc/<pid>/exe. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-journald should be allowed sys_ptrace access on the exe cap_userns 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: # ausearch -c 'systemd-journal' --raw | audit2allow -M my-systemdjournal # semodule -X 300 -i my-systemdjournal.pp Additional Information: Source Context system_u:system_r:syslogd_t:s0 Target Context system_u:system_r:syslogd_t:s0 Target Objects /proc/<pid>/exe [ cap_userns ] Source systemd-journal Source Path /usr/lib/systemd/systemd-journald Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.8.6-302.pf.skylake.fc25.x86_64 #1 SMP Sun Nov 6 00:48:09 UTC 2016 x86_64 x86_64 Alert Count 2247 First Seen 2016-10-23 21:33:07 EDT Last Seen 2016-11-30 12:49:28 EST Local ID acab02b0-e641-418e-acdc-326ec6db3f2c Raw Audit Messages type=AVC msg=audit(1480528168.264:476): avc: denied { sys_ptrace } for pid=768 comm="systemd-journal" capability=19 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:syslogd_t:s0 tclass=cap_userns permissive=0 type=SYSCALL msg=audit(1480528168.264:476): arch=x86_64 syscall=readlinkat success=no exit=EACCES a0=ffffff9c a1=7ffce6223620 a2=55828853af70 a3=63 items=1 ppid=1 pid=768 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-journal exe=/usr/lib/systemd/systemd-journald subj=system_u:system_r:syslogd_t:s0 key=(null) type=CWD msg=audit(1480528168.264:476): cwd=/ type=PATH msg=audit(1480528168.264:476): item=0 name=/proc/2460/exe inode=1667244 dev=00:04 mode=0120777 ouid=1000 ogid=1000 rdev=00:00 obj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 nametype=NORMAL Hash: systemd-journal,syslogd_t,syslogd_t,cap_userns,sys_ptrace Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.8.6-302.pf.skylake.fc25.x86_64 type: libreport Potential duplicate: bug 1374187
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.