Command: /usr/local/sbin/syslog-digest.py Time : 0.0415s Status : exited 0 Output : Syslog digest — 2026-09-07 03:05 EDT Processed 1,889 lines, filtered 1,582 (83%). 307 unknown (65 distinct) from 14 host(s). == amoeba (1 distinct, 1 total) == Sep 7 03:01:47 amoeba systemd[1]: resmon.service: Supervising process 4168182 which is not our child. We'll most likely not notice when it exits. == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 7 02:32:31 b0b02.cs.umd.edu rustdesk[2525548]: cannot open display: == csfw00a (1 distinct, 129 total) == Sep 7 02:03:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x129] == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 7 02:25:05 hazfs.cs.umd.edu pcp[142360]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 7 02:53:46 idm00 named[774780]: client @0x7fea0404d358 10.73.240.42#55974: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 7 02:37:43 idmp0 named[2386583]: client @0x7f8230020198 10.73.240.43#57866: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 50 total) == Sep 7 02:08:10 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x50] == kc00 (1 distinct, 1 total) == Sep 7 03:04:50 kc00 systemd[1]: resmon.service: Supervising process 239028 which is not our child. We'll most likely not notice when it exits. == newhonors2 (1 distinct, 24 total) == Sep 7 02:13:03 newhonors2 dhcpcd[2292365]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 7 02:09:08 outbound00.cs.umd.edu python3[1660632]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 7 02:13:06 outbound01.cs.umd.edu python3[3913799]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587308]: link_config: could not get ethtool features for veth726595e Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587308]: Could not set offload features of veth726595e: No such device Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587379]: link_config: could not get ethtool features for veth3665a95 Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587379]: Could not set offload features of veth3665a95: No such device Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587401]: Could not generate persistent MAC address for vethcdcd5b1: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587402]: Could not generate persistent MAC address for veth8e9b24b: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587405]: Could not generate persistent MAC address for veth26d9ed2: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587406]: Could not generate persistent MAC address for veth0109724: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587421]: Could not generate persistent MAC address for veth0d4c96c: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587416]: Could not generate persistent MAC address for veth99814ee: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587420]: Could not generate persistent MAC address for veth79d6a24: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587424]: Could not generate persistent MAC address for veth9de7115: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587520]: Could not generate persistent MAC address for veth0fd8af0: No such file or directory Sep 7 02:23:58 sentry-docker00.cs.umd.edu systemd-udevd[3587521]: Could not generate persistent MAC address for veth6eb349d: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597024]: link_config: could not get ethtool features for veth79d6a24 Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597024]: Could not set offload features of veth79d6a24: No such device Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597052]: Could not generate persistent MAC address for veth386fe31: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597053]: Could not generate persistent MAC address for veth1117ca3: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597071]: Could not generate persistent MAC address for vethc5c36d5: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597057]: Could not generate persistent MAC address for vethe401da3: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597080]: Could not generate persistent MAC address for veth65f9283: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597081]: Could not generate persistent MAC address for vethbc406ba: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597099]: Could not generate persistent MAC address for veth2d0b1c2: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597092]: Could not generate persistent MAC address for vethd851d6d: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597091]: Could not generate persistent MAC address for vethb7ce532: No such file or directory Sep 7 02:44:06 sentry-docker00.cs.umd.edu systemd-udevd[3597105]: Could not generate persistent MAC address for vethe10dbe3: No such file or directory Sep 7 03:04:14 sentry-docker00.cs.umd.edu systemd-udevd[3606717]: link_config: could not get ethtool features for veth2d0b1c2 Sep 7 03:04:14 sentry-docker00.cs.umd.edu systemd-udevd[3606717]: Could not set offload features of veth2d0b1c2: No such device Sep 7 03:04:15 sentry-docker00.cs.umd.edu systemd-udevd[3606746]: Could not generate persistent MAC address for vethdadd3d0: No such file or directory Sep 7 03:04:15 sentry-docker00.cs.umd.edu systemd-udevd[3606747]: Could not generate persistent MAC address for veth627fed7: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 7 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 7 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 7 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 7 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 7 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 7 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 7 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 7 02:25:47 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EW7pGX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EW7pGX. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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 7 02:25:48 submit26-b9-f1 setroubleshoot[523215]: 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
participants (1)
-
cron/syslog01.cs.umd.edu