Command: /usr/local/sbin/syslog-digest.py Time : 0.0420s Status : exited 0 Output : Syslog digest — 2026-09-15 06:05 EDT Processed 1,995 lines, filtered 1,709 (85%). 286 unknown (64 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 15 05:44:29 b0b02.cs.umd.edu rustdesk[1312361]: cannot open display: == csfw00a (1 distinct, 120 total) == Sep 15 05:04:37 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x120] == gle-dind04 (2 distinct, 2 total) == Sep 15 05:34:05 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 15 05:34:05 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 15 05:48:32 grades01.cs.umd.edu puppet-agent[11711]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 15 05:25:01 hazfs.cs.umd.edu pcp[2919509]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 15 05:53:54 idm00 named[4166701]: client @0x7f11a8c67778 10.73.240.42#50322: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 15 05:37:38 idmp0 named[1598691]: client @0x7f2d2401e448 10.73.240.43#52270: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 36 total) == Sep 15 05:07:55 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x36] == munin (2 distinct, 4 total) == Sep 15 05:23:10 munin sudo[2217653]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 15 05:23:10 munin sudo[2217653]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 15 05:13:02 newhonors2 dhcpcd[2662800]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 15 05:09:09 outbound00.cs.umd.edu python3[232434]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 15 05:08:18 outbound01.cs.umd.edu python3[2489816]: ldapdb [x7] Sep 15 05:09:29 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == sentry-docker00.cs.umd.edu (24 distinct, 24 total) == Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[717987]: link_config: could not get ethtool features for veth313b8a8 Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[717987]: Could not set offload features of veth313b8a8: No such device Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[717993]: Could not generate persistent MAC address for veth42d2508: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[717991]: Could not generate persistent MAC address for veth0490e17: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718061]: Could not generate persistent MAC address for veth945eb66: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718059]: Could not generate persistent MAC address for veth8c5fb69: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718083]: Could not generate persistent MAC address for vethf445e1c: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718081]: Could not generate persistent MAC address for vethe2dbc3f: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718095]: Could not generate persistent MAC address for vethcf06a65: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718096]: Could not generate persistent MAC address for vethc09d0aa: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718145]: Could not generate persistent MAC address for veth920f88a: No such file or directory Sep 15 05:24:52 sentry-docker00.cs.umd.edu systemd-udevd[718146]: Could not generate persistent MAC address for veth78e488e: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727400]: link_config: could not get ethtool features for veth920f88a Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727400]: Could not set offload features of veth920f88a: No such device Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727434]: Could not generate persistent MAC address for veth943aef9: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727435]: Could not generate persistent MAC address for veth53d8b51: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727438]: Could not generate persistent MAC address for vethfb05612: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727439]: Could not generate persistent MAC address for vethcbe012a: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727434]: Could not generate persistent MAC address for veth195ff9e: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727445]: Could not generate persistent MAC address for veth68891d3: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727457]: Could not generate persistent MAC address for veth5ece4dd: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727434]: Could not generate persistent MAC address for veth0ddebe5: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727528]: Could not generate persistent MAC address for veth577ba4f: No such file or directory Sep 15 05:45:01 sentry-docker00.cs.umd.edu systemd-udevd[727529]: Could not generate persistent MAC address for veth301afe2: No such file or directory == strawberry (7 distinct, 38 total) == Sep 15 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 15 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 15 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 15 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 15 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 15 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 15 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GJvfLG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GJvfLG. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:06:41 submit26-b9-f3 setroubleshoot[1073261]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.c6VBNZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.c6VBNZ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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 15 05:24:45 submit26-b9-f4 setroubleshoot[818028]: 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