Hide Forgot
Description of problem: SELinux is preventing /usr/bin/systemctl from 'write' accesses on the chr_file kmsg. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemctl should be allowed write access on the kmsg chr_file 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 systemctl /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:logrotate_t:s0-s0:c0.c1023 Target Context system_u:object_r:kmsg_device_t:s0 Target Objects kmsg [ chr_file ] Source systemctl Source Path /usr/bin/systemctl Port <Unknown> Host (removed) Source RPM Packages systemd-222-8.fc23.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-155.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.2.5-300.fc23.x86_64 #1 SMP Tue Oct 27 04:29:56 UTC 2015 x86_64 x86_64 Alert Count 7 First Seen 2015-11-22 03:44:01 EST Last Seen 2016-01-04 03:28:01 EST Local ID bfb3b4fe-ad00-4a1d-9288-2d06d3b7c06e Raw Audit Messages type=AVC msg=audit(1451896081.607:151571): avc: denied { write } for pid=8524 comm="systemctl" name="kmsg" dev="devtmpfs" ino=1042 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file permissive=0 type=SYSCALL msg=audit(1451896081.607:151571): arch=x86_64 syscall=open success=no exit=EACCES a0=56073d55a544 a1=80101 a2=0 a3=7f802673fb98 items=0 ppid=8523 pid=8524 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemctl exe=/usr/bin/systemctl subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) Hash: systemctl,logrotate_t,kmsg_device_t,chr_file,write Version-Release number of selected component: selinux-policy-3.13.1-155.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.5-300.fc23.x86_64 type: libreport
SELinux is preventing /usr/bin/systemctl from 'write' accesses on the chr_file kmsg. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemctl should be allowed write access on the kmsg chr_file 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 systemctl /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:logrotate_t:s0-s0:c0.c1023 Target Context system_u:object_r:kmsg_device_t:s0 Target Objects kmsg [ chr_file ] Source systemctl Source Path /usr/bin/systemctl Port <Unknown> Host (removed) Source RPM Packages systemd-219-19.el7.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-60.el7.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.0-327.4.5.el7.x86_64 #1 SMP Mon Jan 25 22:07:14 UTC 2016 x86_64 x86_64 Alert Count 2 First Seen 2016-02-08 08:07:58 GST Last Seen 2016-02-16 13:44:05 GST Local ID eede6187-5c30-4ca5-9a02-886ac37b9600 Raw Audit Messages type=AVC msg=audit(1455615845.368:617): avc: denied { write } for pid=5365 comm="systemctl" name="kmsg" dev="devtmpfs" ino=5759 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:kmsg_device_t:s0 tclass=chr_file type=SYSCALL msg=audit(1455615845.368:617): arch=x86_64 syscall=open success=no exit=EACCES a0=7f5f761ec38b a1=80101 a2=ffffffff a3=7f5f752467b8 items=0 ppid=5364 pid=5365 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm=systemctl exe=/usr/bin/systemctl subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) Hash: systemctl,logrotate_t,kmsg_device_t,chr_file,write
*** Bug 1372755 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.