Command: /usr/local/sbin/syslog-digest.py Time : 0.0463s Status : exited 0 Output : Syslog digest — 2026-10-05 06:05 EDT Processed 1,735 lines, filtered 1,376 (79%). 359 unknown (175 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 5 05:14:17 b0b02.cs.umd.edu rustdesk[392239]: cannot open display: == emaar (1 distinct, 1 total) == Oct 5 06:02:53 emaar systemd[1]: insights-client.service: Start request repeated too quickly. == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 5 05:48:30 grades01.cs.umd.edu puppet-agent[32187]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == hasaraumd (1 distinct, 1 total) == Oct 5 05:12:03 hasaraumd kernel: workqueue: page_reporting_process hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Oct 5 05:54:39 idm00 named[4166701]: client @0x7f11a4296188 10.73.240.42#51251: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 5 05:39:25 idmp0 named[1598691]: client @0x7f2d4002f658 10.73.240.43#65028: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 5 05:28:28 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 44 total) == Oct 5 05:38:51 munin sudo[94132]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22] Oct 5 05:38:51 munin sudo[94132]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22] == neo-gizmonic (1 distinct, 1 total) == Oct 5 06:04:57 neo-gizmonic systemd[1]: resmon.service: Supervising process 3551672 which is not our child. We'll most likely not notice when it exits. == newhonors2 (1 distinct, 24 total) == Oct 5 05:13:03 newhonors2 dhcpcd[3581389]: dhcpcd is not running [x24] == ntop00 (99 distinct, 99 total) == Oct 5 05:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3394) *** Oct 5 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3394) *** Oct 5 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3394, QN: 62/62, ET: 0) *** Oct 5 05:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3394, QN: 3987/3987, ET: 5) *** Oct 5 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3395) *** Oct 5 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3395, QN: 70/70, ET: 0) *** Oct 5 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3395) *** Oct 5 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3395, QN: 3850/3850, ET: 0) *** Oct 5 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3396) *** Oct 5 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3396) *** Oct 5 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3396, QN: 65/65, ET: 0) *** Oct 5 05:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3396, QN: 3740/3740, ET: 5) *** Oct 5 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3397) *** Oct 5 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3397, QN: 3707/3707, ET: 0) *** Oct 5 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3397) *** Oct 5 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3397, QN: 53/53, ET: 0) *** Oct 5 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3398) *** Oct 5 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3398) *** Oct 5 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3398, QN: 61/61, ET: 0) *** Oct 5 05:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3398, QN: 3696/3696, ET: 5) *** Oct 5 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3399) *** Oct 5 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3399, QN: 3457/3457, ET: 0) *** Oct 5 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3399) *** Oct 5 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3399, QN: 72/72, ET: 0) *** Oct 5 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3400) *** Oct 5 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3400) *** Oct 5 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3400, QN: 54/54, ET: 0) *** Oct 5 05:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3400, QN: 3467/3467, ET: 5) *** Oct 5 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3401) *** Oct 5 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3401, QN: 3659/3659, ET: 0) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 5 05:09:09 outbound00.cs.umd.edu python3[2888449]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 5 05:08:16 outbound01.cs.umd.edu python3[960386]: ldapdb [x7] Oct 5 05:09:28 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == portal (1 distinct, 75 total) == Oct 5 05:05:59 portal setroubleshoot[1060527]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x75] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 5 05:23:34 sentry-docker00.cs.umd.edu systemd-udevd[1724335]: link_config: could not get ethtool features for veth5c450bb Oct 5 05:23:34 sentry-docker00.cs.umd.edu systemd-udevd[1724335]: Could not set offload features of veth5c450bb: No such device Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724393]: Could not generate persistent MAC address for veth6f9fa18: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724394]: Could not generate persistent MAC address for vethbcd0a5e: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724397]: Could not generate persistent MAC address for vethe5ade1b: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724398]: Could not generate persistent MAC address for veth7ec0d8b: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724421]: Could not generate persistent MAC address for veth23b1953: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724422]: Could not generate persistent MAC address for veth7a2c9bd: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724440]: Could not generate persistent MAC address for veth0267581: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724435]: Could not generate persistent MAC address for veth04805d6: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724434]: Could not generate persistent MAC address for veth1424874: No such file or directory Oct 5 05:23:35 sentry-docker00.cs.umd.edu systemd-udevd[1724425]: Could not generate persistent MAC address for vethb5883ae: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733741]: link_config: could not get ethtool features for vethe5ade1b Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733741]: Could not set offload features of vethe5ade1b: No such device Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733771]: Could not generate persistent MAC address for veth8a4bd1c: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733772]: Could not generate persistent MAC address for veth647ff63: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733790]: Could not generate persistent MAC address for veth04facac: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733782]: Could not generate persistent MAC address for veth59a7693: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733782]: Could not generate persistent MAC address for veth489230a: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733781]: Could not generate persistent MAC address for vethd25a450: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733790]: Could not generate persistent MAC address for vethf9d1685: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733776]: Could not generate persistent MAC address for veth1ad0330: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733782]: Could not generate persistent MAC address for vetheff069c: No such file or directory Oct 5 05:43:43 sentry-docker00.cs.umd.edu systemd-udevd[1733781]: Could not generate persistent MAC address for veth1350d22: No such file or directory Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743127]: link_config: could not get ethtool features for veth8a4bd1c Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743127]: Could not set offload features of veth8a4bd1c: No such device Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743163]: Could not generate persistent MAC address for veth68067ef: No such file or directory Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743164]: Could not generate persistent MAC address for veth8109d5a: No such file or directory Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743167]: Could not generate persistent MAC address for vethdaadad8: No such file or directory Oct 5 06:03:51 sentry-docker00.cs.umd.edu systemd-udevd[1743168]: Could not generate persistent MAC address for vethadfe2c4: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 5 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 5 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 5 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Hvqt9j/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Hvqt9j. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 Oct 5 05:06:48 submit26-b9-f3 setroubleshoot[1074637]: 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 == submit26-b9-f4 (9 distinct, 9 total) == Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.UWDgzB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.UWDgzB. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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 Oct 5 05:24:52 submit26-b9-f4 setroubleshoot[3831321]: 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