Command: /usr/local/sbin/syslog-digest.py Time : 0.0511s Status : exited 0 Output : Syslog digest — 2026-09-30 14:05 EDT Processed 2,106 lines, filtered 1,637 (77%). 469 unknown (229 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 30 13:07:15 b0b02.cs.umd.edu rustdesk[2811406]: cannot open display: == biggulp.cs.umd.edu (6 distinct, 6 total) == Sep 30 13:46:35 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 13:46:35 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 13:46:37 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 13:46:37 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 13:46:40 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 13:46:40 biggulp.cs.umd.edu sshd-session[1239511]: error: kex_protocol_error: type 30 seq 7 [preauth] == cheezit.cs.umd.edu (8 distinct, 10 total) == Sep 30 13:29:51 cheezit.cs.umd.edu krb5_child[522733]: Preauthentication failed [x2] Sep 30 13:29:51 cheezit.cs.umd.edu sshd-session[522712]: error: PAM: Authentication failure for ekmolloy from 10.175.196.29 [x2] Sep 30 13:52:40 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 13:52:40 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 13:52:42 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 13:52:42 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 13:52:44 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 13:52:44 cheezit.cs.umd.edu sshd-session[536932]: error: kex_protocol_error: type 30 seq 7 [preauth] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 30 13:25:39 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 30 13:54:24 idm00 named[4166701]: client @0x7f11a404b548 10.73.240.42#49371: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 13:39:27 idmp0 named[1598691]: client @0x7f2d2803dc38 10.73.240.43#50229: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (23 distinct, 51 total) == Sep 30 13:46:24 inbound00.cs.umd.edu sshd-session[1453272]: error: maximum authentication attempts exceeded for root from 176.193.255.161 port 44204 ssh2 [preauth] Sep 30 13:46:47 inbound00.cs.umd.edu sshd-session[1453288]: error: maximum authentication attempts exceeded for root from 176.193.255.161 port 45390 ssh2 [preauth] Sep 30 13:47:11 inbound00.cs.umd.edu sshd-session[1453332]: error: maximum authentication attempts exceeded for root from 176.193.255.161 port 46624 ssh2 [preauth] Sep 30 13:47:21 inbound00.cs.umd.edu krb5_child[1453424]: Client 'admin@UMD.EDU' not found in Kerberos database [x16] Sep 30 13:47:43 inbound00.cs.umd.edu sshd-session[1453421]: error: maximum authentication attempts exceeded for admin from 176.193.255.161 port 48158 ssh2 [preauth] Sep 30 13:48:05 inbound00.cs.umd.edu sshd-session[1453468]: error: maximum authentication attempts exceeded for admin from 176.193.255.161 port 49438 ssh2 [preauth] Sep 30 13:48:43 inbound00.cs.umd.edu sshd-session[1453585]: error: maximum authentication attempts exceeded for invalid user oracle from 176.193.255.161 port 51486 ssh2 [preauth] Sep 30 13:49:04 inbound00.cs.umd.edu sshd-session[1453617]: error: maximum authentication attempts exceeded for invalid user oracle from 176.193.255.161 port 52598 ssh2 [preauth] Sep 30 13:49:37 inbound00.cs.umd.edu sshd-session[1453706]: error: maximum authentication attempts exceeded for invalid user usuario from 176.193.255.161 port 54334 ssh2 [preauth] Sep 30 13:49:57 inbound00.cs.umd.edu sshd-session[1453743]: error: maximum authentication attempts exceeded for invalid user usuario from 176.193.255.161 port 55488 ssh2 [preauth] Sep 30 13:50:27 inbound00.cs.umd.edu sshd-session[1453823]: error: maximum authentication attempts exceeded for invalid user test from 176.193.255.161 port 57054 ssh2 [preauth] Sep 30 13:50:52 inbound00.cs.umd.edu sshd-session[1454150]: error: maximum authentication attempts exceeded for invalid user test from 176.193.255.161 port 58146 ssh2 [preauth] Sep 30 13:51:25 inbound00.cs.umd.edu sshd-session[1454383]: error: maximum authentication attempts exceeded for invalid user user from 176.193.255.161 port 60108 ssh2 [preauth] Sep 30 13:51:47 inbound00.cs.umd.edu sshd-session[1454549]: error: maximum authentication attempts exceeded for invalid user user from 176.193.255.161 port 32928 ssh2 [preauth] Sep 30 13:52:34 inbound00.cs.umd.edu sshd-session[1454635]: error: maximum authentication attempts exceeded for invalid user ftpuser from 176.193.255.161 port 34990 ssh2 [preauth] Sep 30 13:52:59 inbound00.cs.umd.edu sshd-session[1454668]: error: maximum authentication attempts exceeded for invalid user ftpuser from 176.193.255.161 port 36340 ssh2 [preauth] Sep 30 13:53:24 inbound00.cs.umd.edu krb5_child[1454777]: Client 'test1@UMD.EDU' not found in Kerberos database [x14] Sep 30 13:53:42 inbound00.cs.umd.edu sshd-session[1454773]: error: maximum authentication attempts exceeded for test1 from 176.193.255.161 port 38550 ssh2 [preauth] Sep 30 13:54:11 inbound00.cs.umd.edu sshd-session[1454819]: error: maximum authentication attempts exceeded for test1 from 176.193.255.161 port 39850 ssh2 [preauth] Sep 30 13:54:40 inbound00.cs.umd.edu sshd-session[1454921]: error: maximum authentication attempts exceeded for invalid user test2 from 176.193.255.161 port 41794 ssh2 [preauth] Sep 30 13:55:00 inbound00.cs.umd.edu sshd-session[1454958]: error: maximum authentication attempts exceeded for invalid user test2 from 176.193.255.161 port 42842 ssh2 [preauth] Sep 30 13:55:33 inbound00.cs.umd.edu sshd-session[1455685]: error: maximum authentication attempts exceeded for invalid user ubuntu from 176.193.255.161 port 44506 ssh2 [preauth] Sep 30 13:55:57 inbound00.cs.umd.edu sshd-session[1456119]: error: maximum authentication attempts exceeded for invalid user ubuntu from 176.193.255.161 port 45670 ssh2 [preauth] == itmon02 (2 distinct, 4 total) == Sep 30 13:18:26 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] Sep 30 13:36:34 itmon02 systemd[1]: resmon.service: Supervising process 3528228 which is not our child. We'll most likely not notice when it exits. == krispykreme.cs.umd.edu (6 distinct, 6 total) == Sep 30 13:24:36 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 13:24:36 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 13:24:37 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 13:24:37 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 13:24:40 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 13:24:40 krispykreme.cs.umd.edu sshd-session[272877]: error: kex_protocol_error: type 30 seq 7 [preauth] == netman.cs.umd.edu (2 distinct, 4 total) == Sep 30 13:35:14 netman.cs.umd.edu systemd[1]: resmon.service: Supervising process 2623789 which is not our child. We'll most likely not notice when it exits. Sep 30 13:42:03 netman.cs.umd.edu switchinfo[2626332]: move_tftp_vyos_config: ERROR: git fetch failed (origin unreachable?); the commit above is local only [x3] == newhonors2 (1 distinct, 24 total) == Sep 30 13:13:03 newhonors2 dhcpcd[3369000]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 30 13:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 706) *** Sep 30 13:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 706) *** Sep 30 13:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 706, QN: 71/71, ET: 0) *** Sep 30 13:05:15 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 706, QN: 9173/9173, ET: 14) *** Sep 30 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 707) *** Sep 30 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 707, QN: 9237/9237, ET: 0) *** Sep 30 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 707) *** Sep 30 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 707, QN: 84/84, ET: 0) *** Sep 30 13:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 708) *** Sep 30 13:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 708) *** Sep 30 13:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 708, QN: 72/72, ET: 0) *** Sep 30 13:10:16 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 708, QN: 9253/9253, ET: 15) *** Sep 30 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 709) *** Sep 30 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 709, QN: 8665/8665, ET: 0) *** Sep 30 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 709) *** Sep 30 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 709, QN: 70/70, ET: 0) *** Sep 30 13:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 710) *** Sep 30 13:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 710) *** Sep 30 13:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 710, QN: 70/70, ET: 0) *** Sep 30 13:15:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 710, QN: 8400/8400, ET: 13) *** Sep 30 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 711) *** Sep 30 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 711, QN: 7962/7962, ET: 0) *** Sep 30 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 711) *** Sep 30 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 711, QN: 61/61, ET: 0) *** Sep 30 13:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 712) *** Sep 30 13:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 712) *** Sep 30 13:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 712, QN: 50/50, ET: 0) *** Sep 30 13:20:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 712, QN: 7706/7706, ET: 11) *** Sep 30 13:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 713) *** Sep 30 13:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 713, QN: 7452/7452, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 30 13:09:09 outbound00.cs.umd.edu python3[1281711]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Sep 30 13:13:06 outbound01.cs.umd.edu python3[3546632]: ldapdb [x6] Sep 30 13:14:57 outbound01.cs.umd.edu krb5_child[3546978]: Client 'ins@UMD.EDU' not found in Kerberos database Sep 30 13:33:43 outbound01.cs.umd.edu krb5_child[3551829]: Client 'admin@UMD.EDU' not found in Kerberos database == portal (1 distinct, 73 total) == Sep 30 13:05:32 portal setroubleshoot[3771961]: 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 [x73] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755744]: link_config: could not get ethtool features for veth2bc5525 Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755744]: Could not set offload features of veth2bc5525: No such device Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755831]: Could not generate persistent MAC address for veth24f0dbb: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755832]: Could not generate persistent MAC address for veth50807a6: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755835]: Could not generate persistent MAC address for veth4dd699a: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755836]: Could not generate persistent MAC address for vethf1e425a: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755855]: Could not generate persistent MAC address for veth145ede1: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755851]: Could not generate persistent MAC address for veth910b135: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755851]: Could not generate persistent MAC address for veth98d6702: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755855]: Could not generate persistent MAC address for veth5c648d7: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755870]: Could not generate persistent MAC address for veth0589d8d: No such file or directory Sep 30 13:17:03 sentry-docker00.cs.umd.edu systemd-udevd[2755874]: Could not generate persistent MAC address for veth88a9203: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765394]: link_config: could not get ethtool features for veth910b135 Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765394]: Could not set offload features of veth910b135: No such device Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765437]: Could not generate persistent MAC address for veth43afd9f: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765438]: Could not generate persistent MAC address for veth44112d2: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765441]: Could not generate persistent MAC address for vethc369e27: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765442]: Could not generate persistent MAC address for vethee981da: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765465]: Could not generate persistent MAC address for vethe986e0b: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765466]: Could not generate persistent MAC address for vetha8918b2: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765469]: Could not generate persistent MAC address for vethc709cfe: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765490]: Could not generate persistent MAC address for vetha168067: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765475]: Could not generate persistent MAC address for veth84e1adc: No such file or directory Sep 30 13:37:12 sentry-docker00.cs.umd.edu systemd-udevd[2765483]: Could not generate persistent MAC address for veth6592ea5: No such file or directory Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774791]: link_config: could not get ethtool features for vethc709cfe Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774791]: Could not set offload features of vethc709cfe: No such device Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774812]: Could not generate persistent MAC address for veth2c40cf3: No such file or directory Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774811]: Could not generate persistent MAC address for veth716b621: No such file or directory Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774837]: Could not generate persistent MAC address for veth767342b: No such file or directory Sep 30 13:57:20 sentry-docker00.cs.umd.edu systemd-udevd[2774838]: Could not generate persistent MAC address for vethee3f738: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 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 30 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 30 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 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 30 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 30 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 6 total) == Sep 30 13:13:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-f2 (1 distinct, 3 total) == Sep 30 13:05:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (10 distinct, 14 total) == Sep 30 13:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vYyd2M/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vYyd2M. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 Sep 30 13:06:46 submit26-b9-f3 setroubleshoot[281908]: 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 == submit26-b9-f4 (10 distinct, 14 total) == Sep 30 13:18:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 [x2] Sep 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 [x2] Sep 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tqRdxz/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tqRdxz. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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 30 13:24:50 submit26-b9-f4 setroubleshoot[3241913]: 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