Command: /usr/local/sbin/syslog-digest.py Time : 0.0563s Status : exited 0 Output : Syslog digest — 2026-09-19 14:05 EDT Processed 2,867 lines, filtered 2,268 (79%). 599 unknown (199 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 13:51:00 b0b02.cs.umd.edu rustdesk[2908059]: cannot open display: == bale (5 distinct, 85 total) == Sep 19 13:05:54 bale setroubleshoot[870494]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 19 13:05:55 bale setroubleshoot[870494]: 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 [x13] Sep 19 13:05:57 bale setroubleshoot[870494]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 19 13:06:00 bale setroubleshoot[870494]: 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 [x11] Sep 19 13:06:12 bale setroubleshoot[871108]: 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 [x12] == csfw00a (1 distinct, 126 total) == Sep 19 13:04:16 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x126] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 19 13:50:19 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 19 13:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#61352: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 13:37:56 idmp0 named[1598691]: client @0x7f2d34043a38 10.73.240.43#57760: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 19 13:38:09 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (1 distinct, 5 total) == Sep 19 13:24:40 krispykreme.cs.umd.edu sshd-session[4114163]: error: send_error: write: Connection reset by peer [x5] == munin (2 distinct, 6 total) == Sep 19 13:58:05 munin sudo[307400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3] Sep 19 13:58:05 munin sudo[307400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3] == newhonors2 (1 distinct, 24 total) == Sep 19 13:13:03 newhonors2 dhcpcd[2860307]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 19 13:05:02 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 130) *** Sep 19 13:05:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 5793/5793, ET: 20) *** Sep 19 13:05:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 130, QN: 47/47, ET: 19) *** Sep 19 13:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 131) *** Sep 19 13:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 56/56, ET: 0) *** Sep 19 13:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 131) *** Sep 19 13:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 131, QN: 6572/6572, ET: 0) *** Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12] Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12] Sep 19 13:08:02 ntop00 setroubleshoot[642896]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 13:08:02 ntop00 setroubleshoot[642896]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12] Sep 19 13:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) *** Sep 19 13:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 132) *** Sep 19 13:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 64/64, ET: 0) *** Sep 19 13:10:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 132, QN: 6588/6588, ET: 21) *** Sep 19 13:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 133) *** Sep 19 13:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 59/59, ET: 0) *** Sep 19 13:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 133) *** Sep 19 13:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 133, QN: 6256/6256, ET: 0) *** Sep 19 13:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) *** Sep 19 13:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 134) *** Sep 19 13:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 53/53, ET: 0) *** Sep 19 13:15:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 134, QN: 6424/6424, ET: 21) *** Sep 19 13:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 19 13:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 6858/6858, ET: 0) *** Sep 19 13:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 135) *** Sep 19 13:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 135, QN: 55/55, ET: 0) *** Sep 19 13:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** Sep 19 13:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 136, QN: 61/61, ET: 0) *** Sep 19 13:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 136) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 13:09:09 outbound00.cs.umd.edu python3[1708501]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 13:13:06 outbound01.cs.umd.edu python3[3967206]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653374]: link_config: could not get ethtool features for veth75a1e1c Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653374]: Could not set offload features of veth75a1e1c: No such device Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653409]: Could not generate persistent MAC address for veth334f356: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653410]: Could not generate persistent MAC address for vethed5cda3: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653413]: Could not generate persistent MAC address for vethd154d63: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653414]: Could not generate persistent MAC address for veth2d418ab: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653428]: Could not generate persistent MAC address for veth6136334: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653432]: Could not generate persistent MAC address for vethf3478c4: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653432]: Could not generate persistent MAC address for veth5759efe: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653433]: Could not generate persistent MAC address for veth8471c1c: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653449]: Could not generate persistent MAC address for veth11422a6: No such file or directory Sep 19 13:07:43 sentry-docker00.cs.umd.edu systemd-udevd[3653454]: Could not generate persistent MAC address for vethdfe7f09: No such file or directory Sep 19 13:27:51 sentry-docker00.cs.umd.edu systemd-udevd[3663001]: link_config: could not get ethtool features for veth6136334 Sep 19 13:27:51 sentry-docker00.cs.umd.edu systemd-udevd[3663001]: Could not set offload features of veth6136334: No such device Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663037]: Could not generate persistent MAC address for veth270b11f: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663038]: Could not generate persistent MAC address for veth6ff5c5d: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663041]: Could not generate persistent MAC address for veth1637326: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663042]: Could not generate persistent MAC address for veth0d38f54: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663065]: Could not generate persistent MAC address for vethb52a269: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663066]: Could not generate persistent MAC address for vethd673ab3: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663081]: Could not generate persistent MAC address for veth542786a: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663080]: Could not generate persistent MAC address for veth5de8444: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663088]: Could not generate persistent MAC address for veth2a1a552: No such file or directory Sep 19 13:27:52 sentry-docker00.cs.umd.edu systemd-udevd[3663078]: Could not generate persistent MAC address for veth014b248: No such file or directory Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672430]: link_config: could not get ethtool features for veth270b11f Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672430]: Could not set offload features of veth270b11f: No such device Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672455]: Could not generate persistent MAC address for vethd4aa5e8: No such file or directory Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672456]: Could not generate persistent MAC address for vethb82a509: No such file or directory Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672474]: Could not generate persistent MAC address for veth7c256e0: No such file or directory Sep 19 13:48:00 sentry-docker00.cs.umd.edu systemd-udevd[3672473]: Could not generate persistent MAC address for vethc607bcb: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 13:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 13:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (4 distinct, 9 total) == Sep 19 13:05:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497464]: Process 2497461 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497461:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f5ee422a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f5ee422a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497475]: Process 2497472 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497472:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007fb34be2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fb34be2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 13:30:03 submit26-b9-f1 systemd-coredump[2497509]: Process 2497506 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2497506:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007fec9202a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fec9202a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (5 distinct, 11 total) == Sep 19 13:23:22 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] Sep 19 13:50:08 submit26-b9-f2 systemd-coredump[1617004]: Process 1617001 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617001:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f5f46e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f5f46e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 13:50:08 submit26-b9-f2 systemd-coredump[1617032]: Process 1617029 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617029:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f20abc2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f20abc2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 13:50:09 submit26-b9-f2 systemd-coredump[1617066]: Process 1617063 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617063:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007f3b8b22a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f3b8b22a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 Sep 19 13:50:09 submit26-b9-f2 systemd-coredump[1617077]: Process 1617074 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1617074:#012#0 0x0000000000401a31 main (grades + 0x1a31)#012#1 0x00007ff3eba2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007ff3eba2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010d5 _start (grades + 0x10d5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (11 distinct, 20 total) == Sep 19 13:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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] Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qNuA5g/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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] Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qNuA5g. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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] Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: 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 Sep 19 13:06:42 submit26-b9-f3 setroubleshoot[1994351]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yGMzk1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f == submit26-b9-f4 (10 distinct, 12 total) == Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xkHbf3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xkHbf3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:24:46 submit26-b9-f4 setroubleshoot[1438678]: 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 Sep 19 13:25:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]