Command: /usr/local/sbin/syslog-digest.py Time : 0.0497s Status : exited 0 Output : Syslog digest — 2026-10-05 22:05 EDT Processed 1,744 lines, filtered 1,325 (75%). 419 unknown (264 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 5 21:15:20 b0b02.cs.umd.edu rustdesk[635664]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 3 total) == Oct 5 21:53:46 biggulp.cs.umd.edu sshd-session[2773945]: pam_access(sshd:auth): access denied for user `admin' from `178.178.222.56' Oct 5 21:53:47 biggulp.cs.umd.edu krb5_child[2773947]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 5 21:53:47 biggulp.cs.umd.edu sshd-session[2773939]: error: PAM: System error for admin from 178.178.222.56 == borealis (2 distinct, 2 total) == Oct 5 21:57:35 borealis kernel: Warning: Deprecated Driver is detected: nft_compat will not be maintained in a future major release and may be disabled Oct 5 21:57:35 borealis kernel: Warning: Deprecated Driver is detected: nft_compat_module_init will not be maintained in a future major release and may be disabled == gle-dind00.cs.umd.edu (45 distinct, 45 total) == Oct 5 21:19:25 gle-dind00.cs.umd.edu systemd-udevd[2315373]: Could not generate persistent MAC address for veth0f4487e: No such file or directory Oct 5 21:19:25 gle-dind00.cs.umd.edu systemd-udevd[2315374]: Could not generate persistent MAC address for veth934f0a9: No such file or directory Oct 5 21:19:26 gle-dind00.cs.umd.edu systemd-udevd[2315475]: Could not generate persistent MAC address for veth5c4f6f9: No such file or directory Oct 5 21:19:26 gle-dind00.cs.umd.edu systemd-udevd[2315476]: Could not generate persistent MAC address for vethc4e2ade: No such file or directory Oct 5 21:19:27 gle-dind00.cs.umd.edu systemd-udevd[2315576]: Could not generate persistent MAC address for veth61f48af: No such file or directory Oct 5 21:19:27 gle-dind00.cs.umd.edu systemd-udevd[2315577]: Could not generate persistent MAC address for vethaee4521: No such file or directory Oct 5 21:19:28 gle-dind00.cs.umd.edu systemd-udevd[2315673]: Could not generate persistent MAC address for vethb31a39b: No such file or directory Oct 5 21:19:28 gle-dind00.cs.umd.edu systemd-udevd[2315674]: Could not generate persistent MAC address for veth6bce58c: No such file or directory Oct 5 21:19:28 gle-dind00.cs.umd.edu systemd-udevd[2315761]: Could not generate persistent MAC address for veth1f78a72: No such file or directory Oct 5 21:19:28 gle-dind00.cs.umd.edu systemd-udevd[2315762]: Could not generate persistent MAC address for veth0f79b62: No such file or directory Oct 5 21:19:46 gle-dind00.cs.umd.edu systemd-udevd[2316078]: Could not generate persistent MAC address for vethca3701f: No such file or directory Oct 5 21:19:46 gle-dind00.cs.umd.edu systemd-udevd[2316077]: Could not generate persistent MAC address for veth2970cfd: No such file or directory Oct 5 21:19:47 gle-dind00.cs.umd.edu systemd-udevd[2316180]: Could not generate persistent MAC address for veth6dc0982: No such file or directory Oct 5 21:19:47 gle-dind00.cs.umd.edu systemd-udevd[2316181]: Could not generate persistent MAC address for veth26ba2e3: No such file or directory Oct 5 21:19:49 gle-dind00.cs.umd.edu systemd-udevd[2316355]: Could not generate persistent MAC address for veth0c35f77: No such file or directory Oct 5 21:19:49 gle-dind00.cs.umd.edu systemd-udevd[2316356]: Could not generate persistent MAC address for veth033648b: No such file or directory Oct 5 21:19:50 gle-dind00.cs.umd.edu systemd-udevd[2316467]: Could not generate persistent MAC address for veth31335ab: No such file or directory Oct 5 21:19:50 gle-dind00.cs.umd.edu systemd-udevd[2316466]: Could not generate persistent MAC address for veth3a701c9: No such file or directory Oct 5 21:27:28 gle-dind00.cs.umd.edu systemd-udevd[2319207]: Could not generate persistent MAC address for vethe8d812c: No such file or directory Oct 5 21:27:28 gle-dind00.cs.umd.edu systemd-udevd[2319208]: Could not generate persistent MAC address for veth2d55f8e: No such file or directory Oct 5 21:27:49 gle-dind00.cs.umd.edu systemd-udevd[2319349]: Could not generate persistent MAC address for veth063b4ce: No such file or directory Oct 5 21:27:49 gle-dind00.cs.umd.edu systemd-udevd[2319350]: Could not generate persistent MAC address for veth221a20c: No such file or directory Oct 5 21:36:24 gle-dind00.cs.umd.edu systemd-udevd[2320960]: Could not generate persistent MAC address for veth0fbabe0: No such file or directory Oct 5 21:36:24 gle-dind00.cs.umd.edu systemd-udevd[2320961]: Could not generate persistent MAC address for veth730f334: No such file or directory Oct 5 21:36:24 gle-dind00.cs.umd.edu systemd-udevd[2321062]: Could not generate persistent MAC address for veth41625cd: No such file or directory Oct 5 21:36:24 gle-dind00.cs.umd.edu systemd-udevd[2321063]: Could not generate persistent MAC address for veth6908964: No such file or directory Oct 5 21:36:25 gle-dind00.cs.umd.edu systemd-udevd[2321162]: Could not generate persistent MAC address for veth588c837: No such file or directory Oct 5 21:36:25 gle-dind00.cs.umd.edu systemd-udevd[2321163]: Could not generate persistent MAC address for veth5102f0b: No such file or directory Oct 5 21:36:26 gle-dind00.cs.umd.edu systemd-udevd[2321262]: Could not generate persistent MAC address for veth20702a2: No such file or directory Oct 5 21:36:26 gle-dind00.cs.umd.edu systemd-udevd[2321263]: Could not generate persistent MAC address for vethb3a69b4: No such file or directory ... 15 more distinct messages not shown == gle-dind02.cs.umd.edu (41 distinct, 41 total) == Oct 5 21:50:17 gle-dind02.cs.umd.edu systemd-udevd[1257828]: Could not generate persistent MAC address for veth088eb24: No such file or directory Oct 5 21:50:17 gle-dind02.cs.umd.edu systemd-udevd[1257829]: Could not generate persistent MAC address for veth205dd1e: No such file or directory Oct 5 21:50:18 gle-dind02.cs.umd.edu systemd-udevd[1257927]: Could not generate persistent MAC address for veth412ffb6: No such file or directory Oct 5 21:50:18 gle-dind02.cs.umd.edu systemd-udevd[1257928]: Could not generate persistent MAC address for veth0949395: No such file or directory Oct 5 21:50:19 gle-dind02.cs.umd.edu systemd-udevd[1258026]: Could not generate persistent MAC address for veth50eb914: No such file or directory Oct 5 21:50:19 gle-dind02.cs.umd.edu systemd-udevd[1258027]: Could not generate persistent MAC address for veth2dfa0a0: No such file or directory Oct 5 21:50:20 gle-dind02.cs.umd.edu systemd-udevd[1258125]: Could not generate persistent MAC address for vethd4448cc: No such file or directory Oct 5 21:50:20 gle-dind02.cs.umd.edu systemd-udevd[1258124]: Could not generate persistent MAC address for vethbf08732: No such file or directory Oct 5 21:50:20 gle-dind02.cs.umd.edu systemd-udevd[1258213]: Could not generate persistent MAC address for veth7571008: No such file or directory Oct 5 21:50:20 gle-dind02.cs.umd.edu systemd-udevd[1258214]: Could not generate persistent MAC address for veth913811c: No such file or directory Oct 5 21:50:38 gle-dind02.cs.umd.edu systemd-udevd[1258501]: Could not generate persistent MAC address for vethd94994c: No such file or directory Oct 5 21:50:38 gle-dind02.cs.umd.edu systemd-udevd[1258502]: Could not generate persistent MAC address for vethf6cc658: No such file or directory Oct 5 21:50:39 gle-dind02.cs.umd.edu systemd-udevd[1258600]: Could not generate persistent MAC address for vethb9f8e36: No such file or directory Oct 5 21:50:39 gle-dind02.cs.umd.edu systemd-udevd[1258601]: Could not generate persistent MAC address for veth9427fee: No such file or directory Oct 5 21:50:41 gle-dind02.cs.umd.edu systemd-udevd[1258779]: Could not generate persistent MAC address for vethe20f652: No such file or directory Oct 5 21:50:41 gle-dind02.cs.umd.edu systemd-udevd[1258780]: Could not generate persistent MAC address for veth45cbb79: No such file or directory Oct 5 21:50:42 gle-dind02.cs.umd.edu systemd-udevd[1258891]: Could not generate persistent MAC address for veth299e728: No such file or directory Oct 5 21:50:42 gle-dind02.cs.umd.edu systemd-udevd[1258892]: Could not generate persistent MAC address for vethd1d007d: No such file or directory Oct 5 21:56:12 gle-dind02.cs.umd.edu systemd-udevd[1260137]: Could not generate persistent MAC address for veth7f1e92e: No such file or directory Oct 5 21:56:12 gle-dind02.cs.umd.edu systemd-udevd[1260138]: Could not generate persistent MAC address for vetha26439d: No such file or directory Oct 5 21:56:13 gle-dind02.cs.umd.edu lldpd[973]: unable to send packet on real device for vethd1d007d: No such device or address Oct 5 21:56:25 gle-dind02.cs.umd.edu systemd-udevd[1260255]: Could not generate persistent MAC address for veth7019b05: No such file or directory Oct 5 21:56:25 gle-dind02.cs.umd.edu systemd-udevd[1260256]: Could not generate persistent MAC address for veth6840e77: No such file or directory Oct 5 22:02:21 gle-dind02.cs.umd.edu systemd-udevd[1261516]: Could not generate persistent MAC address for veth801822b: No such file or directory Oct 5 22:02:21 gle-dind02.cs.umd.edu systemd-udevd[1261517]: Could not generate persistent MAC address for vethc5464d2: No such file or directory Oct 5 22:02:21 gle-dind02.cs.umd.edu systemd-udevd[1261613]: Could not generate persistent MAC address for vethe0572de: No such file or directory Oct 5 22:02:21 gle-dind02.cs.umd.edu systemd-udevd[1261614]: Could not generate persistent MAC address for veth7e7cd19: No such file or directory Oct 5 22:02:22 gle-dind02.cs.umd.edu systemd-udevd[1261712]: Could not generate persistent MAC address for vethd012c91: No such file or directory Oct 5 22:02:22 gle-dind02.cs.umd.edu systemd-udevd[1261711]: Could not generate persistent MAC address for vethee19cdd: No such file or directory Oct 5 22:02:23 gle-dind02.cs.umd.edu systemd-udevd[1261810]: Could not generate persistent MAC address for vethde3bfcd: No such file or directory ... 11 more distinct messages not shown == gle-dind04 (4 distinct, 4 total) == Oct 5 21:34:48 gle-dind04 lldpd[1171]: unable to send packet on real device for vethcb9f7d0: No such device or address Oct 5 21:47:55 gle-dind04 lldpd[1171]: unable to send packet on real device for veth87473ae: No such device or address Oct 5 21:48:11 gle-dind04 lldpd[1171]: unable to send packet on real device for vethbfa5725: No such device or address Oct 5 21:58:34 gle-dind04 lldpd[1171]: unable to send packet on real device for vethc0b8f83: No such device or address == idm00 (1 distinct, 1 total) == Oct 5 21:54:39 idm00 named[4166701]: client @0x7f11a4064588 10.73.240.42#64881: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 5 21:39:23 idmp0 named[1598691]: client @0x7f2d30015348 10.73.240.43#56338: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Oct 5 21:07:57 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == munin (2 distinct, 12 total) == Oct 5 21:38:28 munin sudo[440883]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Oct 5 21:38:28 munin sudo[440883]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Oct 5 21:13:03 newhonors2 dhcpcd[3611219]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 5 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3778) *** Oct 5 21:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3778, QN: 56/56, ET: 1) *** Oct 5 21:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3778, QN: 5610/5610, ET: 10) *** Oct 5 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3779) *** Oct 5 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3779, QN: 7004/7004, ET: 0) *** Oct 5 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3779) *** Oct 5 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3779, QN: 64/64, ET: 0) *** Oct 5 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3780) *** Oct 5 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3780) *** Oct 5 21:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3780, QN: 73/73, ET: 1) *** Oct 5 21:10:12 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3780, QN: 6912/6912, ET: 11) *** Oct 5 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3781) *** Oct 5 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3781, QN: 6021/6021, ET: 0) *** Oct 5 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3781) *** Oct 5 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3781, QN: 79/79, ET: 0) *** Oct 5 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3782) *** Oct 5 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3782) *** Oct 5 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3782, QN: 70/70, ET: 0) *** Oct 5 21:15:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3782, QN: 5780/5780, ET: 8) *** Oct 5 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3783) *** Oct 5 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3783, QN: 57/57, ET: 0) *** Oct 5 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3783) *** Oct 5 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3783, QN: 5261/5261, ET: 0) *** Oct 5 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3784) *** Oct 5 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3784) *** Oct 5 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3784, QN: 58/58, ET: 0) *** Oct 5 21:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3784, QN: 5055/5055, ET: 7) *** Oct 5 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3785) *** Oct 5 21:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3785, QN: 56/56, ET: 0) *** Oct 5 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3785) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 5 21:09:09 outbound00.cs.umd.edu python3[3113719]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 5 21:13:06 outbound01.cs.umd.edu python3[1187794]: ldapdb [x6] == portal (1 distinct, 77 total) == Oct 5 21:05:16 portal setroubleshoot[1276375]: 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 [x77] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168677]: link_config: could not get ethtool features for vethed79db0 Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168677]: Could not set offload features of vethed79db0: No such device Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168705]: Could not generate persistent MAC address for vethc909a8c: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168706]: Could not generate persistent MAC address for vethe16a7cc: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168709]: Could not generate persistent MAC address for veth0d11040: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168710]: Could not generate persistent MAC address for veth0134218: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168734]: Could not generate persistent MAC address for vethf9fdaf9: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168733]: Could not generate persistent MAC address for veth031b3d9: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168759]: Could not generate persistent MAC address for vetha9e55d7: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168761]: Could not generate persistent MAC address for veth0880f8b: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168801]: Could not generate persistent MAC address for veth76012e8: No such file or directory Oct 5 21:10:06 sentry-docker00.cs.umd.edu systemd-udevd[2168795]: Could not generate persistent MAC address for veth245df93: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178303]: link_config: could not get ethtool features for veth0d11040 Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178303]: Could not set offload features of veth0d11040: No such device Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178349]: Could not generate persistent MAC address for veth125f608: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178350]: Could not generate persistent MAC address for vethc72c232: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178356]: Could not generate persistent MAC address for veth5f98202: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178363]: Could not generate persistent MAC address for veth50b532c: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178374]: Could not generate persistent MAC address for vetheb903bd: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178376]: Could not generate persistent MAC address for veth89a5e2f: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178376]: Could not generate persistent MAC address for vethe4d856b: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178374]: Could not generate persistent MAC address for vethafc63d6: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178369]: Could not generate persistent MAC address for vethbd51faf: No such file or directory Oct 5 21:30:14 sentry-docker00.cs.umd.edu systemd-udevd[2178373]: Could not generate persistent MAC address for veth1c4b1dc: No such file or directory Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187874]: link_config: could not get ethtool features for veth125f608 Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187874]: Could not set offload features of veth125f608: No such device Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187903]: Could not generate persistent MAC address for veth9c51c0d: No such file or directory Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187904]: Could not generate persistent MAC address for vethaa16797: No such file or directory Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187907]: Could not generate persistent MAC address for veth8ef7055: No such file or directory Oct 5 21:50:22 sentry-docker00.cs.umd.edu systemd-udevd[2187917]: Could not generate persistent MAC address for vethc028388: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 5 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 5 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 5 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Oct 5 21:40:03 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (10 distinct, 10 total) == Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TE4HZb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TE4HZb. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 21:06:48 submit26-b9-f3 setroubleshoot[1246360]: 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 Oct 5 22:00:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (9 distinct, 9 total) == Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gM2jUp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gM2jUp. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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 Oct 5 21:24:53 submit26-b9-f4 setroubleshoot[3959063]: 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