Command: /usr/local/sbin/syslog-digest.py Time : 0.0464s Status : exited 0 Output : Syslog digest — 2026-09-13 18:05 EDT Processed 2,090 lines, filtered 1,685 (80%). 405 unknown (82 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 13 17:42:14 b0b02.cs.umd.edu rustdesk[762119]: cannot open display: == csfw00a (1 distinct, 122 total) == Sep 13 17:04:08 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122] == frozone (1 distinct, 1 total) == Sep 13 17:35:32 frozone systemd-tmpfiles[1534957]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == galax (2 distinct, 80 total) == Sep 13 17:05:42 galax boltd[2250]: watchdog: failed to send ping: failed to send msg: Connection refused [x40] Sep 13 17:05:42 galax systemd-journald[670]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [x40] == gle-dind04 (1 distinct, 1 total) == Sep 13 17:31:56 gle-dind04 lldpd[22022]: unable to send packet on real device for vethb4a9a1e: No such device or address == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 13 17:25:03 hazfs.cs.umd.edu pcp[4154106]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 13 17:53:53 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#63066: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 13 17:37:38 idmp0 named[1598691]: client @0x7f2d1c03fa28 10.73.240.43#57713: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 41 total) == Sep 13 17:08:14 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x41] == matrix (1 distinct, 1 total) == Sep 13 17:36:04 matrix sshd[1742444]: error: PAM: Authentication failure for root from 212.116.238.51 == newhonors2 (1 distinct, 24 total) == Sep 13 17:13:03 newhonors2 dhcpcd[2594943]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 13 17:09:08 outbound00.cs.umd.edu python3[3917752]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 13 17:13:07 outbound01.cs.umd.edu python3[1981526]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886152]: link_config: could not get ethtool features for vetheb6bbf4 Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886152]: Could not set offload features of vetheb6bbf4: No such device Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886183]: Could not generate persistent MAC address for veth6f687cb: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886184]: Could not generate persistent MAC address for veth1f069b9: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886187]: Could not generate persistent MAC address for veth8e8b098: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886188]: Could not generate persistent MAC address for vetha1ab822: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886207]: Could not generate persistent MAC address for vethea5f6bd: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth0008ba7: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth4305a0e: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886207]: Could not generate persistent MAC address for veth3a11390: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886198]: Could not generate persistent MAC address for veth72a6cbb: No such file or directory Sep 13 17:09:54 sentry-docker00.cs.umd.edu systemd-udevd[3886199]: Could not generate persistent MAC address for veth9d9d4f4: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895746]: link_config: could not get ethtool features for veth0008ba7 Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895746]: Could not set offload features of veth0008ba7: No such device Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895774]: link_config: could not get ethtool features for veth3a11390 Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895774]: Could not set offload features of veth3a11390: No such device Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895808]: Could not generate persistent MAC address for vethe3c6b36: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895807]: Could not generate persistent MAC address for veth6f2f3d7: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895811]: Could not generate persistent MAC address for veth42320cb: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895812]: Could not generate persistent MAC address for veth40b9cac: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895851]: Could not generate persistent MAC address for vethaa379f7: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895852]: Could not generate persistent MAC address for veth33f88ba: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895879]: Could not generate persistent MAC address for veth631a69d: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895874]: Could not generate persistent MAC address for veth2c22c4f: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895870]: Could not generate persistent MAC address for veth4cf60a7: No such file or directory Sep 13 17:30:02 sentry-docker00.cs.umd.edu systemd-udevd[3895883]: Could not generate persistent MAC address for veth64ae8dc: No such file or directory Sep 13 17:50:10 sentry-docker00.cs.umd.edu systemd-udevd[3905247]: link_config: could not get ethtool features for veth631a69d Sep 13 17:50:10 sentry-docker00.cs.umd.edu systemd-udevd[3905247]: Could not set offload features of veth631a69d: No such device Sep 13 17:50:11 sentry-docker00.cs.umd.edu systemd-udevd[3905289]: Could not generate persistent MAC address for veth2bc1a81: No such file or directory Sep 13 17:50:11 sentry-docker00.cs.umd.edu systemd-udevd[3905290]: Could not generate persistent MAC address for veth2d6c5cb: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 13 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 13 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 13 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 13 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 5 total) == Sep 13 17:33:06 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f2 (1 distinct, 7 total) == Sep 13 17:10:15 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f3 (11 distinct, 20 total) == Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 [x2] Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 [x2] Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.A2ur28/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:40 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.A2ur28. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 [x2] Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: 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 [x2] Sep 13 17:06:41 submit26-b9-f3 setroubleshoot[733562]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.D42JJM. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 13 17:12:01 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] == submit26-b9-f4 (10 distinct, 10 total) == Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h5TnTX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h5TnTX. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:43 submit26-b9-f4 setroubleshoot[542538]: 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 13 17:24:44 submit26-b9-f4 setroubleshoot[542538]: 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 Sep 13 17:53:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL