Command: /usr/local/sbin/syslog-digest.py Time : 0.1594s Status : exited 0 Output : Syslog digest — 2026-10-11 03:05 EDT Processed 6,223 lines, filtered 3,627 (58%). 2,596 unknown (197 distinct) from 22 host(s). == abuse (1 distinct, 348 total) == Oct 11 02:05:25 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 ] [x348] == atif01.cs.umd.edu (1 distinct, 1 total) == Oct 11 02:32:41 atif01.cs.umd.edu kernel: net_ratelimit: 8 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 11 02:22:24 b0b02.cs.umd.edu rustdesk[2539295]: cannot open display: == florence-ruohan (9 distinct, 15 total) == Oct 11 03:04:03 florence-ruohan nologin[344905]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN Oct 11 03:04:03 florence-ruohan pipewire[344902]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied [x2] Oct 11 03:04:03 florence-ruohan pipewire[344902]: mod.rt: could not set nice-level to -11: Permission denied Oct 11 03:04:04 florence-ruohan systemd-udevd[83597]: /etc/udev/rules.d/99-virtualgl-dri.rules:1 Unknown group 'vglusers', ignoring Oct 11 03:04:04 florence-ruohan pipewire-media-session[344903]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Oct 11 03:04:04 florence-ruohan pipewire-media-session[344903]: mod.rt: could not make thread 344925 realtime using RTKit: Permission denied Oct 11 03:04:04 florence-ruohan pipewire[344902]: mod.rt: could not make thread 344961 realtime using RTKit: Permission denied Oct 11 03:04:04 florence-ruohan pulseaudio[344904]: Failed to create secure directory (/nonexistent/.config/pulse): No such file or directory [x5] Oct 11 03:04:04 florence-ruohan puppet-agent[344912]: Certificate 'CN=florence-ruohan.cs.umd.edu' is revoked [x2] == idm00 (1 distinct, 1 total) == Oct 11 02:54:45 idm00 named[2816192]: client @0x7fd0e80a3d18 10.73.240.42#56682: update '73.10.in-addr.arpa/IN' denied == idmh1 (14 distinct, 168 total) == Oct 11 02:06:49 idmh1 check-named-alive[204426]: zone cs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:49 idmh1 check-named-alive[204487]: zone csdlabs.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:49 idmh1 check-named-alive[204548]: zone csic.umd.edu: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:49 idmh1 check-named-alive[204609]: zone 72.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:49 idmh1 check-named-alive[204675]: zone 73.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:50 idmh1 check-named-alive[204738]: zone 88.10.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:50 idmh1 check-named-alive[204799]: zone 28.172.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:50 idmh1 check-named-alive[204860]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:50 idmh1 check-named-alive[204921]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:50 idmh1 check-named-alive[204982]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:51 idmh1 check-named-alive[205043]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:51 idmh1 check-named-alive[205107]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:51 idmh1 check-named-alive[205170]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] Oct 11 02:06:51 idmh1 check-named-alive[205231]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691201 lags newest peer 1791695702 by 4501 (threshold 3600); not acting [x12] == idmp0 (15 distinct, 169 total) == Oct 11 02:07:33 idmp0 check-named-alive[90511]: zone cs.umd.edu: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 02:07:34 idmp0 check-named-alive[90572]: zone csdlabs.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:34 idmp0 check-named-alive[90633]: zone csic.umd.edu: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:34 idmp0 check-named-alive[90694]: zone 72.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:35 idmp0 check-named-alive[90755]: zone 73.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:35 idmp0 check-named-alive[90820]: zone 88.10.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:35 idmp0 check-named-alive[90881]: zone 28.172.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:35 idmp0 check-named-alive[90942]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:36 idmp0 check-named-alive[91003]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:36 idmp0 check-named-alive[91064]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 02:07:36 idmp0 check-named-alive[91125]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 02:07:37 idmp0 check-named-alive[91186]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691939 lags newest peer 1791695702 by 3763 (threshold 3600); not acting [x12] Oct 11 02:07:37 idmp0 check-named-alive[91247]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:07:37 idmp0 check-named-alive[91308]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691940 lags newest peer 1791695702 by 3762 (threshold 3600); not acting [x12] Oct 11 02:39:23 idmp0 named[61110]: client @0x7fd7e0001518 10.73.240.43#52750: update '73.10.in-addr.arpa/IN' denied == idmv0 (14 distinct, 159 total) == Oct 11 02:05:01 idmv0 check-named-alive[3430126]: zone 127.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 02:05:01 idmv0 check-named-alive[3430187]: zone 128.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 02:05:01 idmv0 check-named-alive[3430248]: zone 129.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 02:05:01 idmv0 check-named-alive[3430309]: zone 130.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 02:05:02 idmv0 check-named-alive[3430370]: zone 131.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x12] Oct 11 02:10:00 idmv0 check-named-alive[3431081]: zone cs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:00 idmv0 check-named-alive[3431142]: zone csdlabs.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:00 idmv0 check-named-alive[3431203]: zone csic.umd.edu: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:00 idmv0 check-named-alive[3431264]: zone 72.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:00 idmv0 check-named-alive[3431325]: zone 73.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:01 idmv0 check-named-alive[3431386]: zone 88.10.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:01 idmv0 check-named-alive[3431447]: zone 28.172.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:01 idmv0 check-named-alive[3431508]: zone 125.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] Oct 11 02:10:01 idmv0 check-named-alive[3431569]: zone 126.8.128.in-addr.arpa: local SOA serial 1791691202 lags newest peer 1791695702 by 4500 (threshold 3600); not acting [x11] == itmon02 (2 distinct, 5 total) == Oct 11 02:13:05 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] Oct 11 02:17:24 itmon02 systemd-timedated[536044]: /dev/rtc is busy. Is somebody keeping it open continuously? That's not a good idea... Returning a bogus RTC timestamp. == mcstic (2 distinct, 5 total) == Oct 11 02:36:37 mcstic krb5_child[1831346]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 11 02:36:43 mcstic sshd[1831341]: error: PAM: Authentication failure for admin from 35.205.210.70 == munin (2 distinct, 10 total) == Oct 11 02:48:17 munin sudo[3154329]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Oct 11 02:48:17 munin sudo[3154329]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == newhonors2 (1 distinct, 24 total) == Oct 11 02:13:03 newhonors2 dhcpcd[3859436]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 11 02:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6778) *** Oct 11 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6778) *** Oct 11 02:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6778, QN: 97/97, ET: 1) *** Oct 11 02:05:41 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6778, QN: 17142/17142, ET: 40) *** Oct 11 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6779) *** Oct 11 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6779, QN: 11351/11351, ET: 0) *** Oct 11 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6779) *** Oct 11 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6779, QN: 99/99, ET: 0) *** Oct 11 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6780) *** Oct 11 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6780) *** Oct 11 02:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6780, QN: 92/92, ET: 1) *** Oct 11 02:10:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6780, QN: 5998/5998, ET: 13) *** Oct 11 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6781) *** Oct 11 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6781, QN: 71/71, ET: 0) *** Oct 11 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6781) *** Oct 11 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6781, QN: 5215/5215, ET: 0) *** Oct 11 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6782) *** Oct 11 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6782, QN: 70/70, ET: 0) *** Oct 11 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6782) *** Oct 11 02:15:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6782, QN: 5238/5238, ET: 10) *** Oct 11 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6783) *** Oct 11 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6783, QN: 68/68, ET: 0) *** Oct 11 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 6783) *** Oct 11 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 6783, QN: 5536/5536, ET: 0) *** Oct 11 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6784) *** Oct 11 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6784) *** Oct 11 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6784, QN: 76/76, ET: 0) *** Oct 11 02:20:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6784, QN: 5471/5471, ET: 12) *** Oct 11 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 6785) *** Oct 11 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 6785, QN: 82/82, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 11 02:09:09 outbound00.cs.umd.edu python3[1472576]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 11 02:13:06 outbound01.cs.umd.edu python3[2949390]: ldapdb [x6] == strawberry (7 distinct, 38 total) == Oct 11 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 11 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 11 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 11 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 11 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit10-cln25 (5 distinct, 1514 total) == Oct 11 02:06:11 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 ] [x1180] Oct 11 02:06:11 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 ] [x329] Oct 11 02:25:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_check: Input/output error [x2] Oct 11 02:28:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmie_check: Input/output error [x2] Oct 11 02:30:01 submit10-cln25 systemd: Failed at step USER spawning /usr/libexec/pcp/bin/pmlogger_daily: Input/output error == submit26-b9-3 (1 distinct, 1 total) == Sep 13 08:15:07 submit26-b9-3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f1 (10 distinct, 10 total) == Oct 11 02:18:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.pPkMzv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.pPkMzv. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 Oct 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 11 02:26:03 submit26-b9-f1 setroubleshoot[2353711]: 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 == submit26-b9-f2 (10 distinct, 14 total) == Oct 11 02:05:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Oct 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 [x2] Oct 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 [x2] Oct 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.mFV4EY/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.mFV4EY. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 11 02:06:57 submit26-b9-f2 setroubleshoot[1442807]: 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 == submit26-b9-f3 (1 distinct, 3 total) == Oct 11 02:05:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (1 distinct, 1 total) == Oct 11 02:08:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL