Command: /usr/local/sbin/syslog-digest.py Time : 0.0438s Status : exited 0 Output : Syslog digest — 2026-09-14 19:05 EDT Processed 1,973 lines, filtered 1,658 (84%). 315 unknown (76 distinct) from 16 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 14 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-14T22:10:59.423121132Z" level=info msg="PurgeUploads starting: olderThan=2026-09-07 22:10:59.423045464 +0000 UTC m=+3631020.182973792, actuallyDelete=true" Sep 14 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-14T22:10:59.423628935Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 14 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-14T22:10:59.423650857Z" 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 14 18:43:47 b0b02.cs.umd.edu rustdesk[1144001]: cannot open display: == csfw00a (1 distinct, 112 total) == Sep 14 18:04:28 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x112] == gle-dind04 (1 distinct, 1 total) == Sep 14 18:37:41 gle-dind04 lldpd[1171]: unable to send packet on real device for veth1ccdcb4: No such device or address == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 14 18:25:02 hazfs.cs.umd.edu pcp[3650542]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 14 18:53:53 idm00 named[4166701]: client @0x7f1198078018 10.73.240.42#59068: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 14 18:37:38 idmp0 named[1598691]: client @0x7f2d24000cc8 10.73.240.43#57094: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 36 total) == Sep 14 18:07:59 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x36] == newhonors2 (1 distinct, 24 total) == Sep 14 18:13:03 newhonors2 dhcpcd[2642152]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 14 18:09:09 outbound00.cs.umd.edu python3[76296]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 14 18:13:07 outbound01.cs.umd.edu python3[2335224]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405319]: link_config: could not get ethtool features for vethd4584a1 Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405319]: Could not set offload features of vethd4584a1: No such device Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405439]: Could not generate persistent MAC address for veth7666250: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405440]: Could not generate persistent MAC address for veth471fb85: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405450]: Could not generate persistent MAC address for vethde08367: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405451]: Could not generate persistent MAC address for veth36c02c1: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405468]: Could not generate persistent MAC address for vetha0a25d7: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405457]: Could not generate persistent MAC address for veth51c19e5: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405490]: Could not generate persistent MAC address for vethd3558a0: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405503]: Could not generate persistent MAC address for veth6d961e3: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405510]: Could not generate persistent MAC address for vethcbcff1e: No such file or directory Sep 14 18:20:18 sentry-docker00.cs.umd.edu systemd-udevd[405528]: Could not generate persistent MAC address for veth707b3f9: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414889]: link_config: could not get ethtool features for veth707b3f9 Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414889]: Could not set offload features of veth707b3f9: No such device Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414917]: Could not generate persistent MAC address for veth33a0d65: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414916]: Could not generate persistent MAC address for vethb88cd1b: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414920]: Could not generate persistent MAC address for veth23b8052: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414923]: Could not generate persistent MAC address for vethc16d444: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414944]: Could not generate persistent MAC address for vetheb155d7: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414945]: Could not generate persistent MAC address for veth3809352: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414963]: Could not generate persistent MAC address for veth1434d21: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414952]: Could not generate persistent MAC address for veth5faae34: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414954]: Could not generate persistent MAC address for veth4464598: No such file or directory Sep 14 18:40:26 sentry-docker00.cs.umd.edu systemd-udevd[414948]: Could not generate persistent MAC address for veth1e380c2: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424325]: Could not generate persistent MAC address for vethfa8e2fa: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424326]: Could not generate persistent MAC address for veth8abe114: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424355]: Could not generate persistent MAC address for vethd2ddfb2: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424356]: Could not generate persistent MAC address for vethaa50fb2: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424359]: Could not generate persistent MAC address for veth0ad22e4: No such file or directory Sep 14 19:00:34 sentry-docker00.cs.umd.edu systemd-udevd[424364]: Could not generate persistent MAC address for veth8e2acb5: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 14 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 14 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 14 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 14 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 14 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 14 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 14 18:34:43 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 17 total) == Sep 14 18:13:27 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] Sep 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Q2K0GG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Q2K0GG. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 14 18:25:51 submit26-b9-f1 setroubleshoot[1642323]: 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 (10 distinct, 17 total) == Sep 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Im51yu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Im51yu. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:06:47 submit26-b9-f2 setroubleshoot[784829]: 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 14 18:08:32 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f3 (1 distinct, 10 total) == Sep 14 18:08:19 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x10] == submit26-b9-f4 (1 distinct, 6 total) == Sep 14 18:15:40 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6]