Command: /usr/local/sbin/syslog-digest.py Time : 0.0469s Status : exited 0 Output : Syslog digest — 2026-10-04 06:05 EDT Processed 1,638 lines, filtered 1,263 (77%). 375 unknown (175 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 4 05:12:49 b0b02.cs.umd.edu rustdesk[27137]: cannot open display: == galax (1 distinct, 1 total) == Oct 4 05:57:38 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK == gle-dind04 (1 distinct, 1 total) == Oct 4 05:21:40 gle-dind04 lldpd[1171]: unable to send packet on real device for veth7c36073: No such device or address == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 4 05:48:39 grades01.cs.umd.edu puppet-agent[3071]: 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 == idm00 (1 distinct, 1 total) == Oct 4 05:54:37 idm00 named[4166701]: client @0x7f11a40481e8 10.73.240.42#57204: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 4 05:39:23 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#64574: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 2 total) == Oct 4 06:02:44 inbound01.cs.umd.edu krb5_child[752481]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == itmon02 (1 distinct, 5 total) == Oct 4 05:28:34 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (1 distinct, 1 total) == Oct 4 05:52:15 krispykreme.cs.umd.edu sshd-session[1742877]: error: send_error: write: Connection reset by peer == munin (2 distinct, 46 total) == Oct 4 05:08:01 munin sudo[3756384]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x23] Oct 4 05:08:01 munin sudo[3756384]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x23] == newhonors2 (1 distinct, 24 total) == Oct 4 05:13:02 newhonors2 dhcpcd[3535531]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 4 05:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2818) *** Oct 4 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2818) *** Oct 4 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2818, QN: 63/63, ET: 0) *** Oct 4 05:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2818, QN: 4258/4258, ET: 7) *** Oct 4 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2819) *** Oct 4 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2819, QN: 4289/4289, ET: 0) *** Oct 4 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2819) *** Oct 4 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2819, QN: 65/65, ET: 0) *** Oct 4 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2820) *** Oct 4 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2820) *** Oct 4 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2820, QN: 66/66, ET: 0) *** Oct 4 05:10:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2820, QN: 4493/4493, ET: 7) *** Oct 4 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2821) *** Oct 4 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2821, QN: 4405/4405, ET: 0) *** Oct 4 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2821) *** Oct 4 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2821, QN: 63/63, ET: 0) *** Oct 4 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2822) *** Oct 4 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2822) *** Oct 4 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2822, QN: 51/51, ET: 0) *** Oct 4 05:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2822, QN: 4268/4268, ET: 7) *** Oct 4 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2823) *** Oct 4 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2823, QN: 4315/4315, ET: 0) *** Oct 4 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2823) *** Oct 4 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2823, QN: 45/45, ET: 0) *** Oct 4 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2824) *** Oct 4 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2824) *** Oct 4 05:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2824, QN: 49/49, ET: 1) *** Oct 4 05:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2824, QN: 4459/4459, ET: 7) *** Oct 4 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2825) *** Oct 4 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2825, QN: 4528/4528, ET: 0) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 4 05:09:09 outbound00.cs.umd.edu python3[2550495]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 4 05:08:31 outbound01.cs.umd.edu python3[621859]: ldapdb [x7] Oct 4 05:10:46 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, 78 total) == Oct 4 05:05:55 portal setroubleshoot[741370]: 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 [x78] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044079]: link_config: could not get ethtool features for veth3d3e829 Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044079]: Could not set offload features of veth3d3e829: No such device Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044146]: Could not generate persistent MAC address for veth1c71ea5: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044147]: Could not generate persistent MAC address for vethc0ca2c7: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044150]: Could not generate persistent MAC address for veth4d02d9f: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044171]: Could not generate persistent MAC address for veth1287300: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044158]: Could not generate persistent MAC address for vetha40a616: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044172]: Could not generate persistent MAC address for vethd948e65: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044176]: Could not generate persistent MAC address for veth1a4fd82: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044177]: Could not generate persistent MAC address for veth5e6c139: No such file or directory Oct 4 05:13:31 sentry-docker00.cs.umd.edu systemd-udevd[1044180]: Could not generate persistent MAC address for veth432c9db: No such file or directory Oct 4 05:13:32 sentry-docker00.cs.umd.edu systemd-udevd[1044181]: Could not generate persistent MAC address for veth69b2cb7: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053779]: Could not generate persistent MAC address for vethdd16092: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053780]: Could not generate persistent MAC address for vethfce723a: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053783]: Could not generate persistent MAC address for vethfd6907c: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053787]: Could not generate persistent MAC address for veth306b8f8: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053805]: Could not generate persistent MAC address for vethf6c1430: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053801]: Could not generate persistent MAC address for vetha92d2df: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053809]: Could not generate persistent MAC address for vethe0f8c40: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053810]: Could not generate persistent MAC address for vethc2500fe: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053828]: Could not generate persistent MAC address for veth7df97d1: No such file or directory Oct 4 05:33:40 sentry-docker00.cs.umd.edu systemd-udevd[1053829]: Could not generate persistent MAC address for vethe01cdf6: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063136]: link_config: could not get ethtool features for vethf6c1430 Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063136]: Could not set offload features of vethf6c1430: No such device Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063170]: Could not generate persistent MAC address for veth9c206a2: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063171]: Could not generate persistent MAC address for vethac983c3: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063174]: Could not generate persistent MAC address for veth28c169c: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063175]: Could not generate persistent MAC address for vethdfd6e91: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063198]: Could not generate persistent MAC address for vethd4414d3: No such file or directory Oct 4 05:53:48 sentry-docker00.cs.umd.edu systemd-udevd[1063199]: Could not generate persistent MAC address for vetha6e8440: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 4 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 4 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 4 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 4 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 4 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 4 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 4 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 12 total) == Oct 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 [x2] Oct 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.je8Muy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Oct 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 [x2] Oct 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.je8Muy. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 4 05:06:48 submit26-b9-f3 setroubleshoot[873677]: 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 (11 distinct, 17 total) == Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zdOhao/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.zdOhao. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:24:52 submit26-b9-f4 setroubleshoot[3690672]: 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 [x2] Oct 4 05:25:26 submit26-b9-f4 setroubleshoot[3690734]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.D2vF7j/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 4 05:25:26 submit26-b9-f4 setroubleshoot[3690734]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.D2vF7j. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c