Command: /usr/local/sbin/syslog-digest.py Time : 7.4267s Status : exited 0 Output : Syslog digest — 2026-09-26 18:05 EDT Processed 118,853 lines, filtered 1,472 (1%). 117,381 unknown (139 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 18:01:52 b0b02.cs.umd.edu rustdesk[1416015]: cannot open display: == frozone (1 distinct, 1 total) == Sep 26 17:35:46 frozone systemd-tmpfiles[2785556]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == gle-dind04 (7 distinct, 7 total) == Sep 26 17:37:11 gle-dind04 systemd-coredump[3143165]: Process 3143163 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143163:#012#0 0x0000558965dca2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000558965de92c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000558965de8fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000558965de41d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000558965de40a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000558965de4065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000558965e08ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000558965e02651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000558965dfe7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000558965de1edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000558965e12b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000558965e4ca47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:11 gle-dind04 systemd-coredump[3143173]: Process 3143171 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143171:#012#0 0x000055e81a82b2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055e81a84a2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055e81a849fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055e81a8451d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055e81a8450a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055e81a845065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055e81a869ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055e81a863651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055e81a85f7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055e81a842edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055e81a873b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055e81a8ada47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:12 gle-dind04 systemd-coredump[3143180]: Process 3143178 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143178:#012#0 0x00005579a327b2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005579a329a2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x00005579a3299fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x00005579a32951d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x00005579a32950a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x00005579a3295065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x00005579a32b9ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x00005579a32b3651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005579a32af7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x00005579a3292edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x00005579a32c3b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005579a32fda47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:12 gle-dind04 systemd-coredump[3143188]: Process 3143186 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143186:#012#0 0x0000563449a072ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563449a262c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563449a25fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563449a211d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563449a210a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563449a21065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563449a45ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563449a3f651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563449a3b7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563449a1eedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563449a4fb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563449a89a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:12 gle-dind04 systemd-coredump[3143195]: Process 3143193 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143193:#012#0 0x0000564a962a32ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000564a962c22c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000564a962c1fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000564a962bd1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000564a962bd0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000564a962bd065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000564a962e1ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000564a962db651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000564a962d77a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000564a962baedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000564a962ebb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000564a96325a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:12 gle-dind04 systemd-coredump[3143202]: Process 3143200 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143200:#012#0 0x0000563f125f82ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563f126172c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563f12616fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563f126121d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563f126120a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563f12612065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563f12636ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563f12630651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563f1262c7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563f1260fedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563f12640b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563f1267aa47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 26 17:37:12 gle-dind04 systemd-coredump[3143209]: Process 3143207 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3143207:#012#0 0x000055aed118e2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055aed11ad2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055aed11acfc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055aed11a81d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055aed11a80a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055aed11a8065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055aed11ccada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055aed11c6651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055aed11c27a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055aed11a5edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055aed11d6b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055aed1210a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 == idm00 (1 distinct, 1 total) == Sep 26 17:54:08 idm00 named[4166701]: client @0x7f11980696f8 10.73.240.42#49790: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 17:39:28 idmp0 named[1598691]: client @0x7f2d44011478 10.73.240.43#63408: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 26 17:28:11 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == munin (2 distinct, 20 total) == Sep 26 17:33:02 munin sudo[4041106]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10] Sep 26 17:33:02 munin sudo[4041106]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10] == newhonors2 (1 distinct, 24 total) == Sep 26 17:13:02 newhonors2 dhcpcd[3193871]: dhcpcd is not running [x24] == ntop00 (58 distinct, 117211 total) == Sep 26 17:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 17:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6] Sep 26 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 802) *** Sep 26 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 802, QN: 0/55, ET: 0) *** Sep 26 17:05:07 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x55962] Sep 26 17:05:07 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7380] Sep 26 17:05:07 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53339] Sep 26 17:05:07 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223] Sep 26 17:05:07 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223] Sep 26 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 805) *** Sep 26 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 805, QN: 8274/8274, ET: 0) *** Sep 26 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 805) *** Sep 26 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 805, QN: 55/55, ET: 0) *** Sep 26 17:14:03 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x12] Sep 26 17:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 17:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6] Sep 26 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 806) *** Sep 26 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 806, QN: 0/11482, ET: 0) *** Sep 26 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 806) *** Sep 26 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 806, QN: 0/51, ET: 0) *** Sep 26 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 809) *** Sep 26 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 809) *** Sep 26 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 809, QN: 59/59, ET: 0) *** Sep 26 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 809, QN: 16970/16970, ET: 0) *** Sep 26 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 810) *** Sep 26 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 810, QN: 0/58, ET: 0) *** Sep 26 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 810) *** Sep 26 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 810, QN: 0/16972, ET: 0) *** Sep 26 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 813) *** Sep 26 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 813, QN: 15591/15591, ET: 0) *** ... 28 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 17:09:09 outbound00.cs.umd.edu python3[4169402]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 12 total) == Sep 26 17:13:07 outbound01.cs.umd.edu python3[2236152]: ldapdb [x6] Sep 26 17:28:58 outbound01.cs.umd.edu krb5_child[2240374]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 26 17:38:45 outbound01.cs.umd.edu krb5_child[2242553]: Client 'backup@UMD.EDU' not found in Kerberos database [x2] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 26 17:18:55 sentry-docker00.cs.umd.edu systemd-udevd[155560]: link_config: could not get ethtool features for vethc6e21fc Sep 26 17:18:55 sentry-docker00.cs.umd.edu systemd-udevd[155560]: Could not set offload features of vethc6e21fc: No such device Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155593]: Could not generate persistent MAC address for veth01f0a3c: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155594]: Could not generate persistent MAC address for vethc388015: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155597]: Could not generate persistent MAC address for vethde49559: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155598]: Could not generate persistent MAC address for veth7a11789: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155611]: Could not generate persistent MAC address for vethe61a9bf: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155610]: Could not generate persistent MAC address for veth790305e: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155610]: Could not generate persistent MAC address for veth92f56bd: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155600]: Could not generate persistent MAC address for vethe0ab2c5: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155668]: Could not generate persistent MAC address for vethf76a300: No such file or directory Sep 26 17:18:56 sentry-docker00.cs.umd.edu systemd-udevd[155672]: Could not generate persistent MAC address for veth0e5aa32: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165239]: link_config: could not get ethtool features for veth01f0a3c Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165239]: Could not set offload features of veth01f0a3c: No such device Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165275]: Could not generate persistent MAC address for veth60ca094: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165276]: Could not generate persistent MAC address for vethd6c78ce: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165279]: Could not generate persistent MAC address for veth7bcc2f7: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165280]: Could not generate persistent MAC address for veth66422d1: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165286]: Could not generate persistent MAC address for veth882d87c: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165295]: Could not generate persistent MAC address for veth313dc4d: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165305]: Could not generate persistent MAC address for vethcfc076b: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165306]: Could not generate persistent MAC address for vethb345a09: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165320]: Could not generate persistent MAC address for veth4721839: No such file or directory Sep 26 17:39:04 sentry-docker00.cs.umd.edu systemd-udevd[165311]: Could not generate persistent MAC address for veth3d82b5c: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174650]: Could not generate persistent MAC address for veth2d0190e: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174651]: Could not generate persistent MAC address for vethd2d888e: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174654]: Could not generate persistent MAC address for vethf335ea8: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174655]: Could not generate persistent MAC address for vethb009203: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174654]: Could not generate persistent MAC address for vethf9af350: No such file or directory Sep 26 17:59:12 sentry-docker00.cs.umd.edu systemd-udevd[174655]: Could not generate persistent MAC address for veth09c07d6: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 26 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 26 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 26 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 26 17:18:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 10 total) == Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PEEKpg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.PEEKpg. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:06:45 submit26-b9-f3 setroubleshoot[3563633]: 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 26 17:20:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (10 distinct, 13 total) == Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.O6QBOK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.O6QBOK. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:24:48 submit26-b9-f4 setroubleshoot[2608143]: 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 26 17:38:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL