Command: /usr/local/sbin/syslog-digest.py Time : 0.0418s Status : exited 0 Output : Syslog digest — 2026-09-08 03:05 EDT Processed 1,840 lines, filtered 1,536 (83%). 304 unknown (66 distinct) from 13 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 8 02:34:04 b0b02.cs.umd.edu rustdesk[2892274]: cannot open display: == csfw00a (2 distinct, 122 total) == Sep 8 02:03:55 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] Sep 8 02:58:02 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 8 02:25:04 hazfs.cs.umd.edu pcp[3503108]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 8 02:53:45 idm00 named[774780]: client @0x7fea0c01db28 10.73.240.42#62750: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 8 02:37:43 idmp0 named[2386583]: client @0x7f8244011328 10.73.240.43#58764: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 48 total) == Sep 8 02:08:14 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x48] == munin (2 distinct, 8 total) == Sep 8 02:22:50 munin sudo[2769087]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 8 02:22:50 munin sudo[2769087]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 8 02:13:03 newhonors2 dhcpcd[2337806]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 8 02:09:09 outbound00.cs.umd.edu python3[2000440]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Sep 8 02:13:06 outbound01.cs.umd.edu python3[60727]: ldapdb [x6] Sep 8 02:17:53 outbound01.cs.umd.edu krb5_child[61695]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 8 02:18:20 outbound01.cs.umd.edu sshd-session[61734]: error: Protocol major versions differ: 2 vs. 1 == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68424]: link_config: could not get ethtool features for veth3dc1fee Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68424]: Could not set offload features of veth3dc1fee: No such device Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68459]: Could not generate persistent MAC address for veth1cf1e5c: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68460]: Could not generate persistent MAC address for veth6a2778a: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68463]: Could not generate persistent MAC address for veth01f3b19: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68464]: Could not generate persistent MAC address for veth870ab64: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68487]: Could not generate persistent MAC address for veth196cb34: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68488]: Could not generate persistent MAC address for veth613fa91: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68514]: Could not generate persistent MAC address for vethc1b3b68: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68518]: Could not generate persistent MAC address for veth72443cd: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68549]: Could not generate persistent MAC address for veth2ab348e: No such file or directory Sep 8 02:13:57 sentry-docker00.cs.umd.edu systemd-udevd[68538]: Could not generate persistent MAC address for veth03ca5f6: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77932]: link_config: could not get ethtool features for veth01f3b19 Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77932]: Could not set offload features of veth01f3b19: No such device Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77966]: Could not generate persistent MAC address for veth5f3ece3: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77967]: Could not generate persistent MAC address for veth4568b21: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77992]: Could not generate persistent MAC address for veth92be71e: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77993]: Could not generate persistent MAC address for veth6936a0a: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[78011]: Could not generate persistent MAC address for veth343afdd: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[78016]: Could not generate persistent MAC address for vethf81a421: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77997]: Could not generate persistent MAC address for veth0835d5e: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77998]: Could not generate persistent MAC address for veth4b01de7: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[78010]: Could not generate persistent MAC address for veth98734f5: No such file or directory Sep 8 02:34:05 sentry-docker00.cs.umd.edu systemd-udevd[77992]: Could not generate persistent MAC address for vethcf43f93: No such file or directory Sep 8 02:54:13 sentry-docker00.cs.umd.edu systemd-udevd[87757]: link_config: could not get ethtool features for veth98734f5 Sep 8 02:54:13 sentry-docker00.cs.umd.edu systemd-udevd[87757]: Could not set offload features of veth98734f5: No such device Sep 8 02:54:14 sentry-docker00.cs.umd.edu systemd-udevd[87785]: Could not generate persistent MAC address for veth26c5baa: No such file or directory Sep 8 02:54:14 sentry-docker00.cs.umd.edu systemd-udevd[87786]: Could not generate persistent MAC address for veth31a831d: No such file or directory Sep 8 02:54:14 sentry-docker00.cs.umd.edu systemd-udevd[87803]: Could not generate persistent MAC address for veth0aa7854: No such file or directory Sep 8 02:54:14 sentry-docker00.cs.umd.edu systemd-udevd[87785]: Could not generate persistent MAC address for veth25525b5: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 8 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 8 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 8 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 8 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 8 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 8 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 8 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.j0aeAv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.j0aeAv. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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 8 02:25:48 submit26-b9-f1 setroubleshoot[667995]: 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