Command: /usr/local/sbin/syslog-digest.py Time : 0.0428s Status : exited 0 Output : Syslog digest — 2026-09-15 03:05 EDT Processed 1,871 lines, filtered 1,541 (82%). 330 unknown (80 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 15 02:44:17 b0b02.cs.umd.edu rustdesk[1266512]: cannot open display: == csfw00a (1 distinct, 134 total) == Sep 15 02:04:34 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x134] == hazfs.cs.umd.edu (1 distinct, 2 total) == Sep 15 02:25:02 hazfs.cs.umd.edu pcp[1974243]: pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log [x2] == idm00 (1 distinct, 1 total) == Sep 15 02:53:54 idm00 named[4166701]: client @0x7f11a00432a8 10.73.240.42#57197: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 15 02:37:38 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#51103: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 44 total) == Sep 15 02:08:11 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x44] == mcstic (3 distinct, 6 total) == Sep 15 02:05:26 mcstic krb5_child[602765]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 15 02:05:30 mcstic sshd[602760]: error: PAM: Authentication failure for admin from 35.187.107.129 Sep 15 02:05:46 mcstic sshd[602773]: error: Protocol major versions differ: 2 vs. 1 == netman.cs.umd.edu (2 distinct, 5 total) == Sep 15 02:30:01 netman.cs.umd.edu krb5_child[645055]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 15 02:30:05 netman.cs.umd.edu sshd[645050]: error: PAM: Authentication failure for admin from 34.52.197.52 == newhonors2 (1 distinct, 24 total) == Sep 15 02:13:02 newhonors2 dhcpcd[2657229]: dhcpcd is not running [x24] == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 15 02:09:09 outbound00.cs.umd.edu python3[189437]: ldapdb [x6] Sep 15 02:37:36 outbound00.cs.umd.edu sshd-session[196161]: error: maximum authentication attempts exceeded for root from 63.245.189.17 port 55828 ssh2 [preauth] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 15 02:13:06 outbound01.cs.umd.edu python3[2448672]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 15 02:23:37 sentry-docker00.cs.umd.edu systemd-udevd[632322]: link_config: could not get ethtool features for vethe3792ed Sep 15 02:23:37 sentry-docker00.cs.umd.edu systemd-udevd[632322]: Could not set offload features of vethe3792ed: No such device Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632411]: Could not generate persistent MAC address for vethd8122ad: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632412]: Could not generate persistent MAC address for vethd06ced0: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632415]: Could not generate persistent MAC address for veth6d57fe2: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632416]: Could not generate persistent MAC address for veth313635a: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632416]: Could not generate persistent MAC address for veth8b47ecc: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632430]: Could not generate persistent MAC address for vethf2230d8: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632423]: Could not generate persistent MAC address for veth800ffae: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632419]: Could not generate persistent MAC address for veth072d594: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632416]: Could not generate persistent MAC address for veth39f3aff: No such file or directory Sep 15 02:23:38 sentry-docker00.cs.umd.edu systemd-udevd[632423]: Could not generate persistent MAC address for vethf5f37f7: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642099]: link_config: could not get ethtool features for vethd8122ad Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642099]: Could not set offload features of vethd8122ad: No such device Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642136]: Could not generate persistent MAC address for vethe033d27: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642137]: Could not generate persistent MAC address for veth83462c0: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642140]: Could not generate persistent MAC address for veth314865c: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642157]: Could not generate persistent MAC address for veth9646fb9: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642142]: Could not generate persistent MAC address for veth771f03f: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642156]: Could not generate persistent MAC address for vethb99d619: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642156]: Could not generate persistent MAC address for veth2297f91: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642142]: Could not generate persistent MAC address for veth6aa0d3a: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642175]: Could not generate persistent MAC address for vethd9d08da: No such file or directory Sep 15 02:43:46 sentry-docker00.cs.umd.edu systemd-udevd[642179]: Could not generate persistent MAC address for vethaa2bde6: No such file or directory Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651641]: link_config: could not set ethtool features for veth6aa0d3a Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651641]: Could not set offload features of veth6aa0d3a: Operation not permitted Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651673]: Could not generate persistent MAC address for vethafa4a84: No such file or directory Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651674]: Could not generate persistent MAC address for veth031ec21: No such file or directory Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651692]: Could not generate persistent MAC address for vethefb0663: No such file or directory Sep 15 03:03:54 sentry-docker00.cs.umd.edu systemd-udevd[651681]: Could not generate persistent MAC address for vetha2d9a25: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 15 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 15 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 15 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 15 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 15 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 15 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 15 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 11 total) == Sep 15 02:06:40 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.m8A17O/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.m8A17O. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:51 submit26-b9-f1 setroubleshoot[1750127]: 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 15 02:25:52 submit26-b9-f1 setroubleshoot[1750127]: 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 (10 distinct, 10 total) == Sep 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.n8nE0B/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.n8nE0B. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 15 02:06:47 submit26-b9-f2 setroubleshoot[888815]: 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 Sep 15 02:33:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (1 distinct, 2 total) == Sep 15 02:13:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (1 distinct, 2 total) == Sep 15 02:10:07 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2]
participants (1)
-
cron/syslog01.cs.umd.edu