Command: /usr/local/sbin/syslog-digest.py Time : 0.0410s Status : exited 0 Output : Syslog digest — 2026-09-16 03:05 EDT Processed 1,977 lines, filtered 1,730 (87%). 247 unknown (72 distinct) from 13 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 16 02:45:47 b0b02.cs.umd.edu rustdesk[1633834]: cannot open display: == csfw00a (1 distinct, 107 total) == Sep 16 02:03:49 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x107] == idm00 (1 distinct, 1 total) == Sep 16 02:53:56 idm00 named[4166701]: client @0x7f11a4064588 10.73.240.42#58161: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 16 02:37:41 idmp0 named[1598691]: client @0x7f2d30021688 10.73.240.43#65262: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 16 02:23:50 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 2 total) == Sep 16 02:08:08 munin sudo[2669582]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 16 02:08:08 munin sudo[2669582]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 16 02:13:02 newhonors2 dhcpcd[2703097]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 16 02:09:09 outbound00.cs.umd.edu python3[528843]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 16 02:13:06 outbound01.cs.umd.edu python3[2788523]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306582]: link_config: could not get ethtool features for vethc2fb667 Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306582]: Could not set offload features of vethc2fb667: No such device Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306618]: Could not generate persistent MAC address for vethc90fced: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306620]: Could not generate persistent MAC address for vethca868f5: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306622]: Could not generate persistent MAC address for veth3413fc9: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306620]: Could not generate persistent MAC address for vethd190f8d: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306623]: Could not generate persistent MAC address for veth1ab9c39: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306618]: Could not generate persistent MAC address for vethc1385e4: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306620]: Could not generate persistent MAC address for veth60e07ed: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306634]: Could not generate persistent MAC address for veth09ab8fe: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306642]: Could not generate persistent MAC address for vethb41b6ef: No such file or directory Sep 16 02:13:28 sentry-docker00.cs.umd.edu systemd-udevd[1306636]: Could not generate persistent MAC address for veth4f9b9aa: No such file or directory Sep 16 02:33:36 sentry-docker00.cs.umd.edu systemd-udevd[1315994]: link_config: could not get ethtool features for veth09ab8fe Sep 16 02:33:36 sentry-docker00.cs.umd.edu systemd-udevd[1315994]: Could not set offload features of veth09ab8fe: No such device Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316061]: Could not generate persistent MAC address for veth46afdb3: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316062]: Could not generate persistent MAC address for veth26338e6: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316065]: Could not generate persistent MAC address for veth23e387f: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316068]: Could not generate persistent MAC address for veth05cfa47: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316077]: Could not generate persistent MAC address for veth9b154eb: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316081]: Could not generate persistent MAC address for vethbffc7e0: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316077]: Could not generate persistent MAC address for vethdb00b31: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316081]: Could not generate persistent MAC address for veth54f9d53: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316114]: Could not generate persistent MAC address for veth07c7095: No such file or directory Sep 16 02:33:37 sentry-docker00.cs.umd.edu systemd-udevd[1316123]: Could not generate persistent MAC address for veth9bbb919: No such file or directory Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325760]: link_config: could not get ethtool features for veth46afdb3 Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325760]: Could not set offload features of veth46afdb3: No such device Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325846]: Could not generate persistent MAC address for veth24131df: No such file or directory Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325847]: Could not generate persistent MAC address for veth4b0773c: No such file or directory Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325850]: Could not generate persistent MAC address for vethce191fc: No such file or directory Sep 16 02:53:45 sentry-docker00.cs.umd.edu systemd-udevd[1325851]: Could not generate persistent MAC address for vethe972fc5: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 16 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 16 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 16 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 16 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 16 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 16 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 16 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 10 total) == Sep 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lR3Zt0/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lR3Zt0. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 16 02:25:52 submit26-b9-f1 setroubleshoot[1899489]: 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 Sep 16 02:57:55 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (9 distinct, 11 total) == Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2] Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2] Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.7egK1p/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.7egK1p. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 16 02:06:47 submit26-b9-f2 setroubleshoot[1035513]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7