Command: /usr/local/sbin/syslog-digest.py Time : 0.1445s Status : exited 0 Output : Syslog digest — 2026-10-09 22:05 EDT Processed 5,386 lines, filtered 3,170 (58%). 2,216 unknown (233 distinct) from 21 host(s). == abuse (1 distinct, 347 total) == Oct 9 21:05:16 abuse rsyslogd[1033]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.2404.0 try https://www.rsyslog.com/e/2433 ] [x347] == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 9 21:20:37 b0b02.cs.umd.edu rustdesk[2098245]: cannot open display: == gle-dind00.cs.umd.edu (35 distinct, 35 total) == Oct 9 21:28:09 gle-dind00.cs.umd.edu systemd-udevd[3657852]: Could not generate persistent MAC address for veth0736f05: No such file or directory Oct 9 21:28:09 gle-dind00.cs.umd.edu systemd-udevd[3657853]: Could not generate persistent MAC address for vethd82597b: No such file or directory Oct 9 21:28:10 gle-dind00.cs.umd.edu systemd-udevd[3658120]: Could not generate persistent MAC address for vethf61a986: No such file or directory Oct 9 21:28:10 gle-dind00.cs.umd.edu systemd-udevd[3658121]: Could not generate persistent MAC address for veth7a33af8: No such file or directory Oct 9 21:28:11 gle-dind00.cs.umd.edu systemd-udevd[3658218]: Could not generate persistent MAC address for veth1fceb3c: No such file or directory Oct 9 21:28:11 gle-dind00.cs.umd.edu systemd-udevd[3658219]: Could not generate persistent MAC address for vethc5343d8: No such file or directory Oct 9 21:28:12 gle-dind00.cs.umd.edu systemd-udevd[3658320]: Could not generate persistent MAC address for vetha32135e: No such file or directory Oct 9 21:28:12 gle-dind00.cs.umd.edu systemd-udevd[3658321]: Could not generate persistent MAC address for vetha4371ff: No such file or directory Oct 9 21:28:13 gle-dind00.cs.umd.edu systemd-udevd[3658419]: Could not generate persistent MAC address for veth3cc1a32: No such file or directory Oct 9 21:28:13 gle-dind00.cs.umd.edu systemd-udevd[3658420]: Could not generate persistent MAC address for veth7fb66a1: No such file or directory Oct 9 21:28:15 gle-dind00.cs.umd.edu systemd-udevd[3658592]: Could not generate persistent MAC address for vethbb7a7e4: No such file or directory Oct 9 21:28:15 gle-dind00.cs.umd.edu systemd-udevd[3658593]: Could not generate persistent MAC address for vethf2b20a9: No such file or directory Oct 9 21:28:16 gle-dind00.cs.umd.edu systemd-udevd[3658703]: Could not generate persistent MAC address for vethc8babdd: No such file or directory Oct 9 21:28:16 gle-dind00.cs.umd.edu systemd-udevd[3658702]: Could not generate persistent MAC address for vethd5b85bf: No such file or directory Oct 9 21:28:19 gle-dind00.cs.umd.edu systemd-udevd[3658827]: Could not generate persistent MAC address for veth4c85961: No such file or directory Oct 9 21:28:19 gle-dind00.cs.umd.edu systemd-udevd[3658828]: Could not generate persistent MAC address for veth6309be0: No such file or directory Oct 9 21:28:20 gle-dind00.cs.umd.edu systemd-udevd[3658959]: Could not generate persistent MAC address for veth855ade1: No such file or directory Oct 9 21:28:20 gle-dind00.cs.umd.edu systemd-udevd[3658960]: Could not generate persistent MAC address for veth3df2a80: No such file or directory Oct 9 21:29:09 gle-dind00.cs.umd.edu systemd-udevd[3659149]: Could not generate persistent MAC address for vethd7f2812: No such file or directory Oct 9 21:29:09 gle-dind00.cs.umd.edu systemd-udevd[3659148]: Could not generate persistent MAC address for veth2ac54b7: No such file or directory Oct 9 21:29:10 gle-dind00.cs.umd.edu systemd-udevd[3659250]: Could not generate persistent MAC address for veth25d3e6a: No such file or directory Oct 9 21:29:10 gle-dind00.cs.umd.edu systemd-udevd[3659251]: Could not generate persistent MAC address for veth7f9d22f: No such file or directory Oct 9 21:29:11 gle-dind00.cs.umd.edu systemd-udevd[3659345]: Could not generate persistent MAC address for vethe3f5105: No such file or directory Oct 9 21:29:11 gle-dind00.cs.umd.edu systemd-udevd[3659346]: Could not generate persistent MAC address for veth90ee2fe: No such file or directory Oct 9 21:29:12 gle-dind00.cs.umd.edu systemd-udevd[3659449]: Could not generate persistent MAC address for veth54c7fd2: No such file or directory Oct 9 21:29:12 gle-dind00.cs.umd.edu systemd-udevd[3659448]: Could not generate persistent MAC address for veth377380d: No such file or directory Oct 9 21:29:13 gle-dind00.cs.umd.edu systemd-udevd[3659545]: Could not generate persistent MAC address for vethddbc3af: No such file or directory Oct 9 21:29:13 gle-dind00.cs.umd.edu systemd-udevd[3659546]: Could not generate persistent MAC address for vethfdb5f4c: No such file or directory Oct 9 21:29:14 gle-dind00.cs.umd.edu systemd-udevd[3659718]: Could not generate persistent MAC address for veth6c75e00: No such file or directory Oct 9 21:29:14 gle-dind00.cs.umd.edu systemd-udevd[3659719]: Could not generate persistent MAC address for veth4de7124: No such file or directory ... 5 more distinct messages not shown == gle-dind02.cs.umd.edu (52 distinct, 52 total) == Oct 9 21:26:36 gle-dind02.cs.umd.edu systemd-udevd[2404710]: Could not generate persistent MAC address for veth1acaff4: No such file or directory Oct 9 21:26:36 gle-dind02.cs.umd.edu systemd-udevd[2404711]: Could not generate persistent MAC address for vethc125e30: No such file or directory Oct 9 21:26:37 gle-dind02.cs.umd.edu systemd-udevd[2404811]: Could not generate persistent MAC address for veth4e9fdb7: No such file or directory Oct 9 21:26:37 gle-dind02.cs.umd.edu systemd-udevd[2404812]: Could not generate persistent MAC address for veth35a3e6e: No such file or directory Oct 9 21:26:38 gle-dind02.cs.umd.edu systemd-udevd[2404909]: Could not generate persistent MAC address for vethbe6f5c3: No such file or directory Oct 9 21:26:38 gle-dind02.cs.umd.edu systemd-udevd[2404910]: Could not generate persistent MAC address for veth80a9a08: No such file or directory Oct 9 21:26:39 gle-dind02.cs.umd.edu systemd-udevd[2405009]: Could not generate persistent MAC address for veth621c3c5: No such file or directory Oct 9 21:26:39 gle-dind02.cs.umd.edu systemd-udevd[2405010]: Could not generate persistent MAC address for vethce50474: No such file or directory Oct 9 21:26:40 gle-dind02.cs.umd.edu systemd-udevd[2405108]: Could not generate persistent MAC address for vethfc27227: No such file or directory Oct 9 21:26:40 gle-dind02.cs.umd.edu systemd-udevd[2405109]: Could not generate persistent MAC address for veth3411981: No such file or directory Oct 9 21:26:42 gle-dind02.cs.umd.edu systemd-udevd[2405280]: Could not generate persistent MAC address for veth8cd152b: No such file or directory Oct 9 21:26:42 gle-dind02.cs.umd.edu systemd-udevd[2405279]: Could not generate persistent MAC address for vethf3d6b12: No such file or directory Oct 9 21:26:43 gle-dind02.cs.umd.edu systemd-udevd[2405393]: Could not generate persistent MAC address for veth5d74c77: No such file or directory Oct 9 21:26:43 gle-dind02.cs.umd.edu systemd-udevd[2405394]: Could not generate persistent MAC address for veth5c5dbaf: No such file or directory Oct 9 21:26:46 gle-dind02.cs.umd.edu systemd-udevd[2405523]: Could not generate persistent MAC address for vethb880167: No such file or directory Oct 9 21:26:46 gle-dind02.cs.umd.edu systemd-udevd[2405524]: Could not generate persistent MAC address for vethb23aba8: No such file or directory Oct 9 21:26:47 gle-dind02.cs.umd.edu systemd-udevd[2405634]: Could not generate persistent MAC address for vethdc231bc: No such file or directory Oct 9 21:26:47 gle-dind02.cs.umd.edu systemd-udevd[2405635]: Could not generate persistent MAC address for vethde21aa0: No such file or directory Oct 9 21:28:21 gle-dind02.cs.umd.edu systemd-udevd[2406286]: Could not generate persistent MAC address for veth87515a6: No such file or directory Oct 9 21:28:21 gle-dind02.cs.umd.edu systemd-udevd[2406287]: Could not generate persistent MAC address for veth0434af7: No such file or directory Oct 9 21:28:22 gle-dind02.cs.umd.edu systemd-udevd[2406387]: Could not generate persistent MAC address for vethd76ce02: No such file or directory Oct 9 21:28:22 gle-dind02.cs.umd.edu systemd-udevd[2406388]: Could not generate persistent MAC address for veth14f173c: No such file or directory Oct 9 21:28:23 gle-dind02.cs.umd.edu systemd-udevd[2406486]: Could not generate persistent MAC address for vethfaa6f5e: No such file or directory Oct 9 21:28:23 gle-dind02.cs.umd.edu systemd-udevd[2406487]: Could not generate persistent MAC address for vethe991da2: No such file or directory Oct 9 21:28:25 gle-dind02.cs.umd.edu systemd-udevd[2406587]: Could not generate persistent MAC address for veth065e0a7: No such file or directory Oct 9 21:28:25 gle-dind02.cs.umd.edu systemd-udevd[2406586]: Could not generate persistent MAC address for vethccd0423: No such file or directory Oct 9 21:28:25 gle-dind02.cs.umd.edu systemd-udevd[2406685]: Could not generate persistent MAC address for veth6cb1623: No such file or directory Oct 9 21:28:25 gle-dind02.cs.umd.edu systemd-udevd[2406686]: Could not generate persistent MAC address for veth9d5abbd: No such file or directory Oct 9 21:28:27 gle-dind02.cs.umd.edu systemd-udevd[2406856]: Could not generate persistent MAC address for veth7132dd5: No such file or directory Oct 9 21:28:27 gle-dind02.cs.umd.edu systemd-udevd[2406857]: Could not generate persistent MAC address for vethfca8390: No such file or directory ... 22 more distinct messages not shown == idm00 (1 distinct, 1 total) == Oct 9 21:54:43 idm00 named[4166701]: client @0x7f11a0005288 10.73.240.42#64917: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 9 21:39:21 idmp0 named[1598691]: client @0x7f2d480190a8 10.73.240.43#50332: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Oct 9 21:18:43 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 9 21:29:08 krispykreme.cs.umd.edu sshd-session[4014118]: error: send_error: write: Connection reset by peer == munin (2 distinct, 2 total) == Oct 9 21:08:13 munin sudo[2512983]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Oct 9 21:08:13 munin sudo[2512983]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Oct 9 21:13:03 newhonors2 dhcpcd[3804544]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 9 21:05:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6082, QN: 6339/6339, ET: 13) *** Oct 9 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6083) *** Oct 9 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6083, QN: 63/63, ET: 0) *** Oct 9 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6083) *** Oct 9 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6083, QN: 8124/8124, ET: 0) *** Oct 9 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6084) *** Oct 9 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6084) *** Oct 9 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6084, QN: 64/64, ET: 0) *** Oct 9 21:10:20 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6084, QN: 9045/9045, ET: 19) *** Oct 9 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6085) *** Oct 9 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6085, QN: 7156/7156, ET: 0) *** Oct 9 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6085) *** Oct 9 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6085, QN: 65/65, ET: 0) *** Oct 9 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6086) *** Oct 9 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6086) *** Oct 9 21:15:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6086, QN: 63/63, ET: 1) *** Oct 9 21:15:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6086, QN: 6206/6206, ET: 12) *** Oct 9 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6087) *** Oct 9 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6087, QN: 7618/7618, ET: 0) *** Oct 9 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6087) *** Oct 9 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6087, QN: 62/62, ET: 0) *** Oct 9 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6088) *** Oct 9 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6088) *** Oct 9 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6088, QN: 58/58, ET: 0) *** Oct 9 21:20:17 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6088, QN: 8577/8577, ET: 16) *** Oct 9 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6089) *** Oct 9 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6089, QN: 6857/6857, ET: 0) *** Oct 9 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6089) *** Oct 9 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6089, QN: 59/59, ET: 0) *** Oct 9 21:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6090) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 9 21:09:09 outbound00.cs.umd.edu python3[1068397]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 9 21:13:06 outbound01.cs.umd.edu python3[2539480]: ldapdb [x6] == quiss (1 distinct, 1 total) == Oct 9 21:07:16 quiss systemd-coredump[1819976]: Process 3784707 (claude) of user 14533 dumped core.#012#012Stack trace of thread 3784707:#012#0 0x0000000003bb74cc n/a (/adminhomes/josephao/.local/share/claude/versions/2.1.284 + 0x39b74cc)#012ELF object binary architecture: AMD x86-64 == strawberry (7 distinct, 38 total) == Oct 9 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 9 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 9 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 9 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 9 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 9 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 9 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1538 total) == Oct 9 21:05:22 submit10-cln25 rsyslogd: file '/var/log/messages': open error: Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2433 ] [x1200] Oct 9 21:05:22 submit10-cln25 rsyslogd: imjournal: fopen() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Input/output error [v8.24.0-57.el7_9.3 try http://www.rsyslog.com/e/2013 ] [x333] Oct 9 21:25:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 9 21:28:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 9 21:30:00 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (2 distinct, 9 total) == Sep 12 00:38:16 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] Sep 12 01:31:25 submit26-b9-3 systemd-coredump[2911994]: Process 2911991 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2911991:#012#0 0x00000000004021e2 highlight_text (release02 + 0x21e2)#012#1 0x0000000000401593 main (release02 + 0x1593)#012#2 0x00007fcc0022a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fcc0022a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010c5 _start (release02 + 0x10c5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f1 (1 distinct, 10 total) == Oct 9 21:05:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x10] == submit26-b9-f2 (1 distinct, 8 total) == Oct 9 21:15:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f3 (12 distinct, 21 total) == Oct 9 21:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 [x2] Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.v8GhKF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba [x2] Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.v8GhKF. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 [x2] Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Oct 9 21:06:50 submit26-b9-f3 setroubleshoot[2680837]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7u7PHe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 9 21:50:36 submit26-b9-f3 systemd-coredump[2690449]: Process 2690446 (release02) of user 1001 dumped core.#012#012Stack trace of thread 2690446:#012#0 0x0000000000402276 highlight_text (release02 + 0x2276)#012#1 0x0000000000401593 main (release02 + 0x1593)#012#2 0x00007f7ab6e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f7ab6e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010c5 _start (release02 + 0x10c5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (10 distinct, 14 total) == Oct 9 21:05:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.scqZ6E/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Oct 9 21:24:55 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.scqZ6E. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 9 21:24:56 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Oct 9 21:24:56 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Oct 9 21:24:56 submit26-b9-f4 setroubleshoot[695731]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915