Command: /usr/local/sbin/syslog-digest.py Time : 0.0407s Status : exited 0 Output : Syslog digest — 2026-09-28 06:05 EDT Processed 1,657 lines, filtered 1,422 (85%). 235 unknown (167 distinct) from 13 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 28 06:04:04 b0b02.cs.umd.edu rustdesk[1967720]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 28 05:48:28 grades01.cs.umd.edu puppet-agent[8627]: 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 28 05:54:10 idm00 named[4166701]: client @0x7f11986d48e8 10.73.240.42#51373: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 28 05:39:28 idmp0 named[1598691]: client @0x7f2d2801dea8 10.73.240.43#57155: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 28 05:18:13 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == newhonors2 (1 distinct, 24 total) == Sep 28 05:13:02 newhonors2 dhcpcd[3262354]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 28 05:05:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 216) *** Sep 28 05:05:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 217) *** Sep 28 05:05:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 216, QN: 4513/4513, ET: 0) *** Sep 28 05:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 216) *** Sep 28 05:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 216, QN: 70/70, ET: 0) *** Sep 28 05:05:08 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 217, QN: 4513/4513, ET: 7) *** Sep 28 05:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 217) *** Sep 28 05:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 217, QN: 44/44, ET: 0) *** Sep 28 05:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 219) *** Sep 28 05:10:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 218) *** Sep 28 05:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 219, QN: 4812/4812, ET: 0) *** Sep 28 05:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 218) *** Sep 28 05:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 218, QN: 39/39, ET: 0) *** Sep 28 05:10:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 218, QN: 4812/4812, ET: 6) *** Sep 28 05:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 219) *** Sep 28 05:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 219, QN: 44/44, ET: 0) *** Sep 28 05:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 220) *** Sep 28 05:15:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 221) *** Sep 28 05:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 220, QN: 4589/4589, ET: 0) *** Sep 28 05:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 220) *** Sep 28 05:15:02 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 220, QN: 60/60, ET: 1) *** Sep 28 05:15:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 221, QN: 4589/4589, ET: 6) *** Sep 28 05:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 221) *** Sep 28 05:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 221, QN: 62/62, ET: 0) *** Sep 28 05:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 222) *** Sep 28 05:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 223) *** Sep 28 05:20:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 222) *** Sep 28 05:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 223, QN: 4248/4248, ET: 0) *** Sep 28 05:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 222, QN: 59/59, ET: 0) *** Sep 28 05:20:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 222, QN: 4248/4248, ET: 6) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 28 05:09:08 outbound00.cs.umd.edu python3[486343]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 9 total) == Sep 28 05:08:33 outbound01.cs.umd.edu python3[2750639]: ldapdb [x7] Sep 28 05:09:41 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. Sep 28 05:25:53 outbound01.cs.umd.edu krb5_child[2755725]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170264]: link_config: could not get ethtool features for vethe4fca1b Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170264]: Could not set offload features of vethe4fca1b: No such device Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170299]: Could not generate persistent MAC address for veth152068b: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170300]: Could not generate persistent MAC address for veth43e946b: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170303]: Could not generate persistent MAC address for vethba9347f: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170304]: Could not generate persistent MAC address for veth5fcf51a: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170327]: Could not generate persistent MAC address for veth879d3f8: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170328]: Could not generate persistent MAC address for vethf49837a: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170349]: Could not generate persistent MAC address for veth3c24f27: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170334]: Could not generate persistent MAC address for veth76d555b: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170349]: Could not generate persistent MAC address for veth3dc7d19: No such file or directory Sep 28 05:13:46 sentry-docker00.cs.umd.edu systemd-udevd[1170342]: Could not generate persistent MAC address for vethf873512: No such file or directory Sep 28 05:33:54 sentry-docker00.cs.umd.edu systemd-udevd[1179891]: link_config: could not get ethtool features for vethba9347f Sep 28 05:33:54 sentry-docker00.cs.umd.edu systemd-udevd[1179891]: Could not set offload features of vethba9347f: No such device Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179927]: Could not generate persistent MAC address for vetha8ae5ba: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179928]: Could not generate persistent MAC address for veth1eea662: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179931]: Could not generate persistent MAC address for veth4c9f2b3: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179932]: Could not generate persistent MAC address for veth41e82a0: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179927]: Could not generate persistent MAC address for vethb0f25cb: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179935]: Could not generate persistent MAC address for veth9fd80c8: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179973]: Could not generate persistent MAC address for vethc716b1c: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179976]: Could not generate persistent MAC address for veth93d9d40: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1179985]: Could not generate persistent MAC address for vethaa90341: No such file or directory Sep 28 05:33:55 sentry-docker00.cs.umd.edu systemd-udevd[1180003]: Could not generate persistent MAC address for vethc188a5f: No such file or directory Sep 28 05:54:02 sentry-docker00.cs.umd.edu systemd-udevd[1189291]: link_config: could not get ethtool features for vetha8ae5ba Sep 28 05:54:02 sentry-docker00.cs.umd.edu systemd-udevd[1189291]: Could not set offload features of vetha8ae5ba: No such device Sep 28 05:54:03 sentry-docker00.cs.umd.edu systemd-udevd[1189326]: Could not generate persistent MAC address for veth81af149: No such file or directory Sep 28 05:54:03 sentry-docker00.cs.umd.edu systemd-udevd[1189327]: Could not generate persistent MAC address for veth9da9ca2: No such file or directory Sep 28 05:54:03 sentry-docker00.cs.umd.edu systemd-udevd[1189352]: Could not generate persistent MAC address for veth77166c5: No such file or directory Sep 28 05:54:03 sentry-docker00.cs.umd.edu systemd-udevd[1189353]: Could not generate persistent MAC address for vethc0572c4: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 28 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 28 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 28 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 28 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 28 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 28 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 28 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.FGv7LA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FGv7LA. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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 28 05:06:45 submit26-b9-f3 setroubleshoot[3936318]: 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) == Sep 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 Sep 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 Sep 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.dumIqK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.dumIqK. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 28 05:24:48 submit26-b9-f4 setroubleshoot[2857593]: 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 28 05:24:49 submit26-b9-f4 setroubleshoot[2857593]: 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