Command: /usr/local/sbin/syslog-digest.py Time : 0.0491s Status : exited 0 Output : Syslog digest — 2026-09-30 19:05 EDT Processed 2,083 lines, filtered 1,730 (83%). 353 unknown (188 distinct) from 21 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 30 18:07:28 b0b02.cs.umd.edu rustdesk[2887766]: cannot open display: Sep 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-30T22:10:59.436089304Z" level=info msg="PurgeUploads starting: olderThan=2026-09-23 22:10:59.435990617 +0000 UTC m=+5013420.195918918, actuallyDelete=true" Sep 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-30T22:10:59.43673281Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 30 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-30T22:10:59.436754823Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1 == biggulp.cs.umd.edu (4 distinct, 5 total) == Sep 30 18:26:39 biggulp.cs.umd.edu sshd-session[1288045]: error: send_error: write: Connection reset by peer [x2] Sep 30 18:57:28 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): SSLSocket Disconnected from Cloud. Sep 30 18:58:00 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 30 18:58:00 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == hackerman (3 distinct, 3 total) == Sep 30 18:53:28 hackerman falcon-sensor-bpf[896]: CrowdStrike(4): SSLSocket Disconnected from Cloud. Sep 30 18:54:00 hackerman falcon-sensor-bpf[896]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 30 18:54:00 hackerman falcon-sensor-bpf[896]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == idm00 (1 distinct, 1 total) == Sep 30 18:54:23 idm00 named[4166701]: client @0x7f11986d0898 10.73.240.42#65415: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 18:39:27 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#58487: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (2 distinct, 4 total) == Sep 30 18:39:55 inbound01.cs.umd.edu krb5_child[3733292]: Client 'admin@UMD.EDU' not found in Kerberos database [x3] Sep 30 18:46:58 inbound01.cs.umd.edu krb5_child[3735162]: Preauthentication failed == itmon02 (1 distinct, 1 total) == Sep 30 18:23:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == munin (2 distinct, 10 total) == Sep 30 18:28:25 munin sudo[1960369]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Sep 30 18:28:25 munin sudo[1960369]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == newhonors2 (1 distinct, 24 total) == Sep 30 18:13:03 newhonors2 dhcpcd[3378341]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Sep 30 18:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 826) *** Sep 30 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 826) *** Sep 30 18:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 826, QN: 52/52, ET: 0) *** Sep 30 18:05:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 826, QN: 5867/5867, ET: 10) *** Sep 30 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 827) *** Sep 30 18:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 827, QN: 6186/6186, ET: 0) *** Sep 30 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 827) *** Sep 30 18:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 827, QN: 51/51, ET: 0) *** Sep 30 18:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 828) *** Sep 30 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 828) *** Sep 30 18:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 828, QN: 52/52, ET: 0) *** Sep 30 18:10:11 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 828, QN: 6284/6284, ET: 10) *** Sep 30 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 829) *** Sep 30 18:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 6020/6020, ET: 0) *** Sep 30 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 829) *** Sep 30 18:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 52/52, ET: 0) *** Sep 30 18:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) *** Sep 30 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) *** Sep 30 18:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 56/56, ET: 0) *** Sep 30 18:15:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 6131/6131, ET: 8) *** Sep 30 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 831) *** Sep 30 18:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 831, QN: 6265/6265, ET: 0) *** Sep 30 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 831) *** Sep 30 18:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 831, QN: 56/56, ET: 0) *** Sep 30 18:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 832) *** Sep 30 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 832) *** Sep 30 18:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 832, QN: 49/49, ET: 0) *** Sep 30 18:20:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 832, QN: 6215/6215, ET: 8) *** Sep 30 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 833) *** Sep 30 18:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 833, QN: 6211/6211, ET: 0) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 30 18:09:09 outbound00.cs.umd.edu python3[1351714]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 30 18:13:06 outbound01.cs.umd.edu python3[3617211]: ldapdb [x6] == portal (1 distinct, 65 total) == Sep 30 18:05:31 portal setroubleshoot[3835826]: 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 [x65] == quiss (1 distinct, 2 total) == Sep 30 18:17:37 quiss krb5_child[278011]: Preauthentication failed [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898603]: link_config: could not get ethtool features for vethbe4cf7f Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898603]: Could not set offload features of vethbe4cf7f: No such device Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898638]: Could not generate persistent MAC address for veth8b79b5a: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898639]: Could not generate persistent MAC address for veth46fede6: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898642]: Could not generate persistent MAC address for vethdda69af: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898643]: Could not generate persistent MAC address for vethbdc8577: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898666]: Could not generate persistent MAC address for vethb86ac69: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898667]: Could not generate persistent MAC address for vethc8860e9: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898679]: Could not generate persistent MAC address for vethcdd8a0d: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898670]: Could not generate persistent MAC address for vethd4ccf7f: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898717]: Could not generate persistent MAC address for vethc026b0b: No such file or directory Sep 30 18:19:08 sentry-docker00.cs.umd.edu systemd-udevd[2898724]: Could not generate persistent MAC address for veth96b51ae: No such file or directory Sep 30 18:39:16 sentry-docker00.cs.umd.edu systemd-udevd[2908030]: link_config: could not get ethtool features for veth8b79b5a Sep 30 18:39:16 sentry-docker00.cs.umd.edu systemd-udevd[2908030]: Could not set offload features of veth8b79b5a: No such device Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908057]: Could not generate persistent MAC address for vethd1a15ab: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908058]: Could not generate persistent MAC address for vethdd5643d: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908083]: Could not generate persistent MAC address for veth79bc70c: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908084]: Could not generate persistent MAC address for veth17a174d: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908102]: Could not generate persistent MAC address for veth30c6349: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908109]: Could not generate persistent MAC address for vetha82863f: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908111]: Could not generate persistent MAC address for vethd9d7417: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908112]: Could not generate persistent MAC address for veth418f0f2: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908111]: Could not generate persistent MAC address for veth68656aa: No such file or directory Sep 30 18:39:17 sentry-docker00.cs.umd.edu systemd-udevd[2908129]: Could not generate persistent MAC address for veth792ca09: No such file or directory Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917458]: link_config: could not get ethtool features for vethd1a15ab Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917458]: Could not set offload features of vethd1a15ab: No such device Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917490]: Could not generate persistent MAC address for vethcb55cb0: No such file or directory Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917491]: Could not generate persistent MAC address for veth136ba14: No such file or directory Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917494]: Could not generate persistent MAC address for veth96343ff: No such file or directory Sep 30 18:59:25 sentry-docker00.cs.umd.edu systemd-udevd[2917495]: Could not generate persistent MAC address for veth558a4b2: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 30 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 30 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 30 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 30 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 14 total) == Sep 30 18:10:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xRIGRI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xRIGRI. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Sep 30 18:25:59 submit26-b9-f1 setroubleshoot[353259]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (11 distinct, 19 total) == Sep 30 18:05:28 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 [x2] Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.98zyKm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 [x2] Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.98zyKm. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 30 18:06:53 submit26-b9-f2 setroubleshoot[3655337]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7 Sep 30 18:43:33 submit26-b9-f2 systemd-coredump[3657476]: Process 3657473 (release03) of user 1001 dumped core.#012#012Stack trace of thread 3657473:#012#0 0x00007f7b5d16f37c __strlen_evex (libc.so.6 + 0x16f37c)#012#1 0x000000000040129c right_align (release03 + 0x129c)#012#2 0x00000000004011e5 main (release03 + 0x11e5)#012#3 0x00007f7b5d02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#4 0x00007f7b5d02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#5 0x0000000000401085 _start (release03 + 0x1085)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (1 distinct, 8 total) == Sep 30 18:11:34 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f4 (1 distinct, 2 total) == Sep 30 18:25:29 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == yogurt (1 distinct, 6 total) == Sep 30 18:21:14 yogurt kernel: [drm:radeon_gem_va_update_vm [radeon]] *ERROR* Couldn't update BO_VA (-4) [x6]