Command: /usr/local/sbin/syslog-digest.py Time : 0.0452s Status : exited 0 Output : Syslog digest — 2026-09-09 03:05 EDT Processed 2,475 lines, filtered 2,160 (87%). 315 unknown (69 distinct) from 15 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Sep 9 02:35:53 atif01.cs.umd.edu sshd[37474]: fatal: ssh_packet_get_string: incomplete message [preauth] == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 9 02:35:31 b0b02.cs.umd.edu rustdesk[3259112]: cannot open display: == csfw00a (1 distinct, 150 total) == Sep 9 02:04:04 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x150] == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 9 02:25:02 hazfs.cs.umd.edu pcp[2679547]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 9 02:53:47 idm00 named[3831946]: client @0x7f1e693c8d38 10.73.240.42#57464: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 9 02:37:42 idmp0 named[1239047]: client @0x7fd520025dc8 10.73.240.43#60280: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 33 total) == Sep 9 02:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x33] == munin (2 distinct, 2 total) == Sep 9 03:03:12 munin sudo[3294915]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 9 03:03:12 munin sudo[3294915]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 9 02:13:03 newhonors2 dhcpcd[2383635]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 9 02:09:09 outbound00.cs.umd.edu python3[2338883]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 9 02:13:06 outbound01.cs.umd.edu python3[399971]: ldapdb [x6] == sentry-docker00.cs.umd.edu (32 distinct, 32 total) == Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752048]: Could not generate persistent MAC address for vethd343a40: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752039]: Could not generate persistent MAC address for vethc9cedd2: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752124]: Could not generate persistent MAC address for vethea62f58: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752125]: Could not generate persistent MAC address for vethbf59b3a: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752138]: Could not generate persistent MAC address for veth4aa5467: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752137]: Could not generate persistent MAC address for vethe79ae3e: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752182]: Could not generate persistent MAC address for veth2bf5ba4: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752183]: Could not generate persistent MAC address for veth7f60d68: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752207]: Could not generate persistent MAC address for veth2e2151f: No such file or directory Sep 9 02:23:56 sentry-docker00.cs.umd.edu systemd-udevd[752209]: Could not generate persistent MAC address for veth1ce5a04: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761741]: Could not generate persistent MAC address for veth8eb0edf: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761742]: Could not generate persistent MAC address for vethaae8579: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761760]: Could not generate persistent MAC address for veth1054658: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761757]: Could not generate persistent MAC address for veth9bd10ee: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761757]: Could not generate persistent MAC address for veth467cb08: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761749]: Could not generate persistent MAC address for veth4bab359: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761759]: Could not generate persistent MAC address for veth9f03074: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761741]: Could not generate persistent MAC address for veth1053933: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761804]: Could not generate persistent MAC address for veth7bc0975: No such file or directory Sep 9 02:44:04 sentry-docker00.cs.umd.edu systemd-udevd[761807]: Could not generate persistent MAC address for veth1105281: No such file or directory Sep 9 03:04:12 sentry-docker00.cs.umd.edu systemd-udevd[771344]: link_config: could not get ethtool features for veth7bc0975 Sep 9 03:04:12 sentry-docker00.cs.umd.edu systemd-udevd[771344]: Could not set offload features of veth7bc0975: No such device Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771380]: Could not generate persistent MAC address for veth3482c15: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771381]: Could not generate persistent MAC address for veth7170a07: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771406]: Could not generate persistent MAC address for vethacd65c2: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771408]: Could not generate persistent MAC address for vethff5c9d8: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771425]: Could not generate persistent MAC address for vetha9e28c5: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771428]: Could not generate persistent MAC address for veth7396838: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771434]: Could not generate persistent MAC address for vethe82f4f3: No such file or directory Sep 9 03:04:13 sentry-docker00.cs.umd.edu systemd-udevd[771435]: Could not generate persistent MAC address for veth336924a: No such file or directory ... 2 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 9 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 9 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 9 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 9 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 9 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 9 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 9 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 9 02:25:48 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:48 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:48 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:48 submit26-b9-f1 setroubleshoot[857643]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h6odTP/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 9 02:25:49 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:49 submit26-b9-f1 setroubleshoot[857643]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h6odTP. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 9 02:25:49 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:49 submit26-b9-f1 setroubleshoot[857643]: 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 9 02:25:49 submit26-b9-f1 setroubleshoot[857643]: 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 == submit26-b9-f2 (9 distinct, 9 total) == Sep 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 Sep 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 Sep 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.jJPhHV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.jJPhHV. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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 9 02:06:40 submit26-b9-f2 setroubleshoot[19843]: 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
participants (1)
-
cron/syslog01.cs.umd.edu