Bug 2273673
| Summary: | SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Machine. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sebastian Hörberg <sebastian.horberg> | ||||||
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 40 | CC: | dwalsh, knazekovan, lvrabec, mmalik, omosnacek, pkoncity, sebastian.horberg, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:a7ebe5d62b0552fb1babfb9e9dd46c66bd6c593d689d4b22430b107e5de7fd53;VARIANT_ID=kde; | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2024-04-05 19:28:02 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 2025430 [details]
File: description
Created attachment 2025431 [details]
File: os_info
*** This bug has been marked as a duplicate of bug 2265927 *** |
Description of problem: Not sure, it keeps popping up from time to time. SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Machine. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that abrt-dump-journ should be allowed write access on the io.systemd.Machine sock_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: # ausearch -c 'abrt-dump-journ' --raw | audit2allow -M my-abrtdumpjourn # semodule -X 300 -i my-abrtdumpjourn.pp Additional Information: Source Context system_u:system_r:abrt_dump_oops_t:s0 Target Context system_u:object_r:systemd_userdbd_runtime_t:s0 Target Objects io.systemd.Machine [ sock_file ] Source abrt-dump-journ Source Path abrt-dump-journ Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.15-1.fc40.noarch Local Policy RPM selinux-policy-targeted-40.15-1.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.8.4-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 4 20:41:39 UTC 2024 x86_64 Alert Count 62 First Seen 2024-04-04 16:09:44 CEST Last Seen 2024-04-05 16:03:35 CEST Local ID 014862d4-08c2-4d11-9753-7b90f725c115 Raw Audit Messages type=AVC msg=audit(1712325815.230:1691): avc: denied { write } for pid=1234 comm="abrt-dump-journ" name="io.systemd.Machine" dev="tmpfs" ino=2362 scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:object_r:systemd_userdbd_runtime_t:s0 tclass=sock_file permissive=0 Hash: abrt-dump-journ,abrt_dump_oops_t,systemd_userdbd_runtime_t,sock_file,write Version-Release number of selected component: selinux-policy-targeted-40.15-1.fc40.noarch Additional info: reporter: libreport-2.17.15 reason: SELinux is preventing abrt-dump-journ from 'write' accesses on the sock_file io.systemd.Machine. package: selinux-policy-targeted-40.15-1.fc40.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.8.4-300.fc40.x86_64 comment: Not sure, it keeps popping up from time to time. component: selinux-policy