Bug 2417813
| Summary: | SELinux is preventing blocking-2 from 'connectto' accesses on the unix_stream_socket /run/systemd/userdb/io.systemd.Machine. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard L. England <rlengland> | ||||||
| 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: | 43 | CC: | dwalsh, lvrabec, mmalik, omosnacek, pkoncity, rlengland, vmojzis, zpytela | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:04c486b7fbbbbdd115d516b5fb5da615b464bc4d3da931d34aa1ec559c1a0fce;VARIANT_ID=matecompiz; | ||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-12-03 16:36:06 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 2116647 [details]
File: description
Created attachment 2116648 [details]
File: os_info
*** This bug has been marked as a duplicate of bug 2408906 *** |
Description of problem: Sometime after an update/reboot this occurred. Could not track down what caused it to start. SELinux is preventing blocking-2 from 'connectto' accesses on the unix_stream_socket /run/systemd/userdb/io.systemd.Machine. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that blocking-2 should be allowed connectto access on the io.systemd.Machine unix_stream_socket 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 'blocking-2' --raw | audit2allow -M my-blocking2 # semodule -X 300 -i my-blocking2.pp Additional Information: Source Context unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 Target Context system_u:system_r:systemd_machined_t:s0 Target Objects /run/systemd/userdb/io.systemd.Machine [ unix_stream_socket ] Source blocking-2 Source Path blocking-2 Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-42.16-1.fc43.noarch Local Policy RPM selinux-policy-targeted-42.16-1.fc43.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.17.8-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 14 01:47:12 UTC 2025 x86_64 Alert Count 2 First Seen 2025-11-29 09:21:56 PST Last Seen 2025-11-29 09:21:56 PST Local ID 6800d84d-a3de-4f02-a0d2-5ca5a8ed4f09 Raw Audit Messages type=AVC msg=audit(1764436916.346:1833): avc: denied { connectto } for pid=657902 comm="blocking-2" path="/run/systemd/userdb/io.systemd.Machine" scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=system_u:system_r:systemd_machined_t:s0 tclass=unix_stream_socket permissive=0 Hash: blocking-2,thumb_t,systemd_machined_t,unix_stream_socket,connectto Version-Release number of selected component: selinux-policy-targeted-42.16-1.fc43.noarch Additional info: reporter: libreport-2.17.15 reason: SELinux is preventing blocking-2 from 'connectto' accesses on the unix_stream_socket /run/systemd/userdb/io.systemd.Machine. package: selinux-policy-targeted-42.16-1.fc43.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.17.8-300.fc43.x86_64 comment: Sometime after an update/reboot this occurred. Could not track down what caused it to start. component: selinux-policy