Command: /usr/local/sbin/syslog-digest.py Time : 0.0573s Status : exited 0 Output : Syslog digest — 2026-09-23 14:05 EDT Processed 3,010 lines, filtered 2,491 (82%). 519 unknown (241 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 23 13:57:02 b0b02.cs.umd.edu rustdesk[250839]: cannot open display: == bale (5 distinct, 87 total) == Sep 23 13:05:15 bale setroubleshoot[2129855]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 23 13:05:15 bale setroubleshoot[2129855]: 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 23 13:05:18 bale setroubleshoot[2129855]: 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 23 13:05:21 bale setroubleshoot[2129855]: 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 23 13:05:33 bale setroubleshoot[2130470]: 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 [x13] == biggulp.cs.umd.edu (1 distinct, 4 total) == Sep 23 13:44:01 biggulp.cs.umd.edu sshd-session[3663581]: pam_access(sshd:auth): access denied for user `kaptchuk' from `108.51.225.194' [x4] == galax (3 distinct, 8 total) == Sep 23 13:10:06 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6] Sep 23 13:25:25 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 16387 times, consider switching to WQ_UNBOUND Sep 23 13:49:01 galax systemd[1]: motd-news.service: Main process exited, code=dumped, status=11/SEGV == gle-dind00.cs.umd.edu (16 distinct, 16 total) == Sep 23 13:10:07 gle-dind00.cs.umd.edu systemd-udevd[2656180]: Could not generate persistent MAC address for veth0a5d04c: No such file or directory Sep 23 13:10:07 gle-dind00.cs.umd.edu systemd-udevd[2656181]: Could not generate persistent MAC address for vethe20b990: No such file or directory Sep 23 13:10:08 gle-dind00.cs.umd.edu systemd-udevd[2656286]: Could not generate persistent MAC address for veth4e854b6: No such file or directory Sep 23 13:10:08 gle-dind00.cs.umd.edu systemd-udevd[2656287]: Could not generate persistent MAC address for veth7a3d2c3: No such file or directory Sep 23 13:10:08 gle-dind00.cs.umd.edu systemd-udevd[2656384]: Could not generate persistent MAC address for veth7a5ae1f: No such file or directory Sep 23 13:10:08 gle-dind00.cs.umd.edu systemd-udevd[2656385]: Could not generate persistent MAC address for veth95f157e: No such file or directory Sep 23 13:10:09 gle-dind00.cs.umd.edu systemd-udevd[2656488]: Could not generate persistent MAC address for veth89323ca: No such file or directory Sep 23 13:10:09 gle-dind00.cs.umd.edu systemd-udevd[2656487]: Could not generate persistent MAC address for veth40034d9: No such file or directory Sep 23 13:10:10 gle-dind00.cs.umd.edu systemd-udevd[2656587]: Could not generate persistent MAC address for veth6d92bba: No such file or directory Sep 23 13:10:10 gle-dind00.cs.umd.edu systemd-udevd[2656588]: Could not generate persistent MAC address for veth1607f10: No such file or directory Sep 23 13:10:14 gle-dind00.cs.umd.edu systemd-udevd[2656770]: Could not generate persistent MAC address for vetha0c8a54: No such file or directory Sep 23 13:10:14 gle-dind00.cs.umd.edu systemd-udevd[2656772]: Could not generate persistent MAC address for vetha04e1f3: No such file or directory Sep 23 13:10:17 gle-dind00.cs.umd.edu systemd-udevd[2656884]: Could not generate persistent MAC address for veth0ca22e9: No such file or directory Sep 23 13:10:17 gle-dind00.cs.umd.edu systemd-udevd[2656885]: Could not generate persistent MAC address for vetha02e94b: No such file or directory Sep 23 13:10:26 gle-dind00.cs.umd.edu systemd-udevd[2657042]: Could not generate persistent MAC address for veth861d3f1: No such file or directory Sep 23 13:10:26 gle-dind00.cs.umd.edu systemd-udevd[2657043]: Could not generate persistent MAC address for veth71ad186: No such file or directory == gle-dind02.cs.umd.edu (20 distinct, 20 total) == Sep 23 13:08:57 gle-dind02.cs.umd.edu systemd-udevd[2205784]: Could not generate persistent MAC address for veth2f4cff1: No such file or directory Sep 23 13:08:57 gle-dind02.cs.umd.edu systemd-udevd[2205785]: Could not generate persistent MAC address for vethdde5562: No such file or directory Sep 23 13:08:58 gle-dind02.cs.umd.edu systemd-udevd[2205884]: Could not generate persistent MAC address for veth1806ced: No such file or directory Sep 23 13:08:58 gle-dind02.cs.umd.edu systemd-udevd[2205885]: Could not generate persistent MAC address for vethd2a47ce: No such file or directory Sep 23 13:08:58 gle-dind02.cs.umd.edu systemd-udevd[2205983]: Could not generate persistent MAC address for veth44cc700: No such file or directory Sep 23 13:08:58 gle-dind02.cs.umd.edu systemd-udevd[2205984]: Could not generate persistent MAC address for vethc63cb01: No such file or directory Sep 23 13:08:59 gle-dind02.cs.umd.edu systemd-udevd[2206082]: Could not generate persistent MAC address for vetha4647b7: No such file or directory Sep 23 13:08:59 gle-dind02.cs.umd.edu systemd-udevd[2206083]: Could not generate persistent MAC address for veth7d59279: No such file or directory Sep 23 13:09:00 gle-dind02.cs.umd.edu systemd-udevd[2206178]: Could not generate persistent MAC address for vethb05a38d: No such file or directory Sep 23 13:09:00 gle-dind02.cs.umd.edu systemd-udevd[2206179]: Could not generate persistent MAC address for veth8a8edd7: No such file or directory Sep 23 13:09:03 gle-dind02.cs.umd.edu systemd-udevd[2206367]: Could not generate persistent MAC address for vethae9d229: No such file or directory Sep 23 13:09:03 gle-dind02.cs.umd.edu systemd-udevd[2206368]: Could not generate persistent MAC address for veth2c51ce1: No such file or directory Sep 23 13:09:06 gle-dind02.cs.umd.edu systemd-udevd[2206503]: Could not generate persistent MAC address for veth2cc1dda: No such file or directory Sep 23 13:09:06 gle-dind02.cs.umd.edu systemd-udevd[2206502]: Could not generate persistent MAC address for vethff5286a: No such file or directory Sep 23 13:09:52 gle-dind02.cs.umd.edu systemd-udevd[2207490]: Could not generate persistent MAC address for vethb86e147: No such file or directory Sep 23 13:09:52 gle-dind02.cs.umd.edu systemd-udevd[2207491]: Could not generate persistent MAC address for veth55762e2: No such file or directory Sep 23 13:09:54 gle-dind02.cs.umd.edu systemd-udevd[2207608]: Could not generate persistent MAC address for vethaeec958: No such file or directory Sep 23 13:09:54 gle-dind02.cs.umd.edu systemd-udevd[2207607]: Could not generate persistent MAC address for veth403fac8: No such file or directory Sep 23 13:10:03 gle-dind02.cs.umd.edu systemd-udevd[2207726]: Could not generate persistent MAC address for vethf47cd66: No such file or directory Sep 23 13:10:03 gle-dind02.cs.umd.edu systemd-udevd[2207727]: Could not generate persistent MAC address for veth8394a5c: No such file or directory == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 23 13:42:07 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 23 13:54:27 idm00 named[4166701]: client @0x7f11a4064588 10.73.240.42#58051: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 13:39:31 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#53600: update '73.10.in-addr.arpa/IN' denied == irb2156 (2 distinct, 2 total) == Sep 23 13:16:00 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.13. Sep 23 13:48:31 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 128.8.76.3. == itmon02 (3 distinct, 5 total) == Sep 23 13:17:22 itmon02 SetroubleshootPrivileged.py[1876 failed to retrieve rpm info for path '/var/lib/selinux/targeted/active/modules/200/grafana': Sep 23 13:17:22 itmon02 setroubleshoot[1876135]: SELinux is preventing /usr/sbin/grafana from name_connect access on the tcp_socket port 3306. For complete SELinux messages run: sealert -l deb40268-1414-43e0-8915-0a3785a3ecd5 Sep 23 13:22:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == mcstic (1 distinct, 2 total) == Sep 23 13:52:37 mcstic krb5_child[1006339]: Preauthentication failed [x2] == munin (2 distinct, 6 total) == Sep 23 13:09:04 munin sudo[2377460]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3] Sep 23 13:09:04 munin sudo[2377460]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3] == newhonors2 (1 distinct, 24 total) == Sep 23 13:13:03 newhonors2 dhcpcd[3043280]: dhcpcd is not running [x24] == ntop00 (101 distinct, 141 total) == Sep 23 13:05:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 14) *** Sep 23 13:05:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 14) *** Sep 23 13:05:15 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 14, QN: 7600/7600, ET: 14) *** Sep 23 13:05:15 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 14, QN: 45/45, ET: 14) *** Sep 23 13:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 15) *** Sep 23 13:08:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 15, QN: 7355/7355, ET: 0) *** Sep 23 13:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 15) *** Sep 23 13:08:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 15, QN: 58/58, ET: 0) *** Sep 23 13:08:02 ntop00 setroubleshoot[14935]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 5b65c96c-a9fa-4175-8126-0641b1ec385c [x11] Sep 23 13:08:02 ntop00 setroubleshoot[14935]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 0d1f7214-3aae-48d5-8fed-48565bd90d17 [x11] Sep 23 13:08:02 ntop00 setroubleshoot[14935]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 23 13:08:02 ntop00 setroubleshoot[14935]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 4a9c8c49-4f0d-4ad5-b926-84fe3642d3ee [x11] Sep 23 13:10:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 16) *** Sep 23 13:10:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 16) *** Sep 23 13:10:11 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 16, QN: 7227/7227, ET: 10) *** Sep 23 13:10:11 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 16, QN: 52/52, ET: 10) *** Sep 23 13:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 17) *** Sep 23 13:13:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 17, QN: 8066/8066, ET: 0) *** Sep 23 13:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 17) *** Sep 23 13:13:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 17, QN: 60/60, ET: 0) *** Sep 23 13:15:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 18) *** Sep 23 13:15:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 18) *** Sep 23 13:15:13 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - END (PID: 18, QN: 9194/9194, ET: 12) *** Sep 23 13:15:13 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - END (PID: 18, QN: 66/66, ET: 12) *** Sep 23 13:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - START (PID: 19) *** Sep 23 13:18:01 ntop00 sfacctd[9573]: INFO ( p1/print ): *** Purging cache - END (PID: 19, QN: 9881/9881, ET: 0) *** Sep 23 13:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - START (PID: 19) *** Sep 23 13:18:01 ntop00 nfacctd[9659]: INFO ( p1/print ): *** Purging cache - END (PID: 19, QN: 62/62, ET: 0) *** Sep 23 13:20:01 ntop00 sfacctd[9573]: INFO ( m1/mysql ): *** Purging cache - START (PID: 20) *** Sep 23 13:20:01 ntop00 nfacctd[9659]: INFO ( m1/mysql ): *** Purging cache - START (PID: 20) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 23 13:09:09 outbound00.cs.umd.edu python3[3096023]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 23 13:13:06 outbound01.cs.umd.edu python3[1161613]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193083]: link_config: could not get ethtool features for veth83e2723 Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193083]: Could not set offload features of veth83e2723: No such device Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193134]: link_config: could not get ethtool features for veth6af86bd Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193134]: Could not set offload features of veth6af86bd: No such device Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193170]: Could not generate persistent MAC address for vetha1ab1bf: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193171]: Could not generate persistent MAC address for veth04f066f: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193174]: Could not generate persistent MAC address for veth02d494c: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193171]: Could not generate persistent MAC address for veth1208ac0: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193192]: Could not generate persistent MAC address for veth9d32592: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193189]: Could not generate persistent MAC address for veth9ecd4bd: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193189]: Could not generate persistent MAC address for veth6142003: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193192]: Could not generate persistent MAC address for vethc5e7024: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193214]: Could not generate persistent MAC address for vethcc60131: No such file or directory Sep 23 13:07:23 sentry-docker00.cs.umd.edu systemd-udevd[2193218]: Could not generate persistent MAC address for vethaf164fc: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202713]: link_config: could not get ethtool features for veth6142003 Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202713]: Could not set offload features of veth6142003: No such device Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202800]: link_config: could not get ethtool features for veth02d494c Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202800]: Could not set offload features of veth02d494c: No such device Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202826]: Could not generate persistent MAC address for veth77b43c8: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202825]: Could not generate persistent MAC address for veth1f98b4c: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202829]: Could not generate persistent MAC address for veth57264c4: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202830]: Could not generate persistent MAC address for veth409f5ad: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202834]: Could not generate persistent MAC address for veth6dd8474: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202825]: Could not generate persistent MAC address for vethc363b84: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202834]: Could not generate persistent MAC address for veth7e0b025: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202825]: Could not generate persistent MAC address for vethbf87c73: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202835]: Could not generate persistent MAC address for vethe0809c4: No such file or directory Sep 23 13:27:31 sentry-docker00.cs.umd.edu systemd-udevd[2202837]: Could not generate persistent MAC address for veth1a08dba: No such file or directory Sep 23 13:47:39 sentry-docker00.cs.umd.edu systemd-udevd[2212173]: link_config: could not get ethtool features for veth6dd8474 Sep 23 13:47:39 sentry-docker00.cs.umd.edu systemd-udevd[2212173]: Could not set offload features of veth6dd8474: No such device ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 23 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 23 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 23 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 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 23 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 23 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 5 total) == Sep 23 13:05:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f2 (1 distinct, 4 total) == Sep 23 13:05:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (11 distinct, 19 total) == Sep 23 13:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JYAdEC/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JYAdEC. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: 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 23 13:06:44 submit26-b9-f3 setroubleshoot[2738680]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4CfuhG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f == submit26-b9-f4 (10 distinct, 17 total) == Sep 23 13:08:44 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 [x2] Sep 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.caOzAF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 [x2] Sep 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.caOzAF. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 23 13:24:47 submit26-b9-f4 setroubleshoot[2018649]: 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 23 13:24:48 submit26-b9-f4 setroubleshoot[2018649]: 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