Command: /usr/local/sbin/syslog-digest.py Time : 0.0440s Status : exited 0 Output : Syslog digest — 2026-09-16 19:05 EDT Processed 1,872 lines, filtered 1,522 (81%). 350 unknown (137 distinct) from 19 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 16 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-16T22:10:59.424627816Z" level=info msg="PurgeUploads starting: olderThan=2026-09-09 22:10:59.424513292 +0000 UTC m=+3803820.184441630, actuallyDelete=true" Sep 16 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-16T22:10:59.425235721Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 16 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-16T22:10:59.425260779Z" 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 Sep 16 18:46:49 b0b02.cs.umd.edu rustdesk[1880279]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 3 total) == Sep 16 18:20:57 biggulp.cs.umd.edu sshd-session[1844007]: pam_access(sshd:auth): access denied for user `root' from `158.173.89.129' Sep 16 18:20:59 biggulp.cs.umd.edu sshd-session[1844005]: error: PAM: Authentication failure for root from 158.173.89.129 Sep 16 18:28:42 biggulp.cs.umd.edu sshd-session[1845813]: pam_access(sshd:auth): access denied for user `rztao' from `71.178.33.59' == csfw00a (2 distinct, 135 total) == Sep 16 18:03:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133] Sep 16 18:36:23 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2] == galax (1 distinct, 1 total) == Sep 16 18:17:54 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND == hazfs.cs.umd.edu (1 distinct, 1 total) == Sep 16 18:12:01 hazfs.cs.umd.edu rpc.mountd[1586325]: /export/home exported to both 10.73.255.0/24 and 10.73.0.0/16, arbitrarily choosing options from first == idm00 (1 distinct, 1 total) == Sep 16 18:53:56 idm00 named[4166701]: client @0x7f11a93f3e08 10.73.240.42#60262: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 16 18:37:37 idmp0 named[1598691]: client @0x7f2d20030738 10.73.240.43#57744: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (3 distinct, 15 total) == Sep 16 18:47:17 inbound01.cs.umd.edu krb5_child[3108141]: Client 'admin@UMD.EDU' not found in Kerberos database [x12] Sep 16 18:50:22 inbound01.cs.umd.edu krb5_child[3108852]: Client 'massa@UMD.EDU' not found in Kerberos database Sep 16 18:54:21 inbound01.cs.umd.edu krb5_child[3109707]: Preauthentication failed [x2] == itmon02 (1 distinct, 1 total) == Sep 16 18:58:45 itmon02 sshd[1750555]: error: beginning MaxStartups throttling == krispykreme.cs.umd.edu (1 distinct, 1 total) == Sep 16 19:03:14 krispykreme.cs.umd.edu sshd-session[3003841]: pam_access(sshd:auth): access denied for user `pugh' from `108.45.150.204' == munin (2 distinct, 2 total) == Sep 16 19:03:11 munin sudo[3038995]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 16 19:03:11 munin sudo[3038995]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 16 18:13:03 newhonors2 dhcpcd[2733281]: dhcpcd is not running [x24] == ntop00 (50 distinct, 50 total) == Sep 16 18:05:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 42) *** Sep 16 18:05:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 42, QN: 3130/3130, ET: 0) *** Sep 16 18:07:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 67) *** Sep 16 18:07:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 67, QN: 0/0, ET: X) *** Sep 16 18:10:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 43) *** Sep 16 18:10:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 43, QN: 3295/3295, ET: 0) *** Sep 16 18:12:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 68) *** Sep 16 18:12:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 68, QN: 0/0, ET: X) *** Sep 16 18:15:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 44) *** Sep 16 18:15:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 44, QN: 2608/2608, ET: 0) *** Sep 16 18:17:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 69) *** Sep 16 18:17:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 69, QN: 0/0, ET: X) *** Sep 16 18:20:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 45) *** Sep 16 18:20:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 45, QN: 1592/1592, ET: 0) *** Sep 16 18:22:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 70) *** Sep 16 18:22:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 70, QN: 0/0, ET: X) *** Sep 16 18:25:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 46) *** Sep 16 18:25:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 46, QN: 1657/1657, ET: 0) *** Sep 16 18:27:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 71) *** Sep 16 18:27:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 71, QN: 0/0, ET: X) *** Sep 16 18:30:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 47) *** Sep 16 18:30:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 47, QN: 1826/1826, ET: 0) *** Sep 16 18:32:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 72) *** Sep 16 18:32:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 72, QN: 0/0, ET: X) *** Sep 16 18:35:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 48) *** Sep 16 18:35:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 48, QN: 1783/1783, ET: 0) *** Sep 16 18:37:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - START (PID: 73) *** Sep 16 18:37:01 ntop00 nfacctd[9667]: INFO ( default_print/print ): *** Purging cache - END (PID: 73, QN: 0/0, ET: X) *** Sep 16 18:40:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - START (PID: 49) *** Sep 16 18:40:01 ntop00 sfacctd[48024]: INFO ( default_print/print ): *** Purging cache - END (PID: 49, QN: 1650/1650, ET: 0) *** ... 20 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 16 18:09:09 outbound00.cs.umd.edu python3[757502]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 16 18:13:06 outbound01.cs.umd.edu python3[3017635]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 16 18:20:07 sentry-docker00.cs.umd.edu systemd-udevd[1762954]: link_config: could not get ethtool features for veth350ab34 Sep 16 18:20:07 sentry-docker00.cs.umd.edu systemd-udevd[1762954]: Could not set offload features of veth350ab34: No such device Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1762989]: Could not generate persistent MAC address for veth3e30455: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1762990]: Could not generate persistent MAC address for veth2b5a155: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1762993]: Could not generate persistent MAC address for veth36e84a9: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1762994]: Could not generate persistent MAC address for veth368cb4e: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763018]: Could not generate persistent MAC address for vethd77a1a5: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763017]: Could not generate persistent MAC address for vethd794555: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763017]: Could not generate persistent MAC address for veth797a47f: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763026]: Could not generate persistent MAC address for veth8b0295e: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763017]: Could not generate persistent MAC address for veth4e60020: No such file or directory Sep 16 18:20:08 sentry-docker00.cs.umd.edu systemd-udevd[1763042]: Could not generate persistent MAC address for vetha5df13e: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772375]: link_config: could not get ethtool features for veth797a47f Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772375]: Could not set offload features of veth797a47f: No such device Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772401]: Could not generate persistent MAC address for veth4374c39: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772402]: Could not generate persistent MAC address for veth99a41bb: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772424]: Could not generate persistent MAC address for veth92d483b: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772418]: Could not generate persistent MAC address for veth3ef37fe: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772424]: Could not generate persistent MAC address for veth37e12f6: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772418]: Could not generate persistent MAC address for veth98ee242: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772418]: Could not generate persistent MAC address for veth2bbc7b4: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772416]: Could not generate persistent MAC address for veth2f384f3: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772497]: Could not generate persistent MAC address for vethc5ddb01: No such file or directory Sep 16 18:40:16 sentry-docker00.cs.umd.edu systemd-udevd[1772499]: Could not generate persistent MAC address for vethe0ca0d8: No such file or directory Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781844]: link_config: could not get ethtool features for veth4374c39 Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781844]: Could not set offload features of veth4374c39: No such device Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781933]: link_config: could not get ethtool features for veth98ee242 Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781933]: Could not set offload features of veth98ee242: No such device Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781959]: Could not generate persistent MAC address for veth9c73725: No such file or directory Sep 16 19:00:24 sentry-docker00.cs.umd.edu systemd-udevd[1781960]: Could not generate persistent MAC address for vetha31b202: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 16 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 18:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 18:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 16 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 18:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 18:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 16 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 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 [x2] Sep 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 [x2] Sep 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.RwCaHw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.RwCaHw. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 [x2] Sep 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 16 18:25:52 submit26-b9-f1 setroubleshoot[1990259]: 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 [x2] Sep 16 18:25:53 submit26-b9-f1 setroubleshoot[1990259]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.jF46RB. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (9 distinct, 9 total) == Sep 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 Sep 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4SSfvY/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 Sep 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4SSfvY. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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 16 18:06:48 submit26-b9-f2 setroubleshoot[1124468]: 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