Command: /usr/local/sbin/syslog-digest.py Time : 0.0436s Status : exited 0 Output : Syslog digest — 2026-09-15 19:05 EDT Processed 1,892 lines, filtered 1,584 (83%). 308 unknown (90 distinct) from 19 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 15 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-15T22:10:59.423895824Z" level=info msg="PurgeUploads starting: olderThan=2026-09-08 22:10:59.42382886 +0000 UTC m=+3717420.183757175, actuallyDelete=true" Sep 15 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-15T22:10:59.424347708Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 15 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-15T22:10:59.424366953Z" 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 15 18:45:18 b0b02.cs.umd.edu rustdesk[1510987]: cannot open display: == csfw00a (1 distinct, 128 total) == Sep 15 18:04:10 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x128] == hackerman (8 distinct, 8 total) == Sep 15 19:04:45 hackerman goa-identity-se[3464797]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM' Sep 15 19:04:45 hackerman gsd-screensaver[3451940]: Error releasing name org.freedesktop.ScreenSaver: The connection is closed Sep 15 19:04:45 hackerman gsd-datetime[3451938]: Error releasing name org.gnome.SettingsDaemon.Datetime: The connection is closed Sep 15 19:04:45 hackerman gsd-a11y-settin[3451942]: Error releasing name org.gnome.SettingsDaemon.A11ySettings: The connection is closed Sep 15 19:04:45 hackerman gsd-sound[3451941]: Error releasing name org.gnome.SettingsDaemon.Sound: The connection is closed Sep 15 19:04:45 hackerman vmware-user.desktop[3464926]: vmware-user: could not open /proc/fs/vmblock/dev Sep 15 19:04:45 hackerman gsd-usb-protect[3464865]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Sep 15 19:04:58 hackerman gnome-software[3464857]: Kind change on net.launchpad.Gnuclad from console-application to desktop-application is not OK == hazfs.cs.umd.edu (1 distinct, 1 total) == Sep 15 18:25:02 hazfs.cs.umd.edu pcp[2820371]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log == idm00 (1 distinct, 1 total) == Sep 15 18:53:55 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#51773: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 15 18:37:40 idmp0 named[1598691]: client @0x7f2d3802c908 10.73.240.43#65074: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Sep 15 18:37:41 inbound01.cs.umd.edu krb5_child[2762104]: Client 'admin@UMD.EDU' not found in Kerberos database == irb2156 (2 distinct, 2 total) == Sep 15 18:33:24 irb2156 kernel: hrtimer: interrupt took 27273 ns Sep 15 18:53:47 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 128.8.76.3. == itmon02 (1 distinct, 3 total) == Sep 15 18:19:00 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 14 total) == Sep 15 18:13:07 munin sudo[2496960]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7] Sep 15 18:13:07 munin sudo[2496960]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7] == newhonors2 (1 distinct, 24 total) == Sep 15 18:13:03 newhonors2 dhcpcd[2687491]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 15 18:09:09 outbound00.cs.umd.edu python3[416345]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 15 18:13:06 outbound01.cs.umd.edu python3[2675779]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 15 18:10:08 sentry-docker00.cs.umd.edu systemd-udevd[1079558]: link_config: could not get ethtool features for vethe0c0818 Sep 15 18:10:08 sentry-docker00.cs.umd.edu systemd-udevd[1079558]: Could not set offload features of vethe0c0818: No such device Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079610]: Could not generate persistent MAC address for veth126135b: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079611]: Could not generate persistent MAC address for veth59ae21c: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079614]: Could not generate persistent MAC address for veth1896f8b: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079615]: Could not generate persistent MAC address for vethb7c5054: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079627]: Could not generate persistent MAC address for vethd14b596: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079628]: Could not generate persistent MAC address for veth7e82ff8: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079619]: Could not generate persistent MAC address for veth4e4ffb4: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079636]: Could not generate persistent MAC address for veth4e04c14: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079619]: Could not generate persistent MAC address for veth9247f93: No such file or directory Sep 15 18:10:09 sentry-docker00.cs.umd.edu systemd-udevd[1079628]: Could not generate persistent MAC address for veth12819d7: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089064]: link_config: could not get ethtool features for veth126135b Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089064]: Could not set offload features of veth126135b: No such device Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089095]: Could not generate persistent MAC address for veth4c83bdc: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089096]: Could not generate persistent MAC address for vethd2609b0: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089099]: Could not generate persistent MAC address for veth1d98c07: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089100]: Could not generate persistent MAC address for veth5e625c4: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089124]: Could not generate persistent MAC address for veth9b77d0b: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089123]: Could not generate persistent MAC address for veth31c6779: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089145]: Could not generate persistent MAC address for veth56b2551: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089123]: Could not generate persistent MAC address for veth7f580c5: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089145]: Could not generate persistent MAC address for veth3fcbe3e: No such file or directory Sep 15 18:30:17 sentry-docker00.cs.umd.edu systemd-udevd[1089123]: Could not generate persistent MAC address for veth079b37d: No such file or directory Sep 15 18:50:25 sentry-docker00.cs.umd.edu systemd-udevd[1098555]: link_config: could not get ethtool features for veth31c6779 Sep 15 18:50:25 sentry-docker00.cs.umd.edu systemd-udevd[1098555]: Could not set offload features of veth31c6779: No such device Sep 15 18:50:26 sentry-docker00.cs.umd.edu systemd-udevd[1098675]: Could not generate persistent MAC address for vethd75fd2b: No such file or directory Sep 15 18:50:26 sentry-docker00.cs.umd.edu systemd-udevd[1098676]: Could not generate persistent MAC address for vethe4aca0c: No such file or directory Sep 15 18:50:26 sentry-docker00.cs.umd.edu systemd-udevd[1098679]: Could not generate persistent MAC address for veth3ad978a: No such file or directory Sep 15 18:50:26 sentry-docker00.cs.umd.edu systemd-udevd[1098680]: Could not generate persistent MAC address for veth5c57dc7: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 15 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 15 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 15 18:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 15 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 15 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 15 18:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 15 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 12 total) == Sep 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.s9S1nr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.s9S1nr. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 15 18:25:52 submit26-b9-f1 setroubleshoot[1846275]: 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 Sep 15 18:28:30 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (10 distinct, 15 total) == Sep 15 18:05:27 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.fzkLDc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.fzkLDc. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:47 submit26-b9-f2 setroubleshoot[978856]: 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 15 18:06:48 submit26-b9-f2 setroubleshoot[978856]: 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 == submit26-b9-f3 (1 distinct, 5 total) == Sep 15 18:05:22 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (1 distinct, 3 total) == Sep 15 18:18:56 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]