Command: /usr/local/sbin/syslog-digest.py Time : 7.4969s Status : exited 0 Output : Syslog digest — 2026-09-27 18:05 EDT Processed 119,704 lines, filtered 1,315 (1%). 118,389 unknown (142 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 18:03:22 b0b02.cs.umd.edu rustdesk[1783795]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 8 total) == Sep 27 17:27:53 biggulp.cs.umd.edu sshd-session[515400]: pam_access(sshd:auth): access denied for user `conniehg' from `73.133.150.131' Sep 27 17:50:29 biggulp.cs.umd.edu sudo[518829]: conniehg : user NOT in sudoers ; TTY=pts/3 ; PWD=/fs/junkfood/conniehg ; USER=root ; COMMAND=apt-get clean [x2] Sep 27 17:57:20 biggulp.cs.umd.edu sshd-session[521490]: error: send_error: write: Connection reset by peer [x5] == cheezit.cs.umd.edu (2 distinct, 2 total) == Sep 27 18:03:17 cheezit.cs.umd.edu krb5_child[3765970]: Preauthentication failed Sep 27 18:03:17 cheezit.cs.umd.edu sshd-session[3765962]: error: PAM: Authentication failure for psadeghi from 10.206.39.235 == frozone (1 distinct, 1 total) == Sep 27 17:35:47 frozone systemd-tmpfiles[2864770]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == gle-dind04 (7 distinct, 7 total) == Sep 27 17:37:11 gle-dind04 systemd-coredump[3369830]: Process 3369827 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369827:#012#0 0x000055d3b3f3b2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055d3b3f5a2c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055d3b3f59fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055d3b3f551d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055d3b3f550a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055d3b3f55065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055d3b3f79ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055d3b3f73651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055d3b3f6f7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055d3b3f52edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055d3b3f83b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055d3b3fbda47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:11 gle-dind04 systemd-coredump[3369837]: Process 3369835 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369835:#012#0 0x000055e59573a2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x000055e5957592c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x000055e595758fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000055e5957541d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000055e5957540a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000055e595754065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x000055e595778ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000055e595772651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x000055e59576e7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000055e595751edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000055e595782b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x000055e5957bca47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:12 gle-dind04 systemd-coredump[3369844]: Process 3369842 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369842:#012#0 0x0000559644e032ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000559644e222c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000559644e21fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000559644e1d1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000559644e1d0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000559644e1d065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000559644e41ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000559644e3b651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000559644e377a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000559644e1aedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000559644e4bb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000559644e85a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:12 gle-dind04 systemd-coredump[3369851]: Process 3369849 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369849:#012#0 0x0000563375a712ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563375a902c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563375a8ffc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563375a8b1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563375a8b0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563375a8b065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563375aafada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563375aa9651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563375aa57a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563375a88edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563375ab9b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563375af3a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:12 gle-dind04 systemd-coredump[3369860]: Process 3369856 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369856:#012#0 0x0000560b1f77a2ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000560b1f7992c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000560b1f798fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000560b1f7941d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000560b1f7940a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000560b1f794065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000560b1f7b8ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000560b1f7b2651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000560b1f7ae7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000560b1f791edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000560b1f7c2b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000560b1f7fca47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:12 gle-dind04 systemd-coredump[3369867]: Process 3369865 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369865:#012#0 0x0000563d259f92ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x0000563d25a182c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000563d25a17fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x0000563d25a131d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x0000563d25a130a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x0000563d25a13065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000563d25a37ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x0000563d25a31651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x0000563d25a2d7a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x0000563d25a10edd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x0000563d25a41b52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x0000563d25a7ba47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 Sep 27 17:37:12 gle-dind04 systemd-coredump[3369874]: Process 3369872 (ctr) of user 0 dumped core.#012#012Stack trace of thread 3369872:#012#0 0x00005627199242ee n/a (/usr/bin/ctr + 0xe2ee)#012#1 0x00005627199432c7 n/a (/usr/bin/ctr + 0x2d2c7)#012#2 0x0000562719942fc9 n/a (/usr/bin/ctr + 0x2cfc9)#012#3 0x000056271993e1d0 n/a (/usr/bin/ctr + 0x281d0)#012#4 0x000056271993e0a8 n/a (/usr/bin/ctr + 0x280a8)#012#5 0x000056271993e065 n/a (/usr/bin/ctr + 0x28065)#012#6 0x0000562719962ada n/a (/usr/bin/ctr + 0x4cada)#012#7 0x000056271995c651 n/a (/usr/bin/ctr + 0x46651)#012#8 0x00005627199587a5 n/a (/usr/bin/ctr + 0x427a5)#012#9 0x000056271993bedd n/a (/usr/bin/ctr + 0x25edd)#012#10 0x000056271996cb52 n/a (/usr/bin/ctr + 0x56b52)#012#11 0x00005627199a6a47 n/a (/usr/bin/ctr + 0x90a47)#012ELF object binary architecture: AMD x86-64 == idm00 (1 distinct, 1 total) == Sep 27 17:54:09 idm00 named[4166701]: client @0x7f11980696f8 10.73.240.42#61784: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 17:39:28 idmp0 named[1598691]: client @0x7f2d304493e8 10.73.240.43#50002: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 27 17:58:07 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == munin (2 distinct, 10 total) == Sep 27 17:08:29 munin sudo[361660]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Sep 27 17:08:29 munin sudo[361660]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == newhonors2 (1 distinct, 24 total) == Sep 27 17:13:03 newhonors2 dhcpcd[3239330]: dhcpcd is not running [x24] == ntop00 (58 distinct, 118228 total) == Sep 27 17:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 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 27 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1378) *** Sep 27 17:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1378, QN: 0/43, ET: 0) *** Sep 27 17:05:10 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 ] [x56409] Sep 27 17:05:10 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 ] [x53900] Sep 27 17:05:10 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 ] [x7378] Sep 27 17:05:11 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 ] [x231] Sep 27 17:05:11 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 ] [x231] Sep 27 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1381) *** Sep 27 17:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1381, QN: 68/68, ET: 0) *** Sep 27 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1381) *** Sep 27 17:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1381, QN: 13463/13463, ET: 0) *** Sep 27 17:14:01 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 ] [x7] Sep 27 17:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 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 27 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1382) *** Sep 27 17:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1382, QN: 0/13709, ET: 0) *** Sep 27 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1382) *** Sep 27 17:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1382, QN: 0/67, ET: 0) *** Sep 27 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1385) *** Sep 27 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1385) *** Sep 27 17:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1385, QN: 52/52, ET: 0) *** Sep 27 17:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1385, QN: 9283/9283, ET: 0) *** Sep 27 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1386) *** Sep 27 17:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1386, QN: 0/7412, ET: 0) *** Sep 27 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1386) *** Sep 27 17:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1386, QN: 0/53, ET: 0) *** Sep 27 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1389) *** Sep 27 17:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1389, QN: 7463/7463, ET: 0) *** ... 28 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 17:09:08 outbound00.cs.umd.edu python3[314722]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 27 17:13:06 outbound01.cs.umd.edu python3[2577922]: ldapdb [x6] Sep 27 17:51:59 outbound01.cs.umd.edu krb5_child[2586819]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829438]: link_config: could not get ethtool features for veth80b88a5 Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829438]: Could not set offload features of veth80b88a5: No such device Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829473]: Could not generate persistent MAC address for veth1dd8bc4: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829474]: Could not generate persistent MAC address for vethcbce0eb: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829477]: Could not generate persistent MAC address for vethbe594bc: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829478]: Could not generate persistent MAC address for veth7b91b0b: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829501]: Could not generate persistent MAC address for vethe2dda48: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829502]: Could not generate persistent MAC address for veth8fbd481: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829527]: Could not generate persistent MAC address for vethfb731f5: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829529]: Could not generate persistent MAC address for veth70e74dd: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829546]: Could not generate persistent MAC address for veth3aeeed3: No such file or directory Sep 27 17:08:46 sentry-docker00.cs.umd.edu systemd-udevd[829547]: Could not generate persistent MAC address for veth8484830: No such file or directory Sep 27 17:28:54 sentry-docker00.cs.umd.edu systemd-udevd[839145]: link_config: could not get ethtool features for veth1dd8bc4 Sep 27 17:28:54 sentry-docker00.cs.umd.edu systemd-udevd[839145]: Could not set offload features of veth1dd8bc4: No such device Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839177]: Could not generate persistent MAC address for vetha029513: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839178]: Could not generate persistent MAC address for veth5cc1547: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839181]: Could not generate persistent MAC address for veth82b18c4: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839182]: Could not generate persistent MAC address for veth3df56d9: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839194]: Could not generate persistent MAC address for vetha9ad4c8: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839195]: Could not generate persistent MAC address for veth8b27f58: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839209]: Could not generate persistent MAC address for veth7beb30e: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839211]: Could not generate persistent MAC address for vethe8d7c74: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839244]: Could not generate persistent MAC address for vethb284660: No such file or directory Sep 27 17:28:55 sentry-docker00.cs.umd.edu systemd-udevd[839234]: Could not generate persistent MAC address for vethb777964: No such file or directory Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848525]: link_config: could not get ethtool features for veth8b27f58 Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848525]: Could not set offload features of veth8b27f58: No such device Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848559]: Could not generate persistent MAC address for veth2e1f765: No such file or directory Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848560]: Could not generate persistent MAC address for vethc81afd6: No such file or directory Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848563]: Could not generate persistent MAC address for vethede2230: No such file or directory Sep 27 17:49:03 sentry-docker00.cs.umd.edu systemd-udevd[848564]: Could not generate persistent MAC address for veth13014ce: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 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 27 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 27 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 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 27 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 27 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ow6ety/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ow6ety. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 27 17:06:45 submit26-b9-f3 setroubleshoot[3752074]: 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 (9 distinct, 9 total) == Sep 27 17:24:48 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:48 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LD5Tuc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LD5Tuc. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: 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 27 17:24:49 submit26-b9-f4 setroubleshoot[2733763]: 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