Command: /usr/local/sbin/syslog-digest.py Time : 0.5372s Status : exited 0 Output : Syslog digest — 2026-08-05 18:05 EDT Processed 5,060 lines, filtered 4,127 (81%). 933 unknown (127 distinct) from 29 host(s). == abadi-computer (7 distinct, 10 total) == Aug 5 17:23:04 abadi-computer kernel: kauditd_printk_skb: 431 callbacks suppressed Aug 5 17:23:09 abadi-computer kernel: kauditd_printk_skb: 152 callbacks suppressed Aug 5 17:23:14 abadi-computer kernel: kauditd_printk_skb: 71 callbacks suppressed Aug 5 17:23:19 abadi-computer kernel: kauditd_printk_skb: 143 callbacks suppressed Aug 5 17:23:24 abadi-computer kernel: kauditd_printk_skb: 41 callbacks suppressed Aug 5 17:23:33 abadi-computer kernel: kauditd_printk_skb: 17 callbacks suppressed Aug 5 17:26:50 abadi-computer kernel: kauditd_printk_skb: 1 callbacks suppressed [x4] == abuse (1 distinct, 346 total) == Aug 5 17:05:06 abuse rsyslogd[21745]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x346] == b0b02.cs.umd.edu (1 distinct, 1 total) == Aug 5 17:46:45 b0b02.cs.umd.edu rustdesk[3295131]: cannot open display: == cheezit.cs.umd.edu (3 distinct, 4 total) == Aug 5 17:08:25 cheezit.cs.umd.edu krb5_child[1404779]: Preauthentication failed Aug 5 17:08:25 cheezit.cs.umd.edu sshd-session[1404748]: error: PAM: Authentication failure for bahar from 10.174.218.172 Aug 5 17:51:23 cheezit.cs.umd.edu sshd-session[1415859]: error: send_error: write: Connection reset by peer [x2] == contest (9 distinct, 45 total) == Aug 5 17:05:28 contest goferd[1007]: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://satellite8.cs.umd.edu:5647, failed: Connection amqps://satellite8.cs.umd.edu:5647 disconnected: Condition('proton.pythonio', 'Connection refused to all addresses') [x34] Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the directory libdnf.M4msgA. For complete SELinux messages run: sealert -l cb6b25c6-4765-4cf2-88a0-9b3b508e94e9 Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/bin/gpgconf from add_name access on the directory repodata. For complete SELinux messages run: sealert -l 41cf7b1b-0f34-4609-98f2-b66e7825fef7 Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from create access on the file mirrorlist. For complete SELinux messages run: sealert -l fc20ff92-ea83-4f38-a24b-ddfd737a3141 Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l ac675631-fa35-4e93-adc9-b692b18e53e5 Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.M4msgA. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 Aug 5 17:48:18 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 7e499113-2fd7-4f67-bec6-3521efbe3637 [x3] Aug 5 17:48:19 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3928930b-a1ed-448d-950b-0665ac2adef8 [x2] Aug 5 17:48:20 contest setroubleshoot[683815]: SELinux is preventing /usr/libexec/platform-python3.6 from read access on the directory libdnf.KFSrsW. For complete SELinux messages run: sealert -l 45d103b6-0810-4890-a705-990118577ce8 == csfw00a (1 distinct, 310 total) == Aug 5 17:04:25 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x310] == frabjous (3 distinct, 3 total) == Aug 5 17:51:48 frabjous krb5_child[3256498]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 5 17:51:50 frabjous sshd-session[3256437]: error: PAM: Authentication failure for admin from 116.99.171.102 Aug 5 17:54:58 frabjous sshd-session[3256793]: error: PAM: Authentication failure for root from 116.99.171.102 == frozone (1 distinct, 1 total) == Aug 5 17:34:50 frozone systemd-tmpfiles[1594346]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == hackerman (7 distinct, 12 total) == Aug 5 17:19:01 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.CVB0T3”: Permission denied Aug 5 17:20:04 hackerman gnome-software[2060381]: can't reliably fixup error code 4 in domain g-io-error-quark: Not a directory [x4] Aug 5 17:20:12 hackerman gnome-software[2060381]: Only 0 apps for recent list, hiding Aug 5 17:20:28 hackerman gnome-software[2060381]: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Failed to create file “/adminhomes/sajith/.config/dconf/user.DI0GT3”: Permission denied Aug 5 17:20:28 hackerman packagekitd[4187151]: Failed to get cache filename for libreoffice [x2] Aug 5 17:20:28 hackerman packagekitd[4187151]: Failed to get cache filename for kernel [x2] Aug 5 17:20:39 hackerman packagekitd[4187151]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release == idm00 (1 distinct, 1 total) == Aug 5 17:51:17 idm00 named[1455]: client @0x7f330432bc58 10.73.240.42#64471: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Aug 5 17:36:06 idmp0 named[5198]: client @0x7f9910009828 10.73.240.43#55719: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 3 total) == Aug 5 17:53:10 inbound00.cs.umd.edu krb5_child[3279525]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 5 17:59:03 inbound00.cs.umd.edu cockpit-ws[3281396]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2] == inbound01.cs.umd.edu (1 distinct, 2 total) == Aug 5 17:58:57 inbound01.cs.umd.edu cockpit-ws[1295251]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2] == itmon02 (1 distinct, 36 total) == Aug 5 17:07:48 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x36] == krispykreme.cs.umd.edu (5 distinct, 5 total) == Aug 5 17:53:18 krispykreme.cs.umd.edu sshd-session[3695180]: pam_access(sshd:auth): access denied for user `admin' from `116.99.171.102' Aug 5 17:53:19 krispykreme.cs.umd.edu krb5_child[3695182]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 5 17:53:19 krispykreme.cs.umd.edu sshd-session[3695133]: error: PAM: System error for admin from 116.99.171.102 Aug 5 17:56:20 krispykreme.cs.umd.edu sshd-session[3696697]: pam_access(sshd:auth): access denied for user `root' from `116.99.171.102' Aug 5 17:56:23 krispykreme.cs.umd.edu sshd-session[3696662]: error: PAM: Authentication failure for root from 116.99.171.102 == neodontcare.cs.umd.edu (4 distinct, 25 total) == Aug 5 17:16:17 neodontcare.cs.umd.edu tracker-extract[2674983]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed [x16] Aug 5 17:27:43 neodontcare.cs.umd.edu tracker-miner-f[2945379]: g_hash_table_contains: assertion 'hash_table != NULL' failed [x3] Aug 5 17:27:43 neodontcare.cs.umd.edu tracker-extract[2679081]: Could not get mimetype, Error when getting information for file “/fs/junkfood/gasarch/4913”: No such file or directory [x3] Aug 5 17:27:43 neodontcare.cs.umd.edu tracker-extract[2679081]: Task for 'file:///fs/junkfood/gasarch/4913' finished with error: Error when getting information for file “/fs/junkfood/gasarch/4913”: No such file or directory [x3] == newhonors2 (1 distinct, 24 total) == Aug 5 17:13:03 newhonors2 dhcpcd[780721]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (3 distinct, 10 total) == Aug 5 17:09:09 outbound00.cs.umd.edu python3[3221881]: ldapdb [x6] Aug 5 17:53:11 outbound00.cs.umd.edu krb5_child[3231683]: Client 'admin@UMD.EDU' not found in Kerberos database Aug 5 17:56:22 outbound00.cs.umd.edu cockpit-ws[3233026]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3] == outbound01.cs.umd.edu (2 distinct, 7 total) == Aug 5 17:13:06 outbound01.cs.umd.edu python3[1256097]: ldapdb [x6] Aug 5 17:56:26 outbound01.cs.umd.edu cockpit-ws[1266678]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory == sebatinsky.cs.umd.edu (1 distinct, 2 total) == Aug 5 17:50:34 sebatinsky.cs.umd.edu setroubleshoot[1758138]: SELinux is preventing /usr/libexec/platform-python3.6 from add_name access on the directory __db.001. For complete SELinux messages run: sealert -l 26d5bc02-bfff-4827-a9f2-b991fef962b5 [x2] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559510]: link_config: could not get ethtool features for veth3ad4ea8 Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559510]: Could not set offload features of veth3ad4ea8: No such device Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559538]: Could not generate persistent MAC address for vethde5c209: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559539]: Could not generate persistent MAC address for veth81957b7: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559542]: Could not generate persistent MAC address for veth98421b1: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559543]: Could not generate persistent MAC address for vethf597eea: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559566]: Could not generate persistent MAC address for vethe8eba51: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559567]: Could not generate persistent MAC address for veth452fc5c: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559585]: Could not generate persistent MAC address for veth0f53b3a: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559581]: Could not generate persistent MAC address for veth9d12d2f: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559683]: Could not generate persistent MAC address for veth9f677ed: No such file or directory Aug 5 17:22:37 sentry-docker00.cs.umd.edu systemd-udevd[2559689]: Could not generate persistent MAC address for vethedbfc31: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568876]: link_config: could not get ethtool features for veth0f53b3a Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568876]: Could not set offload features of veth0f53b3a: No such device Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568962]: Could not generate persistent MAC address for veth227e2cb: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568963]: Could not generate persistent MAC address for veth73dbe0a: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568966]: Could not generate persistent MAC address for vethfc4692e: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568967]: Could not generate persistent MAC address for veth9d64829: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568990]: Could not generate persistent MAC address for vethdecf139: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568991]: Could not generate persistent MAC address for veth8e5c500: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2569013]: Could not generate persistent MAC address for veth1877fe7: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2569009]: Could not generate persistent MAC address for vethc122b85: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2569005]: Could not generate persistent MAC address for veth435f60a: No such file or directory Aug 5 17:42:45 sentry-docker00.cs.umd.edu systemd-udevd[2568999]: Could not generate persistent MAC address for veth9045fc0: No such file or directory Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578285]: link_config: could not get ethtool features for veth227e2cb Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578285]: Could not set offload features of veth227e2cb: No such device Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578321]: link_config: could not get ethtool features for vethfc4692e Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578321]: Could not set offload features of vethfc4692e: No such device Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578356]: Could not generate persistent MAC address for vethc05fd74: No such file or directory Aug 5 18:02:53 sentry-docker00.cs.umd.edu systemd-udevd[2578357]: Could not generate persistent MAC address for veth14495a0: No such file or directory ... 8 more distinct messages not shown == soul (1 distinct, 1 total) == Aug 5 17:52:21 soul krb5_child[3780678]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (2 distinct, 8 total) == Aug 5 17:09:44 strawberry udisksd[1067]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_W1E8J5KJ: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) [x6] Aug 5 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-2 (9 distinct, 9 total) == Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l d506243c-d61e-48f3-b42a-4592c913deb0 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3b4752ac-1b9a-4af9-a05b-32e4c2eb13ab Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 29e5adbd-4381-4467-b40d-a2219101e096 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Fr3yQp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 1b38f2ec-01ce-4343-8059-ba7494ecc5c4 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e5f9af40-1f63-4924-b012-27ab2a7b2266 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Fr3yQp. For complete SELinux messages run: sealert -l 5c54db87-54a3-4a7c-97b4-b5c48d6c3543 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 63cd60e1-1e61-4276-afea-dd8526ffe8b2 Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 81c7e9ec-e023-4c6d-b1ad-c02a242e655e Aug 5 17:12:53 submit26-b9-2 setroubleshoot[1106766]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 6ae9a597-e123-4d74-8eec-a8ebe0f5e4d0 == submit26-b9-3 (9 distinct, 9 total) == Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 5b912a44-22fd-4560-b201-2a4e289b73f5 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 7f1df1e4-725e-4953-98eb-1079f908f543 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 40b8852a-f77b-44b4-affe-5f11fa33de43 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.fgE1ka/repodata/repomd.xml. For complete SELinux messages run: sealert -l 45a8019e-f6b5-4baa-92c1-862594b40d46 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l e9f0bfff-7784-4126-baa4-2bb06da56591 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.fgE1ka. For complete SELinux messages run: sealert -l 0b17cc3d-cdc6-4fe2-a11f-3892e7c41dc7 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 10e38c64-b65f-4cdd-901e-4375652d9a42 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 7fd9cf72-ef38-48e1-b6aa-b571b26a7b22 Aug 5 17:20:39 submit26-b9-3 setroubleshoot[859427]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l b9b11116-89bd-4a3c-980c-1d422c5dcee4 == submit26-b9-4 (1 distinct, 3 total) == Aug 5 17:15:33 submit26-b9-4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-clnb9 (10 distinct, 14 total) == Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 6783ed2b-5ae4-42b5-975a-4bf50eec4658 [x2] Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 9e7fa955-cc30-4804-ac8c-e1779e85946c [x2] Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 69bfa6e3-089c-40ff-9563-fd30787d0774 Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Xtd6Li/repodata/repomd.xml. For complete SELinux messages run: sealert -l 001acdb5-31ef-4e52-b10b-90f467a89ddc Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l edacddcf-16ed-4dc3-8d82-7c597d5dee23 Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Xtd6Li. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 81cb3698-78f8-440a-8e3c-e5d1041e6b78 [x2] Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 792b472a-115c-4799-9805-fc7436f916b9 Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 15c83a86-837b-41e2-b662-b39cd4e361cb [x2] Aug 5 17:31:58 submit26-clnb9 setroubleshoot[1843172]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ETt9u2. For complete SELinux messages run: sealert -l 62b3782e-4730-4488-8178-94dafe9b552c == talkhosts9 (1 distinct, 2 total) == Aug 5 17:09:07 talkhosts9 setroubleshoot[1497722]: SELinux is preventing /usr/bin/lsof from getattr access on the unix_stream_socket unix_stream_socket. For complete SELinux messages run: sealert -l a6df89b3-c497-469c-8232-c4fde0508abf [x2] == unknown (1 distinct, 1 total) == using-explainable-ai