Command: /usr/local/sbin/syslog-digest.py Time : 0.0485s Status : exited 0 Output : Syslog digest — 2026-10-03 02:05 EDT Processed 1,773 lines, filtered 1,357 (76%). 416 unknown (201 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 3 01:11:01 b0b02.cs.umd.edu rustdesk[3794895]: cannot open display: == cheezit.cs.umd.edu (4 distinct, 4 total) == Oct 3 01:30:13 cheezit.cs.umd.edu sshd-session[1483258]: pam_access(sshd:auth): access denied for user `admin' from `34.76.141.237' Oct 3 01:30:13 cheezit.cs.umd.edu krb5_child[1483260]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 3 01:30:13 cheezit.cs.umd.edu sshd-session[1483256]: error: PAM: System error for admin from 34.76.141.237 Oct 3 01:33:51 cheezit.cs.umd.edu sshd-session[1483960]: error: Protocol major versions differ: 2 vs. 1 == hazfs.cs.umd.edu (11 distinct, 66 total) == Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Oct 3 01:27:56 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Oct 3 01:54:36 idm00 named[4166701]: client @0x7f11a00432a8 10.73.240.42#62417: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 3 01:39:24 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#56687: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 3 01:18:29 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 24 total) == Oct 3 01:08:23 munin sudo[3148878]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x12] Oct 3 01:08:23 munin sudo[3148878]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x12] == newhonors2 (1 distinct, 24 total) == Oct 3 01:13:03 newhonors2 dhcpcd[3482577]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 3 01:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2146, QN: 4375/4375, ET: 7) *** Oct 3 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2147) *** Oct 3 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2147, QN: 4253/4253, ET: 0) *** Oct 3 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2147) *** Oct 3 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2147, QN: 54/54, ET: 0) *** Oct 3 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2148) *** Oct 3 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2148) *** Oct 3 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2148, QN: 58/58, ET: 0) *** Oct 3 01:10:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2148, QN: 4236/4236, ET: 6) *** Oct 3 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2149) *** Oct 3 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2149, QN: 4085/4085, ET: 0) *** Oct 3 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2149) *** Oct 3 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2149, QN: 59/59, ET: 0) *** Oct 3 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2150) *** Oct 3 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2150) *** Oct 3 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2150, QN: 61/61, ET: 0) *** Oct 3 01:15:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2150, QN: 3922/3922, ET: 6) *** Oct 3 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2151) *** Oct 3 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2151, QN: 3899/3899, ET: 0) *** Oct 3 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2151) *** Oct 3 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2151, QN: 62/62, ET: 0) *** Oct 3 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2152) *** Oct 3 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2152) *** Oct 3 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2152, QN: 57/57, ET: 0) *** Oct 3 01:20:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2152, QN: 3942/3942, ET: 6) *** Oct 3 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2153) *** Oct 3 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2153, QN: 3870/3870, ET: 0) *** Oct 3 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2153) *** Oct 3 01:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2153, QN: 55/55, ET: 0) *** Oct 3 01:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2154) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 3 01:09:08 outbound00.cs.umd.edu python3[2157003]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 3 01:13:05 outbound01.cs.umd.edu python3[228823]: ldapdb [x6] Oct 3 01:34:42 outbound01.cs.umd.edu krb5_child[233975]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == portal (1 distinct, 64 total) == Oct 3 01:06:01 portal setroubleshoot[367996]: 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 [x64] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259618]: link_config: could not get ethtool features for veth0c668a4 Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259618]: Could not set offload features of veth0c668a4: No such device Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259653]: Could not generate persistent MAC address for veth01e699f: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259654]: Could not generate persistent MAC address for veth1740d7c: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259657]: Could not generate persistent MAC address for veth4f79169: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259658]: Could not generate persistent MAC address for veth95fc9cd: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259681]: Could not generate persistent MAC address for vethf09c8e6: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259682]: Could not generate persistent MAC address for veth712f471: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259701]: Could not generate persistent MAC address for veth6e181f6: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259706]: Could not generate persistent MAC address for veth921c32e: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259704]: Could not generate persistent MAC address for veth03f2e02: No such file or directory Oct 3 01:22:01 sentry-docker00.cs.umd.edu systemd-udevd[259694]: Could not generate persistent MAC address for vethc7458d9: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269225]: link_config: could not get ethtool features for vethf09c8e6 Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269225]: Could not set offload features of vethf09c8e6: No such device Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269228]: Could not generate persistent MAC address for veth17c56ea: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269230]: Could not generate persistent MAC address for veth1f4a3cd: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269304]: Could not generate persistent MAC address for vethd45fc43: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269305]: Could not generate persistent MAC address for vethe099595: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269314]: Could not generate persistent MAC address for vethbd7a02d: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269315]: Could not generate persistent MAC address for veth153f93f: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269311]: Could not generate persistent MAC address for vethe3cf047: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269326]: Could not generate persistent MAC address for vethac9981e: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269374]: Could not generate persistent MAC address for veth6c86d9b: No such file or directory Oct 3 01:42:09 sentry-docker00.cs.umd.edu systemd-udevd[269377]: Could not generate persistent MAC address for veth47881ee: No such file or directory Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278619]: link_config: could not get ethtool features for veth153f93f Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278619]: Could not set offload features of veth153f93f: No such device Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278661]: Could not generate persistent MAC address for vethd786a93: No such file or directory Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278662]: Could not generate persistent MAC address for vethe53abe3: No such file or directory Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278685]: Could not generate persistent MAC address for veth9b4fb32: No such file or directory Oct 3 02:02:17 sentry-docker00.cs.umd.edu systemd-udevd[278684]: Could not generate persistent MAC address for veth874ed22: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 3 01: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 01: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 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 3 01: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 01: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 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 3 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (3 distinct, 4 total) == Oct 3 01:09:00 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 3 01:09:02 submit26-b9-f1 systemd-coredump[597137]: Process 597134 (release13) of user 1001 dumped core.#012#012Stack trace of thread 597134:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007f646c82a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f646c82a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:09:02 submit26-b9-f1 systemd-coredump[597147]: Process 597145 (release15) of user 1001 dumped core.#012#012Stack trace of thread 597145:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007ffa0de2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ffa0de2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (1 distinct, 1 total) == Oct 3 01:07:09 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (16 distinct, 21 total) == Oct 3 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3z0Dg6/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 3 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3z0Dg6. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 3 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:06:47 submit26-b9-f3 setroubleshoot[660109]: 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 01:08:10 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Oct 3 01:13:08 submit26-b9-f3 systemd-coredump[660644]: Process 660641 (release13) of user 1001 dumped core.#012#012Stack trace of thread 660641:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007ff6ab62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ff6ab62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:13:08 submit26-b9-f3 systemd-coredump[660655]: Process 660652 (release15) of user 1001 dumped core.#012#012Stack trace of thread 660652:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007f7534c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f7534c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:15:08 submit26-b9-f3 systemd-coredump[661142]: Process 661139 (release13) of user 1001 dumped core.#012#012Stack trace of thread 661139:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007f451e62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f451e62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:15:08 submit26-b9-f3 systemd-coredump[661151]: Process 661149 (release15) of user 1001 dumped core.#012#012Stack trace of thread 661149:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007f798302a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f798302a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:23:52 submit26-b9-f3 systemd-coredump[661522]: Process 661519 (release13) of user 1001 dumped core.#012#012Stack trace of thread 661519:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007f74a442a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f74a442a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:23:52 submit26-b9-f3 systemd-coredump[661532]: Process 661529 (release15) of user 1001 dumped core.#012#012Stack trace of thread 661529:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007fc56a02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fc56a02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (16 distinct, 19 total) == Oct 3 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.AU2veR/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 3 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.AU2veR. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 3 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:24:52 submit26-b9-f4 setroubleshoot[3516941]: 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 01:29:20 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Oct 3 01:29:23 submit26-b9-f4 systemd-coredump[3518228]: Process 3518225 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3518225:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007effa002a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007effa002a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:29:23 submit26-b9-f4 systemd-coredump[3518238]: Process 3518235 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3518235:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007fccf762a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fccf762a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:33:14 submit26-b9-f4 systemd-coredump[3518514]: Process 3518511 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3518511:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007f402b02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f402b02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:33:15 submit26-b9-f4 systemd-coredump[3518524]: Process 3518521 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3518521:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007efede62a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007efede62a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:35:13 submit26-b9-f4 systemd-coredump[3519011]: Process 3519008 (release13) of user 1001 dumped core.#012#012Stack trace of thread 3519008:#012#0 0x000000000040152d compact (release13 + 0x152d)#012#1 0x0000000000401201 main (release13 + 0x1201)#012#2 0x00007fa6e4e2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fa6e4e2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release13 + 0x1095)#012ELF object binary architecture: AMD x86-64 Oct 3 01:35:14 submit26-b9-f4 systemd-coredump[3519021]: Process 3519019 (release15) of user 1001 dumped core.#012#012Stack trace of thread 3519019:#012#0 0x000000000040153a compact (release15 + 0x153a)#012#1 0x0000000000401201 main (release15 + 0x1201)#012#2 0x00007fe78e42a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fe78e42a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x0000000000401095 _start (release15 + 0x1095)#012ELF object binary architecture: AMD x86-64
participants (1)
-
cron/syslog01.cs.umd.edu