Command: /usr/local/sbin/syslog-digest.py Time : 0.0498s Status : exited 0 Output : Syslog digest — 2026-10-01 19:05 EDT Processed 1,720 lines, filtered 1,283 (74%). 437 unknown (244 distinct) from 23 host(s). == ar102 (57 distinct, 100 total) == Oct 1 18:05:01 ar102 cosmic-greeter[2905]: Failed to create watcher for com.system76.CosmicTk [x12] Oct 1 18:05:01 ar102 cosmic-greeter[2905]: Failed to create watcher for com.system76.CosmicTheme.Dark [x12] Oct 1 18:05:01 ar102 cosmic-greeter[2905]: Failed to create watcher for com.system76.CosmicTheme.Mode [x12] Oct 1 18:10:47 ar102 kernel: ACPI PPTT: No PPTT table found, CPU and cache topology may be inaccurate Oct 1 18:10:47 ar102 kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 Oct 1 18:10:47 ar102 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. Oct 1 18:10:47 ar102 rpc.idmapd[474]: Setting log level to 0 Oct 1 18:10:48 ar102 rpc.idmapd[474]: exiting on signal 15 Oct 1 18:10:50 ar102 lvm[927]: PV /dev/vda3 online, VG rhel is complete. Oct 1 18:10:51 ar102 systemd-tmpfiles[1014]: Opening file "/tmp/.X11-unix/X0" failed, proceeding without lock: No such device or address Oct 1 18:10:51 ar102 alsactl[1103]: alsa-lib main.c:1804:(snd_use_case_mgr_open) [error.ucm] failed to import hw:0 use case configuration -2 Oct 1 18:10:51 ar102 alsactl[1103]: alsa-lib main.c:1804:(snd_use_case_mgr_open) [error.ucm] failed to import hw:1 use case configuration -2 Oct 1 18:10:51 ar102 (lldpd)[1160]: lldpd.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS Oct 1 18:10:51 ar102 systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. [x3] Oct 1 18:10:52 ar102 kernel: Warning: Unmaintained driver is detected: nft_compat Oct 1 18:10:52 ar102 kernel: Warning: Unmaintained driver is detected: nft_compat_module_init Oct 1 18:10:52 ar102 avahi-daemon[1068]: Host name conflict, retrying with ar102-2 Oct 1 18:10:52 ar102 kernel: block dm-0: the capability attribute has been deprecated. Oct 1 18:10:52 ar102 kernel: PEFILE: Unsigned PE binary Oct 1 18:10:57 ar102 (atd)[2715]: atd.service: Referenced but unset environment variable evaluates to an empty string: OPTS Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-0-rescue.conf:6: Unknown line 'grub_users', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-0-rescue.conf:7: Unknown line 'grub_arg', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-0-rescue.conf:8: Unknown line 'grub_class', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.30.1.el10_2.aarch64.conf:6: Unknown line 'grub_users', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.30.1.el10_2.aarch64.conf:7: Unknown line 'grub_arg', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.30.1.el10_2.aarch64.conf:8: Unknown line 'grub_class', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.34.1.el10_2.aarch64.conf:6: Unknown line 'grub_users', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.34.1.el10_2.aarch64.conf:7: Unknown line 'grub_arg', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.34.1.el10_2.aarch64.conf:8: Unknown line 'grub_class', ignoring. Oct 1 18:10:57 ar102 systemd-logind[2703]: /boot/loader/entries/120a3bfde9664bceb6ca5d9557cdaf19-6.12.0-211.49.1.el10_2.aarch64.conf:6: Unknown line 'grub_users', ignoring. ... 27 more distinct messages not shown == atif01.cs.umd.edu (1 distinct, 1 total) == Oct 1 18:32:54 atif01.cs.umd.edu smartd[2697]: Device: /dev/sda [megaraid_disk_03] [SAT], ATA error count increased from 15 to 17 == b0b02.cs.umd.edu (4 distinct, 4 total) == Oct 1 18:08:57 b0b02.cs.umd.edu rustdesk[3322066]: cannot open display: Oct 1 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-01T22:10:59.437046486Z" level=info msg="PurgeUploads starting: olderThan=2026-09-24 22:10:59.436925225 +0000 UTC m=+5099820.196853611, actuallyDelete=true" Oct 1 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-01T22:10:59.437603519Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Oct 1 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-10-01T22:10:59.43763501Z" 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 == hazfs.cs.umd.edu (1 distinct, 1 total) == Oct 1 18:58:33 hazfs.cs.umd.edu rpc.mountd[1586325]: refused mount request from 10.227.96.19 for /raid/webdev (/): not exported == hspc (2 distinct, 2 total) == Oct 1 18:06:37 hspc falcon-sensor-bpf[1008]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Oct 1 18:06:37 hspc falcon-sensor-bpf[1008]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == idm00 (1 distinct, 1 total) == Oct 1 18:54:24 idm00 named[4166701]: client @0x7f11a93ed928 10.73.240.42#61355: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 18:39:26 idmp0 named[1598691]: client @0x7f2d4c4c8488 10.73.240.43#51799: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 1 18:13:50 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (2 distinct, 2 total) == Oct 1 18:49:13 krispykreme.cs.umd.edu sshd-session[764761]: error: maximum authentication attempts exceeded for invalid user ftpuser from 180.72.249.104 port 34455 ssh2 [preauth] Oct 1 18:49:17 krispykreme.cs.umd.edu sshd-session[764767]: error: maximum authentication attempts exceeded for invalid user ftpuser from 180.72.249.104 port 34577 ssh2 [preauth] == lifepix (2 distinct, 2 total) == Oct 1 18:05:11 lifepix falcon-sensor-bpf[875]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Oct 1 18:05:11 lifepix falcon-sensor-bpf[875]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == munin (2 distinct, 8 total) == Oct 1 18:18:23 munin sudo[2480385]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 1 18:18:23 munin sudo[2480385]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == neodontcare.cs.umd.edu (2 distinct, 2 total) == Oct 1 18:05:51 neodontcare.cs.umd.edu falcon-sensor-bpf[951]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Oct 1 18:05:51 neodontcare.cs.umd.edu falcon-sensor-bpf[951]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == newhonors2 (1 distinct, 24 total) == Oct 1 18:13:03 newhonors2 dhcpcd[3423905]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 1 18:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1402) *** Oct 1 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1402) *** Oct 1 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1402, QN: 65/65, ET: 0) *** Oct 1 18:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1402, QN: 6036/6036, ET: 10) *** Oct 1 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1403) *** Oct 1 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1403, QN: 6004/6004, ET: 0) *** Oct 1 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1403) *** Oct 1 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1403, QN: 58/58, ET: 0) *** Oct 1 18:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1404) *** Oct 1 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1404) *** Oct 1 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1404, QN: 60/60, ET: 0) *** Oct 1 18:10:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1404, QN: 5929/5929, ET: 9) *** Oct 1 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1405) *** Oct 1 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1405, QN: 6245/6245, ET: 0) *** Oct 1 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1405) *** Oct 1 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1405, QN: 67/67, ET: 0) *** Oct 1 18:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1406) *** Oct 1 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1406) *** Oct 1 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1406, QN: 59/59, ET: 0) *** Oct 1 18:15:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1406, QN: 5956/5956, ET: 8) *** Oct 1 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1407) *** Oct 1 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1407, QN: 5792/5792, ET: 0) *** Oct 1 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1407) *** Oct 1 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1407, QN: 56/56, ET: 0) *** Oct 1 18:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1408) *** Oct 1 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1408) *** Oct 1 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1408, QN: 67/67, ET: 0) *** Oct 1 18:20:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1408, QN: 6016/6016, ET: 8) *** Oct 1 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1409) *** Oct 1 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1409, QN: 5964/5964, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 1 18:09:09 outbound00.cs.umd.edu python3[1721243]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 1 18:13:06 outbound01.cs.umd.edu python3[3986025]: ldapdb [x6] == portal (1 distinct, 67 total) == Oct 1 18:05:19 portal setroubleshoot[4144932]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x67] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573744]: link_config: could not get ethtool features for veth574f493 Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573744]: Could not set offload features of veth574f493: No such device Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573839]: link_config: could not get ethtool features for vethf979caa Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573839]: Could not set offload features of vethf979caa: No such device Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573863]: Could not generate persistent MAC address for vethc1cd938: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573864]: Could not generate persistent MAC address for veth7e9fcfa: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573867]: Could not generate persistent MAC address for vethe1735ef: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573868]: Could not generate persistent MAC address for veth7e1785a: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573863]: Could not generate persistent MAC address for veth58a1cb5: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573890]: Could not generate persistent MAC address for vethb074eb1: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573888]: Could not generate persistent MAC address for veth1940f8c: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573872]: Could not generate persistent MAC address for vethf4aebca: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573938]: Could not generate persistent MAC address for vethd33f2cb: No such file or directory Oct 1 18:09:07 sentry-docker00.cs.umd.edu systemd-udevd[3573942]: Could not generate persistent MAC address for veth58f9517: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583233]: link_config: could not get ethtool features for veth1940f8c Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583233]: Could not set offload features of veth1940f8c: No such device Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583262]: Could not generate persistent MAC address for vethbd3cb95: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583263]: Could not generate persistent MAC address for vetha402bfe: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583266]: Could not generate persistent MAC address for veth74e2b97: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583262]: Could not generate persistent MAC address for veth94336ba: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583268]: Could not generate persistent MAC address for vetha0151fc: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583262]: Could not generate persistent MAC address for veth72314af: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583262]: Could not generate persistent MAC address for vethb31890c: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583283]: Could not generate persistent MAC address for vetha353b22: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583350]: Could not generate persistent MAC address for veth0d68fbb: No such file or directory Oct 1 18:29:15 sentry-docker00.cs.umd.edu systemd-udevd[3583351]: Could not generate persistent MAC address for veth816b82b: No such file or directory Oct 1 18:49:24 sentry-docker00.cs.umd.edu systemd-udevd[3592681]: Could not generate persistent MAC address for veth1c7ecd4: No such file or directory Oct 1 18:49:24 sentry-docker00.cs.umd.edu systemd-udevd[3592682]: Could not generate persistent MAC address for vethd41858a: No such file or directory Oct 1 18:49:24 sentry-docker00.cs.umd.edu systemd-udevd[3592685]: Could not generate persistent MAC address for veth86f99e8: No such file or directory Oct 1 18:49:24 sentry-docker00.cs.umd.edu systemd-udevd[3592687]: Could not generate persistent MAC address for veth380bc27: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 1 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 18:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 18:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (12 distinct, 19 total) == Oct 1 18:13:09 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Oct 1 18:13:10 submit26-b9-f1 systemd-coredump[444996]: Process 444993 (release03) of user 1001 dumped core.#012#012Stack trace of thread 444993:#012#0 0x000000000040123b right_align (release03 + 0x123b)#012#1 0x00000000004011d5 main (release03 + 0x11d5)#012#2 0x00007fa08f62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fa08f62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401075 _start (release03 + 0x1075)#012ELF object binary architecture: AMD x86-64 Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 [x2] Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 [x2] Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.L4OMrm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.L4OMrm. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 [x2] Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: 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 [x2] Oct 1 18:25:59 submit26-b9-f1 setroubleshoot[446268]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xrm8OJ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (10 distinct, 11 total) == Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.rPfkyC/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.rPfkyC. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:06:53 submit26-b9-f2 setroubleshoot[3755986]: 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 Oct 1 18:23:12 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (1 distinct, 6 total) == Oct 1 18:08:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-f4 (1 distinct, 1 total) == Oct 1 18:23:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL