Command: /usr/local/sbin/syslog-digest.py Time : 0.0473s Status : exited 0 Output : Syslog digest — 2026-09-29 06:05 EDT Processed 2,145 lines, filtered 1,834 (85%). 311 unknown (171 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 29 05:05:30 b0b02.cs.umd.edu rustdesk[2320596]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 29 05:48:01 grades01.cs.umd.edu puppet-agent[9935]: 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) == Sep 29 05:54:12 idm00 named[4166701]: client @0x7f11a93c7eb8 10.73.240.42#52757: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 29 05:39:28 idmp0 named[1598691]: client @0x7f2d2000e0b8 10.73.240.43#50838: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 29 05:13:32 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == newhonors2 (1 distinct, 24 total) == Sep 29 05:13:03 newhonors2 dhcpcd[3307626]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 29 05:05:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 66/66, ET: 0) *** Sep 29 05:05:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 4393/4393, ET: 6) *** Sep 29 05:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 29 05:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 4460/4460, ET: 0) *** Sep 29 05:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 29 05:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 66/66, ET: 0) *** Sep 29 05:10:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 29 05:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 29 05:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 63/63, ET: 0) *** Sep 29 05:10:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 4399/4399, ET: 6) *** Sep 29 05:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 29 05:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 4487/4487, ET: 0) *** Sep 29 05:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 29 05:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 62/62, ET: 0) *** Sep 29 05:15:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 29 05:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 29 05:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 52/52, ET: 0) *** Sep 29 05:15:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 4487/4487, ET: 6) *** Sep 29 05:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 29 05:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4351/4351, ET: 0) *** Sep 29 05:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 29 05:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 55/55, ET: 0) *** Sep 29 05:20:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 29 05:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 29 05:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 69/69, ET: 0) *** Sep 29 05:20:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 4294/4294, ET: 6) *** Sep 29 05:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** Sep 29 05:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 521, QN: 4195/4195, ET: 0) *** Sep 29 05:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** Sep 29 05:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 521, QN: 62/62, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 29 05:09:09 outbound00.cs.umd.edu python3[824932]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 29 05:08:31 outbound01.cs.umd.edu python3[3089548]: ldapdb [x7] Sep 29 05:09:37 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, 72 total) == Sep 29 05:05:14 portal setroubleshoot[3358518]: 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 [x72] == sebatinsky.cs.umd.edu (3 distinct, 3 total) == Sep 29 05:16:44 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts Sep 29 05:16:44 sebatinsky.cs.umd.edu kernel: hpet1: lost 4 rtc interrupts Sep 29 05:16:44 sebatinsky.cs.umd.edu kernel: hpet1: lost 3 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853685]: link_config: could not get ethtool features for veth3dcd162 Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853685]: Could not set offload features of veth3dcd162: No such device Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853709]: Could not generate persistent MAC address for veth4c5c7ad: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853710]: Could not generate persistent MAC address for veth6646b12: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853735]: Could not generate persistent MAC address for veth1e12079: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853736]: Could not generate persistent MAC address for veth44d1d24: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853739]: Could not generate persistent MAC address for veth7cc3e9a: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853749]: Could not generate persistent MAC address for veth9993d4d: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853790]: Could not generate persistent MAC address for veth173c48b: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853786]: Could not generate persistent MAC address for vethbacac94: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853825]: Could not generate persistent MAC address for veth4399064: No such file or directory Sep 29 05:23:49 sentry-docker00.cs.umd.edu systemd-udevd[1853790]: Could not generate persistent MAC address for veth689fda0: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863112]: link_config: could not get ethtool features for veth1e12079 Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863112]: Could not set offload features of veth1e12079: No such device Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863150]: Could not generate persistent MAC address for veth808215c: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863151]: Could not generate persistent MAC address for vethfdc382d: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863154]: Could not generate persistent MAC address for veth3c5d93b: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863155]: Could not generate persistent MAC address for veth17c83f9: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863150]: Could not generate persistent MAC address for veth9ade2fc: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863151]: Could not generate persistent MAC address for veth684e231: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863169]: Could not generate persistent MAC address for veth58c9f88: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863160]: Could not generate persistent MAC address for veth43effa2: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863166]: Could not generate persistent MAC address for veth6c0821a: No such file or directory Sep 29 05:43:57 sentry-docker00.cs.umd.edu systemd-udevd[1863169]: Could not generate persistent MAC address for vethba52fa5: No such file or directory Sep 29 06:04:05 sentry-docker00.cs.umd.edu systemd-udevd[1872559]: link_config: could not get ethtool features for veth684e231 Sep 29 06:04:05 sentry-docker00.cs.umd.edu systemd-udevd[1872559]: Could not set offload features of veth684e231: No such device Sep 29 06:04:06 sentry-docker00.cs.umd.edu systemd-udevd[1872587]: Could not generate persistent MAC address for veth5840f8e: No such file or directory Sep 29 06:04:06 sentry-docker00.cs.umd.edu systemd-udevd[1872588]: Could not generate persistent MAC address for veth78c86bd: No such file or directory Sep 29 06:04:06 sentry-docker00.cs.umd.edu systemd-udevd[1872588]: Could not generate persistent MAC address for vethc74181f: No such file or directory Sep 29 06:04:06 sentry-docker00.cs.umd.edu systemd-udevd[1872592]: Could not generate persistent MAC address for veth6ac10d6: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 29 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 29 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 29 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 29 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 29 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 29 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 29 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LcVd9P/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LcVd9P. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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 Sep 29 05:06:46 submit26-b9-f3 setroubleshoot[4165533]: 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, 11 total) == Sep 29 05:24:49 submit26-b9-f4 setroubleshoot[3028944]: 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] Sep 29 05:24:49 submit26-b9-f4 setroubleshoot[3028944]: 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] Sep 29 05:24:49 submit26-b9-f4 setroubleshoot[3028944]: 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 Sep 29 05:24:49 submit26-b9-f4 setroubleshoot[3028944]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3e3K54/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 29 05:24:50 submit26-b9-f4 setroubleshoot[3028944]: 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 Sep 29 05:24:50 submit26-b9-f4 setroubleshoot[3028944]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3e3K54. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 29 05:24:50 submit26-b9-f4 setroubleshoot[3028944]: 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 Sep 29 05:24:50 submit26-b9-f4 setroubleshoot[3028944]: 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 Sep 29 05:24:50 submit26-b9-f4 setroubleshoot[3028944]: 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