Command: /usr/local/sbin/syslog-digest.py Time : 7.5073s Status : exited 0 Output : Syslog digest — 2026-09-26 11:05 EDT Processed 120,387 lines, filtered 1,453 (1%). 118,934 unknown (203 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 11:01:25 b0b02.cs.umd.edu rustdesk[1309265]: cannot open display: == grosh (35 distinct, 41 total) == Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for claude-code Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-app-library Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-applets Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-epoch [x3] Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-files Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-greeter Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-initial-setup Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-launcher Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-monitor Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-notifications Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-osd Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-panel Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-randr Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-screenshot Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-session Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-settings Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-settings-daemon Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-term Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-workspaces Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for pop-launcher Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for xdg-desktop-portal-cosmic Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for libxml2 Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for python3-libxml2 Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-modules-extra-matched [x3] Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-tools Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-tools-libs Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for python3-cryptography Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-osk Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel [x3] Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-core ... 5 more distinct messages not shown == idm00 (3 distinct, 3 total) == Sep 26 10:40:57 idm00 named[4166701]: client @0x7f119806f9c8 10.73.245.14#56667: update '73.10.in-addr.arpa/IN' denied Sep 26 10:41:15 idm00 named[4166701]: client @0x7f1198541268 10.73.245.14#56667: update '73.10.in-addr.arpa/IN' denied Sep 26 10:54:09 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#57792: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 10:39:27 idmp0 named[1598691]: client @0x7f2d2c050c58 10.73.240.43#52523: update '73.10.in-addr.arpa/IN' denied == irb2156 (25 distinct, 25 total) == Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for firefox-nightly Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for claude-code Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-app-library Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-applets Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-epoch Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-files Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-greeter Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-initial-setup Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-launcher Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-monitor Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-notifications Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-osd Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-panel Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-randr Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-screenshot Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-session Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-settings Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-settings-daemon Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-term Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-workspaces Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for pop-launcher Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for xdg-desktop-portal-cosmic Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-osk Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for kernel Sep 26 11:00:01 irb2156 (da-udp.*)[1491165]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == itmon02 (1 distinct, 4 total) == Sep 26 10:43:37 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Sep 26 10:26:11 krispykreme.cs.umd.edu sshd-session[2802158]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.227.191' == lifepix (1 distinct, 1 total) == Sep 26 11:00:01 lifepix (da-udp.*)[270711]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == munin (2 distinct, 2 total) == Sep 26 10:09:04 munin sudo[3881020]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 26 10:09:04 munin sudo[3881020]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 26 10:13:02 newhonors2 dhcpcd[3180850]: dhcpcd is not running [x24] == ntop00 (70 distinct, 118728 total) == Sep 26 10:07:51 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7596] Sep 26 10:07:51 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56706] Sep 26 10:07:51 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53903] Sep 26 10:07:51 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x216] Sep 26 10:07:51 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x216] Sep 26 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 635) *** Sep 26 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 635, QN: 5547/5547, ET: 0) *** Sep 26 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 635) *** Sep 26 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 635, QN: 51/51, ET: 0) *** Sep 26 10:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 10:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6] Sep 26 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 636) *** Sep 26 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 636, QN: 0/5964, ET: 0) *** Sep 26 10:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 10:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6] Sep 26 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 636) *** Sep 26 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 636, QN: 0/49, ET: 0) *** Sep 26 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 637) *** Sep 26 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 637, QN: 5673/5673, ET: 0) *** Sep 26 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 637) *** Sep 26 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 637, QN: 49/49, ET: 0) *** Sep 26 10:14:02 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x7] Sep 26 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 639) *** Sep 26 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 639, QN: 5791/5791, ET: 0) *** Sep 26 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 639) *** Sep 26 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 639, QN: 50/50, ET: 0) *** Sep 26 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 640) *** Sep 26 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 640, QN: 0/6126, ET: 0) *** Sep 26 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 640) *** Sep 26 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 640, QN: 0/54, ET: 0) *** ... 40 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 10:09:09 outbound00.cs.umd.edu python3[4071116]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 10:13:06 outbound01.cs.umd.edu python3[2137977]: ldapdb [x6] == quiss (1 distinct, 1 total) == Sep 26 11:00:09 quiss (da-udp.*)[3029696]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149605]: link_config: could not get ethtool features for veth12bfe0d Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149605]: Could not set offload features of veth12bfe0d: No such device Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149621]: Could not generate persistent MAC address for veth8193ae8: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149622]: Could not generate persistent MAC address for veth2583be0: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149692]: Could not generate persistent MAC address for vethd06b0d6: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149693]: Could not generate persistent MAC address for veth232a67b: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149716]: Could not generate persistent MAC address for veth2d45e2b: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149709]: Could not generate persistent MAC address for veth77fa8e3: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149726]: Could not generate persistent MAC address for veth2c14be8: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149728]: Could not generate persistent MAC address for vethfe099da: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149744]: Could not generate persistent MAC address for vetha281b39: No such file or directory Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149728]: Could not generate persistent MAC address for veth17c87a9: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159084]: Could not generate persistent MAC address for veth57a4be3: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159085]: Could not generate persistent MAC address for veth03785a3: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159103]: Could not generate persistent MAC address for veth4f27a5e: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159109]: Could not generate persistent MAC address for veth70f7a51: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159112]: Could not generate persistent MAC address for veth8f63698: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159113]: Could not generate persistent MAC address for veth62a396a: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159131]: Could not generate persistent MAC address for veth0017044: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159136]: Could not generate persistent MAC address for veth77076c0: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159151]: Could not generate persistent MAC address for vethc281e78: No such file or directory Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159158]: Could not generate persistent MAC address for veth8fccd05: No such file or directory Sep 26 10:56:17 sentry-docker00.cs.umd.edu systemd-udevd[4168536]: link_config: could not get ethtool features for veth57a4be3 Sep 26 10:56:17 sentry-docker00.cs.umd.edu systemd-udevd[4168536]: Could not set offload features of veth57a4be3: No such device Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168573]: Could not generate persistent MAC address for vethb3d832d: No such file or directory Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168574]: Could not generate persistent MAC address for vethf7cd2a7: No such file or directory Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168577]: Could not generate persistent MAC address for vethc8b2c6b: No such file or directory Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168578]: Could not generate persistent MAC address for vethbc63730: No such file or directory Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168601]: Could not generate persistent MAC address for veth1f9bd8f: No such file or directory Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168602]: Could not generate persistent MAC address for veth202f6a5: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 10:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 26 10:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 26 10:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 10:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 26 10:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 26 10:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 10:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Aad9Fa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Aad9Fa. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 9 total) == Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.uKTlu8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.uKTlu8. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7