Command: /usr/local/sbin/syslog-digest.py Time : 0.0585s Status : exited 0 Output : Syslog digest — 2026-09-25 19:05 EDT Processed 4,076 lines, filtered 3,564 (87%). 512 unknown (280 distinct) from 22 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 25 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-25T22:10:59.431751632Z" level=info msg="PurgeUploads starting: olderThan=2026-09-18 22:10:59.431664415 +0000 UTC m=+4581420.191592730, actuallyDelete=true" Sep 25 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-25T22:10:59.432426362Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 25 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-25T22:10:59.432446453Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1 Sep 25 19:00:29 b0b02.cs.umd.edu rustdesk[1063065]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Sep 25 18:32:27 biggulp.cs.umd.edu sshd-session[35067]: pam_access(sshd:auth): access denied for user `egolub' from `108.28.255.142' == galax (4 distinct, 7 total) == Sep 25 18:13:09 galax systemd-sysv-generator[140853]: SysV service '/etc/init.d/openipmi' lacks a native systemd unit file, automatically generating a unit file for compatibility. [x2] Sep 25 18:13:09 galax systemd-sysv-generator[140853]: Please update package to include a native systemd unit file. [x2] Sep 25 18:13:09 galax systemd-sysv-generator[140853]: ! This compatibility logic is deprecated, expect removal soon. ! [x2] Sep 25 18:13:09 galax kernel: set_capacity_and_notify: 10 callbacks suppressed == gle-dind02.cs.umd.edu (84 distinct, 115 total) == Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: systemd invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: CPU: 2 PID: 1 Comm: systemd Kdump: loaded Tainted: G X -------- - - 4.18.0-553.162.1.el8_10.x86_64 #1 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: Call Trace: [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: dump_stack+0x41/0x60 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: dump_header+0x4a/0x1df [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: oom_kill_process.cold.33+0xb/0x10 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: out_of_memory+0x1bd/0x4e0 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __alloc_pages_slowpath+0xbf0/0xcd0 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __alloc_pages_nodemask+0x2e2/0x330 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: pagecache_get_page+0xe7/0x330 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: filemap_fault+0x6c8/0xa30 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? __mod_memcg_lruvec_state+0x4a/0xd0 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? __mod_lruvec_page_state+0x5e/0x80 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? page_add_file_rmap+0x99/0x150 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? alloc_set_pte+0xb6/0x420 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? xas_load+0x8/0x80 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? _cond_resched+0x15/0x30 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __xfs_filemap_fault+0x6d/0x200 [xfs] [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __do_fault+0x38/0xc0 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: handle_pte_fault+0x55d/0x880 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? ep_read_events_proc+0xe0/0xe0 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __handle_mm_fault+0x552/0x6d0 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: handle_mm_fault+0xca/0x2a0 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: __do_page_fault+0x1e4/0x440 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: do_page_fault+0x37/0x12d [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: ? page_fault+0x8/0x30 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: page_fault+0x1e/0x30 [x2] Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: RIP: 0033:0x564336f85fc0 Sep 25 18:08:36 gle-dind02.cs.umd.edu kernel: Code: Unable to access opcode bytes at RIP 0x564336f85f96. ... 54 more distinct messages not shown == idm00 (1 distinct, 1 total) == Sep 25 18:54:07 idm00 named[4166701]: client @0x7f11a00908a8 10.73.240.42#49895: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 18:39:29 idmp0 named[1598691]: client @0x7f2d304493e8 10.73.240.43#64616: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (3 distinct, 10 total) == Sep 25 18:13:14 inbound00.cs.umd.edu krb5_child[3993685]: Client 'admin@UMD.EDU' not found in Kerberos database [x6] Sep 25 18:20:34 inbound00.cs.umd.edu krb5_child[3995010]: Client 'backup@UMD.EDU' not found in Kerberos database [x2] Sep 25 18:36:13 inbound00.cs.umd.edu krb5_child[3999802]: Preauthentication failed [x2] == irb2156 (4 distinct, 4 total) == Sep 25 18:08:53 irb2156 systemd-tmpfiles[1406006]: Opening file "/tmp/.X11-unix/X1024" failed, proceeding without lock: No such device or address Sep 25 18:08:53 irb2156 systemd-tmpfiles[1406006]: Opening file "/tmp/.X11-unix/X1025" failed, proceeding without lock: No such device or address Sep 25 18:08:53 irb2156 systemd-tmpfiles[1406006]: Opening file "/tmp/.ICE-unix/4624" failed, proceeding without lock: No such device or address Sep 25 18:08:53 irb2156 systemd-tmpfiles[1406006]: Opening file "/tmp/tmux-12401/default" failed, proceeding without lock: No such device or address == itmon02 (1 distinct, 3 total) == Sep 25 18:33:53 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == mcstic (1 distinct, 2 total) == Sep 25 18:25:39 mcstic krb5_child[1117353]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == munin (2 distinct, 108 total) == Sep 25 18:08:07 munin sudo[3531642]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x54] Sep 25 18:08:07 munin sudo[3531642]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x54] == newhonors2 (1 distinct, 24 total) == Sep 25 18:13:03 newhonors2 dhcpcd[3149891]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 25 18:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) *** Sep 25 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) *** Sep 25 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 58/58, ET: 0) *** Sep 25 18:05:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 8207/8207, ET: 12) *** Sep 25 18:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 25 18:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 8666/8666, ET: 0) *** Sep 25 18:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 25 18:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 60/60, ET: 0) *** Sep 25 18:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 25 18:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 25 18:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 67/67, ET: 0) *** Sep 25 18:10:14 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 9019/9019, ET: 13) *** Sep 25 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 25 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 8064/8064, ET: 0) *** Sep 25 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 25 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 52/52, ET: 0) *** Sep 25 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 25 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 25 18:15:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 60/60, ET: 1) *** Sep 25 18:15:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 7407/7407, ET: 12) *** Sep 25 18:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 25 18:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 7208/7208, ET: 0) *** Sep 25 18:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 25 18:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 63/63, ET: 0) *** Sep 25 18:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 25 18:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 25 18:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 62/62, ET: 1) *** Sep 25 18:20:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 7518/7518, ET: 12) *** Sep 25 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 257) *** Sep 25 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 257) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 18:09:09 outbound00.cs.umd.edu python3[3844658]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 25 18:13:06 outbound01.cs.umd.edu python3[1910832]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 25 18:09:21 sentry-docker00.cs.umd.edu systemd-udevd[3693745]: link_config: could not set ethtool features for vethf242ed3 Sep 25 18:09:21 sentry-docker00.cs.umd.edu systemd-udevd[3693745]: Could not set offload features of vethf242ed3: Operation not permitted Sep 25 18:09:21 sentry-docker00.cs.umd.edu systemd-udevd[3693750]: link_config: could not get ethtool features for veth2371b5c Sep 25 18:09:21 sentry-docker00.cs.umd.edu systemd-udevd[3693750]: Could not set offload features of veth2371b5c: No such device Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693777]: Could not generate persistent MAC address for veth5e5731c: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693778]: Could not generate persistent MAC address for veth08b5bcd: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693781]: Could not generate persistent MAC address for vethcf0461f: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693782]: Could not generate persistent MAC address for veth44f33e4: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693792]: Could not generate persistent MAC address for veth9e551cc: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693798]: Could not generate persistent MAC address for vethf0f0ace: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693792]: Could not generate persistent MAC address for veth707cbf8: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693788]: Could not generate persistent MAC address for veth412d72d: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693788]: Could not generate persistent MAC address for veth609c9be: No such file or directory Sep 25 18:09:22 sentry-docker00.cs.umd.edu systemd-udevd[3693792]: Could not generate persistent MAC address for veth3a898bb: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703124]: link_config: could not get ethtool features for veth5e5731c Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703124]: Could not set offload features of veth5e5731c: No such device Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703170]: Could not generate persistent MAC address for veth825051c: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703171]: Could not generate persistent MAC address for veth4ed5ff8: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703189]: Could not generate persistent MAC address for veth85e57e4: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703190]: Could not generate persistent MAC address for veth73ea068: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703176]: Could not generate persistent MAC address for veth3d3739b: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703191]: Could not generate persistent MAC address for veth532cd71: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703182]: Could not generate persistent MAC address for vethadd3530: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703176]: Could not generate persistent MAC address for veth1cfa9e1: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703218]: Could not generate persistent MAC address for veth1288ebf: No such file or directory Sep 25 18:29:30 sentry-docker00.cs.umd.edu systemd-udevd[3703215]: Could not generate persistent MAC address for veth7249bc9: No such file or directory Sep 25 18:49:38 sentry-docker00.cs.umd.edu systemd-udevd[3712556]: link_config: could not get ethtool features for veth85e57e4 Sep 25 18:49:38 sentry-docker00.cs.umd.edu systemd-udevd[3712556]: Could not set offload features of veth85e57e4: No such device Sep 25 18:49:38 sentry-docker00.cs.umd.edu lldpd[2542515]: unable to bind to raw socket for interface veth85e57e4: No such device Sep 25 18:49:38 sentry-docker00.cs.umd.edu lldpd[2542517]: unable to initialize veth85e57e4 ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 25 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 18:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 18:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 15 total) == Sep 25 18:13:09 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5SaIh1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5SaIh1. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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 25 18:25:56 submit26-b9-f1 setroubleshoot[3685956]: 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, 15 total) == Sep 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.FuN43r/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FuN43r. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:06:51 submit26-b9-f2 setroubleshoot[2770337]: 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 25 18:08:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-f3 (1 distinct, 4 total) == Sep 25 18:15:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f4 (1 distinct, 6 total) == Sep 25 18:05:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == yogurt (5 distinct, 5 total) == Sep 25 18:05:13 yogurt kernel: [drm:radeon_gem_va_update_vm [radeon]] *ERROR* Couldn't update BO_VA (-4) Sep 25 18:56:04 yogurt falcon-sensor-bpf[947]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 25 18:56:04 yogurt falcon-sensor-bpf[947]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 Sep 25 19:00:13 yogurt wmstickynotes[2808339]: The program 'wmstickynotes' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadWindow (invalid Window parameter)'.#012 (Details: serial 24959 error_code 3 request_code 18 minor_code 0)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the --sync command line#012 option to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the gdk_x_error() function.) Sep 25 19:00:13 yogurt systemd-coredump[397831]: Process 2808339 (wmstickynotes) of user 20263 dumped core.