Command: /usr/local/sbin/syslog-digest.py Time : 0.0545s Status : exited 0 Output : Syslog digest — 2026-09-21 23:05 EDT Processed 2,495 lines, filtered 1,888 (75%). 607 unknown (260 distinct) from 26 host(s). == abadi-computer (62 distinct, 62 total) == Sep 21 22:05:39 abadi-computer kernel: gsd-housekeepin invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 Sep 21 22:05:39 abadi-computer kernel: CPU: 1 UID: 120 PID: 2148 Comm: gsd-housekeepin Not tainted 6.17.0-35-generic #35~24.04.1-Ubuntu PREEMPT(voluntary) Sep 21 22:05:39 abadi-computer kernel: Hardware name: Dell Inc. Precision T3600/08HPGT, BIOS A09 05/03/2013 Sep 21 22:05:39 abadi-computer kernel: Call Trace: Sep 21 22:05:39 abadi-computer kernel: <TASK> Sep 21 22:05:39 abadi-computer kernel: dump_stack_lvl+0x76/0xa0 Sep 21 22:05:39 abadi-computer kernel: dump_stack+0x10/0x20 Sep 21 22:05:39 abadi-computer kernel: dump_header+0x48/0x210 Sep 21 22:05:39 abadi-computer kernel: oom_kill_process+0x118/0x290 Sep 21 22:05:39 abadi-computer kernel: ? oom_evaluate_task+0x15c/0x210 Sep 21 22:05:39 abadi-computer kernel: out_of_memory+0x101/0x340 Sep 21 22:05:39 abadi-computer kernel: __alloc_pages_may_oom+0x109/0x1d0 Sep 21 22:05:39 abadi-computer kernel: __alloc_pages_slowpath.constprop.0+0x623/0x9f0 Sep 21 22:05:39 abadi-computer kernel: ? get_page_from_freelist+0x4be/0x6d0 Sep 21 22:05:39 abadi-computer kernel: __alloc_frozen_pages_noprof+0x347/0x360 Sep 21 22:05:39 abadi-computer kernel: alloc_pages_mpol+0x7e/0x1a0 Sep 21 22:05:39 abadi-computer kernel: folio_alloc_noprof+0x65/0xf0 Sep 21 22:05:39 abadi-computer kernel: filemap_alloc_folio_noprof+0x102/0x110 Sep 21 22:05:39 abadi-computer kernel: __filemap_get_folio+0x1f2/0x340 Sep 21 22:05:39 abadi-computer kernel: filemap_fault+0x10c/0xd50 Sep 21 22:05:39 abadi-computer kernel: __do_fault+0x3d/0x190 Sep 21 22:05:39 abadi-computer kernel: do_read_fault+0x12e/0x230 Sep 21 22:05:39 abadi-computer kernel: do_fault+0x167/0x280 Sep 21 22:05:39 abadi-computer kernel: handle_pte_fault+0x15e/0x200 Sep 21 22:05:39 abadi-computer kernel: __handle_mm_fault+0x5ba/0x740 Sep 21 22:05:39 abadi-computer kernel: handle_mm_fault+0x120/0x370 Sep 21 22:05:39 abadi-computer kernel: do_user_addr_fault+0x1d2/0x8d0 Sep 21 22:05:39 abadi-computer kernel: exc_page_fault+0x7f/0x1b0 Sep 21 22:05:39 abadi-computer kernel: asm_exc_page_fault+0x27/0x30 Sep 21 22:05:39 abadi-computer kernel: RIP: 0033:0x79718a26c139 ... 32 more distinct messages not shown == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 22:54:31 b0b02.cs.umd.edu rustdesk[3780088]: cannot open display: == bale (5 distinct, 88 total) == Sep 21 22:05:10 bale setroubleshoot[1601279]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 21 22:05:10 bale setroubleshoot[1601279]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12] Sep 21 22:05:13 bale setroubleshoot[1601279]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 21 22:05:16 bale setroubleshoot[1601279]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12] Sep 21 22:05:28 bale setroubleshoot[1601895]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x14] == csfw00a (1 distinct, 125 total) == Sep 21 22:03:47 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125] == gle-dind04 (1 distinct, 1 total) == Sep 21 23:01:21 gle-dind04 lldpd[1171]: unable to send packet on real device for veth39773c1: No such device or address == idm00 (1 distinct, 1 total) == Sep 21 22:54:03 idm00 named[4166701]: client @0x7f11a00475a8 10.73.240.42#53383: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 22:37:55 idmp0 named[1598691]: client @0x7f2d5002a688 10.73.240.43#61735: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Sep 21 22:27:07 inbound00.cs.umd.edu krb5_child[2653081]: Client 'admin@UMD.EDU' not found in Kerberos database == inbound01.cs.umd.edu (1 distinct, 1 total) == Sep 21 22:42:53 inbound01.cs.umd.edu krb5_child[680223]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 3 total) == Sep 21 22:18:19 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (5 distinct, 5 total) == Sep 21 22:11:40 krispykreme.cs.umd.edu sshd-session[877961]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214' Sep 21 22:11:40 krispykreme.cs.umd.edu krb5_child[877963]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 21 22:11:40 krispykreme.cs.umd.edu sshd-session[877959]: error: PAM: System error for admin from 193.187.110.214 Sep 21 22:54:25 krispykreme.cs.umd.edu sshd-session[889241]: pam_access(sshd:auth): access denied for user `root' from `193.187.110.214' Sep 21 22:54:27 krispykreme.cs.umd.edu sshd-session[889239]: error: PAM: Authentication failure for root from 193.187.110.214 == matrix (3 distinct, 4 total) == Sep 21 22:14:07 matrix krb5_child[164437]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 21 22:14:09 matrix sshd[164431]: error: PAM: Authentication failure for admin from 193.187.110.214 Sep 21 22:56:42 matrix sshd[189236]: error: PAM: Authentication failure for root from 193.187.110.214 == mcstic (3 distinct, 6 total) == Sep 21 22:30:27 mcstic krb5_child[927488]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 21 22:30:33 mcstic sshd[927483]: error: PAM: Authentication failure for admin from 34.22.208.38 Sep 21 22:35:57 mcstic sshd[927740]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 12 total) == Sep 21 22:18:34 munin sudo[1533143]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 21 22:18:34 munin sudo[1533143]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 21 23:00:01 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. == newhonors2 (1 distinct, 24 total) == Sep 21 22:13:02 newhonors2 dhcpcd[2968339]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 21 22:05:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 5851/5851, ET: 30) *** Sep 21 22:05:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 51/51, ET: 30) *** Sep 21 22:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 21 22:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5557/5557, ET: 0) *** Sep 21 22:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 21 22:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 60/60, ET: 0) *** Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12] Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12] Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 22:08:03 ntop00 setroubleshoot[1096537]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12] Sep 21 22:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 21 22:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 21 22:10:28 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5542/5542, ET: 27) *** Sep 21 22:10:28 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 51/51, ET: 27) *** Sep 21 22:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 21 22:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 55/55, ET: 0) *** Sep 21 22:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 21 22:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 5631/5631, ET: 0) *** Sep 21 22:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 21 22:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 21 22:15:29 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 5657/5657, ET: 28) *** Sep 21 22:15:29 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 60/60, ET: 28) *** Sep 21 22:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 21 22:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5656/5656, ET: 0) *** Sep 21 22:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 21 22:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 62/62, ET: 0) *** Sep 21 22:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 21 22:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 21 22:20:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 5872/5872, ET: 30) *** Sep 21 22:20:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 67/67, ET: 30) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 22:09:09 outbound00.cs.umd.edu python3[2512548]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 21 22:13:06 outbound01.cs.umd.edu python3[579870]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074300]: link_config: could not get ethtool features for vethcc9e33b Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074300]: Could not set offload features of vethcc9e33b: No such device Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074334]: Could not generate persistent MAC address for veth1a8e129: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074335]: Could not generate persistent MAC address for veth6eb2921: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074338]: Could not generate persistent MAC address for vethee3da76: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074339]: Could not generate persistent MAC address for vethcbf5ccd: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074362]: Could not generate persistent MAC address for vethafa6d9c: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074363]: Could not generate persistent MAC address for veth3b336e6: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074381]: Could not generate persistent MAC address for veth72a673e: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074388]: Could not generate persistent MAC address for veth10db9e3: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074390]: Could not generate persistent MAC address for vethffcfbb7: No such file or directory Sep 21 22:11:18 sentry-docker00.cs.umd.edu systemd-udevd[1074392]: Could not generate persistent MAC address for veth4000969: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083694]: link_config: could not get ethtool features for vethafa6d9c Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083694]: Could not set offload features of vethafa6d9c: No such device Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083781]: Could not generate persistent MAC address for veth435ee5d: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083782]: Could not generate persistent MAC address for veth77255ad: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083782]: Could not generate persistent MAC address for veth5e4506a: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083795]: Could not generate persistent MAC address for veth37811c0: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083827]: Could not generate persistent MAC address for vethe36577f: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083829]: Could not generate persistent MAC address for veth06ac276: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083855]: Could not generate persistent MAC address for veth3e15713: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083842]: Could not generate persistent MAC address for vethb2da7be: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083840]: Could not generate persistent MAC address for veth85202fd: No such file or directory Sep 21 22:31:26 sentry-docker00.cs.umd.edu systemd-udevd[1083852]: Could not generate persistent MAC address for vethed493ce: No such file or directory Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093147]: link_config: could not get ethtool features for vethed493ce Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093147]: Could not set offload features of vethed493ce: No such device Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093177]: Could not generate persistent MAC address for veth9e4bf9b: No such file or directory Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093178]: Could not generate persistent MAC address for vethd2bc272: No such file or directory Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093181]: Could not generate persistent MAC address for veth32afc0f: No such file or directory Sep 21 22:51:34 sentry-docker00.cs.umd.edu systemd-udevd[1093182]: Could not generate persistent MAC address for veth1510200: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 16 total) == Sep 21 22:10:56 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DxVicq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.DxVicq. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 21 22:25:54 submit26-b9-f1 setroubleshoot[2827593]: 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 (10 distinct, 12 total) == Sep 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OGAHug/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 21 22:06:49 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OGAHug. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 21 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 21 22:06:50 submit26-b9-f2 setroubleshoot[1933624]: 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 Sep 21 22:15:21 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (1 distinct, 8 total) == Sep 21 22:16:19 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f4 (1 distinct, 2 total) == Sep 21 22:19:12 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 21 22:11:57 vacuum.cs.umd.edu abrt-hook-ccpp[13500]: Process 9066 (driver) of user 33 killed by SIGABRT - dumping core Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: Package 'amanda-backup_server' isn't signed with proper key Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-21-22:11:57-9066' exited with 1 Sep 21 22:11:58 vacuum.cs.umd.edu abrt-server[13502]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-21-22:11:57-9066'