Command: /usr/local/sbin/syslog-digest.py Time : 0.0556s Status : exited 0 Output : Syslog digest — 2026-10-03 14:05 EDT Processed 2,910 lines, filtered 2,459 (84%). 451 unknown (244 distinct) from 19 host(s). == b0b02.cs.umd.edu (2 distinct, 2 total) == Oct 3 13:11:46 b0b02.cs.umd.edu rustdesk[3977746]: cannot open display: Oct 3 13:12:30 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. == gle-dind02.cs.umd.edu (36 distinct, 36 total) == Oct 3 13:10:17 gle-dind02.cs.umd.edu systemd-udevd[515734]: Could not generate persistent MAC address for veth18ddde8: No such file or directory Oct 3 13:10:17 gle-dind02.cs.umd.edu systemd-udevd[515733]: Could not generate persistent MAC address for veth1e8bf05: No such file or directory Oct 3 13:10:18 gle-dind02.cs.umd.edu systemd-udevd[515834]: Could not generate persistent MAC address for vethd763412: No such file or directory Oct 3 13:10:18 gle-dind02.cs.umd.edu systemd-udevd[515835]: Could not generate persistent MAC address for vetha1fe3b5: No such file or directory Oct 3 13:10:19 gle-dind02.cs.umd.edu systemd-udevd[515933]: Could not generate persistent MAC address for vethf5992c1: No such file or directory Oct 3 13:10:19 gle-dind02.cs.umd.edu systemd-udevd[515934]: Could not generate persistent MAC address for veth1998aca: No such file or directory Oct 3 13:10:20 gle-dind02.cs.umd.edu systemd-udevd[516032]: Could not generate persistent MAC address for veth6b0655b: No such file or directory Oct 3 13:10:20 gle-dind02.cs.umd.edu systemd-udevd[516033]: Could not generate persistent MAC address for veth4068e32: No such file or directory Oct 3 13:10:20 gle-dind02.cs.umd.edu systemd-udevd[516127]: Could not generate persistent MAC address for veth80d66a5: No such file or directory Oct 3 13:10:20 gle-dind02.cs.umd.edu systemd-udevd[516128]: Could not generate persistent MAC address for veth1ab1d68: No such file or directory Oct 3 13:10:22 gle-dind02.cs.umd.edu systemd-udevd[516300]: Could not generate persistent MAC address for vethff3f0c4: No such file or directory Oct 3 13:10:22 gle-dind02.cs.umd.edu systemd-udevd[516301]: Could not generate persistent MAC address for veth6c12f72: No such file or directory Oct 3 13:10:23 gle-dind02.cs.umd.edu systemd-udevd[516411]: Could not generate persistent MAC address for veth36fb215: No such file or directory Oct 3 13:10:23 gle-dind02.cs.umd.edu systemd-udevd[516412]: Could not generate persistent MAC address for vethca91829: No such file or directory Oct 3 13:10:27 gle-dind02.cs.umd.edu systemd-udevd[516543]: Could not generate persistent MAC address for veth378c12d: No such file or directory Oct 3 13:10:27 gle-dind02.cs.umd.edu systemd-udevd[516544]: Could not generate persistent MAC address for vethfa40069: No such file or directory Oct 3 13:10:28 gle-dind02.cs.umd.edu systemd-udevd[516658]: Could not generate persistent MAC address for veth2d720b1: No such file or directory Oct 3 13:10:28 gle-dind02.cs.umd.edu systemd-udevd[516657]: Could not generate persistent MAC address for vetha5da462: No such file or directory Oct 3 14:02:51 gle-dind02.cs.umd.edu systemd-udevd[525477]: Could not generate persistent MAC address for veth28628e1: No such file or directory Oct 3 14:02:51 gle-dind02.cs.umd.edu systemd-udevd[525478]: Could not generate persistent MAC address for vethbe465e8: No such file or directory Oct 3 14:02:52 gle-dind02.cs.umd.edu systemd-udevd[525576]: Could not generate persistent MAC address for veth754f5ee: No such file or directory Oct 3 14:02:52 gle-dind02.cs.umd.edu systemd-udevd[525575]: Could not generate persistent MAC address for veth520d565: No such file or directory Oct 3 14:02:52 gle-dind02.cs.umd.edu systemd-udevd[525673]: Could not generate persistent MAC address for veth84a5d4f: No such file or directory Oct 3 14:02:52 gle-dind02.cs.umd.edu systemd-udevd[525674]: Could not generate persistent MAC address for vethd129312: No such file or directory Oct 3 14:02:54 gle-dind02.cs.umd.edu systemd-udevd[525771]: Could not generate persistent MAC address for veth0b552ba: No such file or directory Oct 3 14:02:54 gle-dind02.cs.umd.edu systemd-udevd[525772]: Could not generate persistent MAC address for veth762c20b: No such file or directory Oct 3 14:02:54 gle-dind02.cs.umd.edu systemd-udevd[525861]: Could not generate persistent MAC address for veth867951a: No such file or directory Oct 3 14:02:54 gle-dind02.cs.umd.edu systemd-udevd[525862]: Could not generate persistent MAC address for veth8261dfc: No such file or directory Oct 3 14:03:12 gle-dind02.cs.umd.edu systemd-udevd[526179]: Could not generate persistent MAC address for veth3ac7ce5: No such file or directory Oct 3 14:03:12 gle-dind02.cs.umd.edu systemd-udevd[526180]: Could not generate persistent MAC address for veth5687cfe: No such file or directory ... 6 more distinct messages not shown == gle-dind04 (5 distinct, 5 total) == Oct 3 13:59:44 gle-dind04 lldpd[1171]: unable to send packet on real device for veth2a310de: No such device or address Oct 3 14:00:05 gle-dind04 lldpd[1171]: unable to send packet on real device for veth353fff7: No such device or address Oct 3 14:00:08 gle-dind04 kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. Oct 3 14:00:08 gle-dind04 kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. Oct 3 14:01:30 gle-dind04 lldpd[1171]: unable to send packet on real device for veth4978cfa: No such device or address == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 3 13:33:25 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 3 13:54:37 idm00 named[4166701]: client @0x7f11a00279e8 10.73.240.42#54634: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 3 13:39:24 idmp0 named[1598691]: client @0x7f2d480190a8 10.73.240.43#62429: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 3 13:23:20 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 2 total) == Oct 3 14:03:18 munin sudo[3429459]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Oct 3 14:03:18 munin sudo[3429459]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Oct 3 13:13:03 newhonors2 dhcpcd[3505597]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 3 13:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2434) *** Oct 3 13:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2434, QN: 80/80, ET: 0) *** Oct 3 13:05:14 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2434, QN: 9066/9066, ET: 13) *** Oct 3 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2435) *** Oct 3 13:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2435, QN: 8766/8766, ET: 0) *** Oct 3 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2435) *** Oct 3 13:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2435, QN: 76/76, ET: 0) *** Oct 3 13:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2436) *** Oct 3 13:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2436) *** Oct 3 13:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2436, QN: 81/81, ET: 0) *** Oct 3 13:10:13 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2436, QN: 9067/9067, ET: 12) *** Oct 3 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2437) *** Oct 3 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2437) *** Oct 3 13:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2437, QN: 74/74, ET: 0) *** Oct 3 13:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2437, QN: 9813/9813, ET: 0) *** Oct 3 13:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2438) *** Oct 3 13:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2438) *** Oct 3 13:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2438, QN: 94/94, ET: 0) *** Oct 3 13:15:15 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2438, QN: 10745/10745, ET: 14) *** Oct 3 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2439) *** Oct 3 13:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2439, QN: 11243/11243, ET: 0) *** Oct 3 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2439) *** Oct 3 13:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2439, QN: 92/92, ET: 0) *** Oct 3 13:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2440) *** Oct 3 13:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2440) *** Oct 3 13:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2440, QN: 103/103, ET: 0) *** Oct 3 13:20:15 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2440, QN: 10366/10366, ET: 14) *** Oct 3 13:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2441) *** Oct 3 13:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2441, QN: 89/89, ET: 0) *** Oct 3 13:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2441) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 3 13:09:09 outbound00.cs.umd.edu python3[2326250]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 3 13:13:06 outbound01.cs.umd.edu python3[398736]: ldapdb [x6] == portal (1 distinct, 71 total) == Oct 3 13:05:06 portal setroubleshoot[529868]: 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 [x71] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591412]: link_config: could not get ethtool features for veth10f40a2 Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591412]: Could not set offload features of veth10f40a2: No such device Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591413]: link_config: could not set ethtool features for veth0ba6206 Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591413]: Could not set offload features of veth0ba6206: Operation not permitted Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591455]: Could not generate persistent MAC address for veth53b3747: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591456]: Could not generate persistent MAC address for vethdd01670: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591474]: Could not generate persistent MAC address for veth0be92d5: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591467]: Could not generate persistent MAC address for veth2f77222: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591484]: Could not generate persistent MAC address for veth4a6405c: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591483]: Could not generate persistent MAC address for vethd39502b: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591511]: Could not generate persistent MAC address for veth39de8d5: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591509]: Could not generate persistent MAC address for vetha1a6b41: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591507]: Could not generate persistent MAC address for veth991e624: No such file or directory Oct 3 13:06:52 sentry-docker00.cs.umd.edu systemd-udevd[591506]: Could not generate persistent MAC address for veth1200dbc: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[600982]: link_config: could not get ethtool features for veth0be92d5 Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[600982]: Could not set offload features of veth0be92d5: No such device Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601007]: Could not generate persistent MAC address for vethf0b1997: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601008]: Could not generate persistent MAC address for vethf4a49fd: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601026]: Could not generate persistent MAC address for veth7d8f9a3: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601030]: Could not generate persistent MAC address for veth1c33367: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601007]: Could not generate persistent MAC address for veth329969a: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601024]: Could not generate persistent MAC address for vethe0952ab: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601037]: Could not generate persistent MAC address for veth76528ed: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601038]: Could not generate persistent MAC address for veth709f6cd: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601077]: Could not generate persistent MAC address for veth3b51f7b: No such file or directory Oct 3 13:27:00 sentry-docker00.cs.umd.edu systemd-udevd[601083]: Could not generate persistent MAC address for veth5277a24: No such file or directory Oct 3 13:47:09 sentry-docker00.cs.umd.edu systemd-udevd[610307]: link_config: could not get ethtool features for veth3b51f7b Oct 3 13:47:09 sentry-docker00.cs.umd.edu systemd-udevd[610307]: Could not set offload features of veth3b51f7b: No such device Oct 3 13:47:09 sentry-docker00.cs.umd.edu systemd-udevd[610336]: Could not generate persistent MAC address for veth7f73045: No such file or directory Oct 3 13:47:09 sentry-docker00.cs.umd.edu systemd-udevd[610337]: Could not generate persistent MAC address for vethe13984a: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 3 13:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 3 13:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 3 13:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 3 13:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 3 13:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 3 13:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 3 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (4 distinct, 8 total) == Oct 3 13:13:11 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Oct 3 13:13:13 submit26-b9-f1 systemd-coredump[631382]: Process 631378 (release04) of user 1001 dumped core.#012#012Stack trace of thread 631378:#012#0 0x0000000000401436 right_align (release04 + 0x1436)#012#1 0x00000000004011f3 main (release04 + 0x11f3)#012#2 0x00007f799802a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f799802a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 13:15:09 submit26-b9-f1 systemd-coredump[631869]: Process 631865 (release04) of user 1001 dumped core.#012#012Stack trace of thread 631865:#012#0 0x0000000000401436 right_align (release04 + 0x1436)#012#1 0x00000000004011f3 main (release04 + 0x11f3)#012#2 0x00007fc5eea2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fc5eea2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 13:58:21 submit26-b9-f1 systemd-coredump[634516]: Process 634513 (release04) of user 1001 dumped core.#012#012Stack trace of thread 634513:#012#0 0x0000000000401362 right_align (release04 + 0x1362)#012#1 0x00000000004011d3 main (release04 + 0x11d3)#012#2 0x00007eff5b42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007eff5b42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401075 _start (release04 + 0x1075)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (3 distinct, 8 total) == Oct 3 13:18:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Oct 3 13:18:10 submit26-b9-f2 systemd-coredump[3955569]: Process 3955566 (release04) of user 1001 dumped core.#012#012Stack trace of thread 3955566:#012#0 0x0000000000401446 right_align (release04 + 0x1446)#012#1 0x0000000000401203 main (release04 + 0x1203)#012#2 0x00007f27db62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f27db62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release04 + 0x10a5)#012ELF object binary architecture: AMD x86-64 Oct 3 13:57:06 submit26-b9-f2 systemd-coredump[3958372]: Process 3958369 (release04) of user 1001 dumped core.#012#012Stack trace of thread 3958369:#012#0 0x0000000000401362 right_align (release04 + 0x1362)#012#1 0x00000000004011d3 main (release04 + 0x11d3)#012#2 0x00007efc6b82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007efc6b82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401075 _start (release04 + 0x1075)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (16 distinct, 23 total) == Oct 3 13:06:10 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] Oct 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZWEZQ1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZWEZQ1. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:47 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:06:48 submit26-b9-f3 setroubleshoot[701702]: 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 3 13:23:09 submit26-b9-f3 systemd-coredump[702446]: Process 702443 (release04) of user 1001 dumped core.#012#012Stack trace of thread 702443:#012#0 0x0000000000401436 right_align (release04 + 0x1436)#012#1 0x00000000004011f3 main (release04 + 0x11f3)#012#2 0x00007fb71902a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fb71902a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release04 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 13:41:41 submit26-b9-f3 systemd-coredump[704641]: Process 704638 (release04) of user 1001 dumped core.#012#012Stack trace of thread 704638:#012#0 0x0000000000401481 right_align (release04 + 0x1481)#012#1 0x0000000000401203 main (release04 + 0x1203)#012#2 0x00007f22e2c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f22e2c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release04 + 0x10a5)#012ELF object binary architecture: AMD x86-64 Oct 3 13:50:07 submit26-b9-f3 systemd-coredump[705219]: Process 705216 (release03) of user 1001 dumped core.#012#012Stack trace of thread 705216:#012#0 0x00007f1a6876677d __strlen_avx2_rtm (libc.so.6 + 0x16677d)#012#1 0x000000000040124c right_align (release03 + 0x124c)#012#2 0x00000000004011e5 main (release03 + 0x11e5)#012#3 0x00007f1a6862a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f1a6862a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release03 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 13:50:08 submit26-b9-f3 systemd-coredump[705247]: Process 705244 (release13) of user 1001 dumped core.#012#012Stack trace of thread 705244:#012#0 0x00007fd1edb6677d __strlen_avx2_rtm (libc.so.6 + 0x16677d)#012#1 0x00000000004013b0 compact (release13 + 0x13b0)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007fd1eda2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fd1eda2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 13:50:08 submit26-b9-f3 systemd-coredump[705257]: Process 705254 (release15) of user 1001 dumped core.#012#012Stack trace of thread 705254:#012#0 0x00007ff23576677d __strlen_avx2_rtm (libc.so.6 + 0x16677d)#012#1 0x00000000004013bd compact (release15 + 0x13bd)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007ff23562a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007ff23562a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 14:03:09 submit26-b9-f3 systemd-coredump[707086]: Process 707084 (release04) of user 1001 dumped core.#012#012Stack trace of thread 707084:#012#0 0x0000000000401481 right_align (release04 + 0x1481)#012#1 0x0000000000401203 main (release04 + 0x1203)#012#2 0x00007f8b3162a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f8b3162a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release04 + 0x10a5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (15 distinct, 16 total) == Oct 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.P7dIt7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.P7dIt7. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 3 13:24:52 submit26-b9-f4 setroubleshoot[3548351]: 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 Oct 3 13:28:20 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 3 13:28:23 submit26-b9-f4 systemd-coredump[3549158]: Process 3549155 (release03) of user 1001 dumped core.#012#012Stack trace of thread 3549155:#012#0 0x00007fb2a1eae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x000000000040124c right_align (release03 + 0x124c)#012#2 0x00000000004011e5 main (release03 + 0x11e5)#012#3 0x00007fb2a1e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb2a1e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release03 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 13:28:24 submit26-b9-f4 systemd-coredump[3549184]: Process 3549182 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3549182:#012#0 0x00007fb9d6eae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013b0 compact (release13 + 0x13b0)#012#2 0x00000000004011f1 main (release13 + 0x11f1)#012#3 0x00007fb9d6e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fb9d6e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release13 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 13:28:24 submit26-b9-f4 systemd-coredump[3549194]: Process 3549192 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3549192:#012#0 0x00007fe5e54ae0ea __strlen_sse2 (libc.so.6 + 0xae0ea)#012#1 0x00000000004013bd compact (release15 + 0x13bd)#012#2 0x00000000004011f1 main (release15 + 0x11f1)#012#3 0x00007fe5e542a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007fe5e542a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release15 + 0x1085)#012ELF object binary architecture: AMD x86-64 Oct 3 13:38:10 submit26-b9-f4 systemd-coredump[3549927]: Process 3549924 (release04) of user 1001 dumped core.#012#012Stack trace of thread 3549924:#012#0 0x0000000000401446 right_align (release04 + 0x1446)#012#1 0x0000000000401203 main (release04 + 0x1203)#012#2 0x00007fa6f822a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fa6f822a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release04 + 0x10a5)#012ELF object binary architecture: AMD x86-64 Oct 3 13:38:31 submit26-b9-f4 systemd-coredump[3549972]: Process 3549969 (release04) of user 1001 dumped core.#012#012Stack trace of thread 3549969:#012#0 0x0000000000401446 right_align (release04 + 0x1446)#012#1 0x0000000000401203 main (release04 + 0x1203)#012#2 0x00007f3be6e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f3be6e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (release04 + 0x10a5)#012ELF object binary architecture: AMD x86-64