Hide Forgot
Description of problem: SELinux is preventing /usr/lib/systemd/systemd-journald from 'setattr' accesses on the soubor labeled unlabeled_t. ***** Plugin catchall (100. confidence) suggests ************************** Pokud jste přesvědčeni, že má systemd-journald mít ve výchozím stavu přístup setattr na (null) file. Then toto byste měli nahlásit jako chybu. Abyste přístup povolili, můžete vygenerovat lokální modul pravidel. Do prozatím tento přístup povolíte příkazy: # 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:object_r:unlabeled_t:s0 Target Objects (null) [ file ] Source systemd-journal Source Path /usr/lib/systemd/systemd-journald Port <Neznámé> Host (removed) Source RPM Packages systemd-234-10.git5f8984e.fc27.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-283.30.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.15.17-300.fc27.x86_64 #1 SMP Thu Apr 12 18:19:17 UTC 2018 x86_64 x86_64 Alert Count 1 First Seen 2018-04-26 21:15:03 CEST Last Seen 2018-04-26 21:15:03 CEST Local ID 39aa9d2e-1108-4fb2-9a96-cc7df09022ea Raw Audit Messages type=AVC msg=audit(1524770103.857:339): avc: denied { setattr } for pid=470 comm="systemd-journal" name="user-1000.journal" dev="nvme0n1p4" ino=2510530 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 type=SYSCALL msg=audit(1524770103.857:339): arch=x86_64 syscall=fsetxattr success=yes exit=0 a0=22 a1=7f4afe57feeb a2=55e0f46e7e20 a3=2c items=1 ppid=1 pid=470 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=PATH msg=audit(1524770103.857:339): item=0 name=(null) inode=2510530 dev=00:2a mode=0100640 ouid=0 ogid=190 rdev=00:00 obj=system_u:object_r:unlabeled_t:s0 nametype=NORMAL cap_fp=0000000000000000 cap_fi=0000000000000000 cap_fe=0 cap_fver=0 Hash: systemd-journal,syslogd_t,unlabeled_t,file,setattr Version-Release number of selected component: selinux-policy-3.13.1-283.30.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.17-300.fc27.x86_64 type: libreport Potential duplicate: bug 1490295
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.