Command: /usr/local/sbin/syslog-digest.py Time : 0.0420s Status : exited 0 Output : Syslog digest — 2026-09-16 10:05 EDT Processed 1,937 lines, filtered 1,681 (86%). 256 unknown (85 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 16 09:46:16 b0b02.cs.umd.edu rustdesk[1741461]: cannot open display: == biggulp.cs.umd.edu (3 distinct, 3 total) == Sep 16 09:53:36 biggulp.cs.umd.edu sshd-session[1749266]: pam_access(sshd:auth): access denied for user `admin' from `158.173.89.118' Sep 16 09:53:37 biggulp.cs.umd.edu krb5_child[1749268]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 16 09:53:37 biggulp.cs.umd.edu sshd-session[1749264]: error: PAM: System error for admin from 158.173.89.118 == borealis (8 distinct, 10 total) == Sep 16 10:02:51 borealis goa-identity-se[309162]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM' Sep 16 10:02:51 borealis vmware-user.desktop[309291]: vmware-user: could not open /proc/fs/vmblock/dev Sep 16 10:02:52 borealis gsd-usb-protect[309282]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Sep 16 10:02:53 borealis gsd-color[309229]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2412M_7WFG152E149L_gdm_42 Sep 16 10:02:53 borealis gsd-color[309229]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2412M_4V35D7133HNU_gdm_42 Sep 16 10:02:53 borealis gnome-software[309307]: Only 0 apps for recent list, hiding [x3] Sep 16 10:03:41 borealis tracker-extract[310440]: tracker_module_manager_load_modules: assertion 'initialized == TRUE' failed Sep 16 10:04:13 borealis packagekitd[309186]: Failed to get cache filename for firefox == csfw00a (2 distinct, 105 total) == Sep 16 09:04:27 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x101] Sep 16 09:55:50 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == idm00 (1 distinct, 1 total) == Sep 16 09:54:03 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#65118: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 16 09:37:41 idmp0 named[1598691]: client @0x7f2d200357a8 10.73.240.43#55389: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 16 09:13:05 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == newhonors2 (1 distinct, 24 total) == Sep 16 09:13:02 newhonors2 dhcpcd[2716567]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 16 09:09:09 outbound00.cs.umd.edu python3[627371]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 16 09:13:06 outbound01.cs.umd.edu python3[2887028]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506900]: Could not generate persistent MAC address for veth2862dd7: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506901]: Could not generate persistent MAC address for vethd2f9bfb: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506904]: Could not generate persistent MAC address for vethadb616f: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506905]: Could not generate persistent MAC address for vethab4aba3: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506928]: Could not generate persistent MAC address for veth2323d17: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506929]: Could not generate persistent MAC address for veth8106d56: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506947]: Could not generate persistent MAC address for vethd745327: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506937]: Could not generate persistent MAC address for veth620f589: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506956]: Could not generate persistent MAC address for veth2303f0b: No such file or directory Sep 16 09:16:23 sentry-docker00.cs.umd.edu systemd-udevd[1506957]: Could not generate persistent MAC address for veth57e7ec3: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516395]: link_config: could not get ethtool features for vethadb616f Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516395]: Could not set offload features of vethadb616f: No such device Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516492]: link_config: could not get ethtool features for veth2862dd7 Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516492]: Could not set offload features of veth2862dd7: No such device Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516516]: Could not generate persistent MAC address for veth3b5ec4d: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516517]: Could not generate persistent MAC address for vethe9f0365: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516520]: Could not generate persistent MAC address for veth79219d6: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516532]: Could not generate persistent MAC address for veth21b5a9d: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516542]: Could not generate persistent MAC address for vethb06669a: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516516]: Could not generate persistent MAC address for vethc4aa8ea: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516546]: Could not generate persistent MAC address for vethbc1558c: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516547]: Could not generate persistent MAC address for veth0143f76: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516595]: Could not generate persistent MAC address for veth5ddcbea: No such file or directory Sep 16 09:36:31 sentry-docker00.cs.umd.edu systemd-udevd[1516597]: Could not generate persistent MAC address for veth5a08ff5: No such file or directory Sep 16 09:56:39 sentry-docker00.cs.umd.edu systemd-udevd[1525793]: link_config: could not get ethtool features for vethb06669a Sep 16 09:56:39 sentry-docker00.cs.umd.edu systemd-udevd[1525793]: Could not set offload features of vethb06669a: No such device Sep 16 09:56:39 sentry-docker00.cs.umd.edu systemd-udevd[1525879]: link_config: could not set ethtool features for veth79219d6 Sep 16 09:56:39 sentry-docker00.cs.umd.edu systemd-udevd[1525879]: Could not set offload features of veth79219d6: Operation not permitted Sep 16 09:56:40 sentry-docker00.cs.umd.edu systemd-udevd[1525909]: Could not generate persistent MAC address for veth58496d3: No such file or directory Sep 16 09:56:40 sentry-docker00.cs.umd.edu systemd-udevd[1525910]: Could not generate persistent MAC address for veth45eb261: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 16 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 16 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 16 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 16 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 16 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.07zqYi/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.07zqYi. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Sep 16 09:06:41 submit26-b9-f3 setroubleshoot[1278005]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 == submit26-b9-f4 (9 distinct, 9 total) == Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gCV41s/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gCV41s. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Sep 16 09:24:46 submit26-b9-f4 setroubleshoot[961469]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915 == whiffle.cs.umd.edu (2 distinct, 2 total) == Sep 16 09:43:42 whiffle.cs.umd.edu kernel: ipmi_si dmi-ipmi-si.0: BMC returned incorrect response, expected netfn b cmd 40, got netfn b cmd 2c Sep 16 09:43:42 whiffle.cs.umd.edu ipmievd[1428]: Get SEL Info command failed: Unspecified error