Command: /usr/local/sbin/syslog-digest.py Time : 0.0409s Status : exited 0 Output : Syslog digest — 2026-09-25 06:05 EDT Processed 1,595 lines, filtered 1,346 (84%). 249 unknown (178 distinct) from 14 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 25 05:59:42 b0b02.cs.umd.edu rustdesk[864047]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 25 05:48:28 grades01.cs.umd.edu puppet-agent[12455]: 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 25 05:54:07 idm00 named[4166701]: client @0x7f11a007b958 10.73.240.42#56497: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 05:39:51 idmp0 named[1598691]: client @0x7f2d4403cd68 10.73.240.43#54326: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 25 05:08:32 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == matrix (12 distinct, 13 total) == Sep 25 05:47:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2919901, but reception only permitted for main PID 720 Sep 25 05:47:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2919910, but reception only permitted for main PID 720 Sep 25 05:47:32 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2920002, but reception only permitted for main PID 720 Sep 25 05:47:32 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2920008, but reception only permitted for main PID 720 Sep 25 05:47:32 matrix networkctl[2920023]: Interface "veth1536a05" not found. Sep 25 05:47:32 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2920023, but reception only permitted for main PID 720 [x2] Sep 25 05:47:32 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2920084, but reception only permitted for main PID 720 Sep 25 05:47:32 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2920097, but reception only permitted for main PID 720 Sep 25 05:50:57 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2922222, but reception only permitted for main PID 720 Sep 25 05:50:57 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2922228, but reception only permitted for main PID 720 Sep 25 05:50:57 matrix networkctl[2922238]: Interface "veth5e2434c" not found. Sep 25 05:50:57 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2922238, but reception only permitted for main PID 720 == newhonors2 (1 distinct, 24 total) == Sep 25 05:13:03 newhonors2 dhcpcd[3125201]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 25 05:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 514) *** Sep 25 05:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 58/58, ET: 0) *** Sep 25 05:05:07 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 4406/4406, ET: 6) *** Sep 25 05:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 25 05:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 4274/4274, ET: 0) *** Sep 25 05:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 25 05:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 63/63, ET: 0) *** Sep 25 05:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 25 05:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 25 05:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 59/59, ET: 0) *** Sep 25 05:10:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 4020/4020, ET: 5) *** Sep 25 05:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 25 05:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 3807/3807, ET: 0) *** Sep 25 05:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 25 05:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 49/49, ET: 0) *** Sep 25 05:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 25 05:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 25 05:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 45/45, ET: 0) *** Sep 25 05:15:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 3583/3583, ET: 5) *** Sep 25 05:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 25 05:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4458/4458, ET: 0) *** Sep 25 05:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 25 05:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 44/44, ET: 0) *** Sep 25 05:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 25 05:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 25 05:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 51/51, ET: 0) *** Sep 25 05:20:07 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 4222/4222, ET: 6) *** Sep 25 05:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** Sep 25 05:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 521, QN: 3343/3343, ET: 0) *** Sep 25 05:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 05:09:08 outbound00.cs.umd.edu python3[3661693]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 25 05:08:13 outbound01.cs.umd.edu python3[1726031]: ldapdb [x7] Sep 25 05:09:23 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. == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332399]: link_config: could not get ethtool features for veth4a34659 Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332399]: Could not set offload features of veth4a34659: No such device Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332427]: Could not generate persistent MAC address for veth3880023: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332428]: Could not generate persistent MAC address for vethd034998: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332453]: Could not generate persistent MAC address for veth1c9b72a: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332454]: Could not generate persistent MAC address for veth09735aa: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332472]: Could not generate persistent MAC address for vethbdcc848: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332474]: Could not generate persistent MAC address for vethb09eb4c: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332498]: Could not generate persistent MAC address for veth24ad6d2: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332504]: Could not generate persistent MAC address for vethc256314: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332552]: Could not generate persistent MAC address for veth622c572: No such file or directory Sep 25 05:24:05 sentry-docker00.cs.umd.edu systemd-udevd[3332559]: Could not generate persistent MAC address for vethb27ad4a: No such file or directory Sep 25 05:44:13 sentry-docker00.cs.umd.edu systemd-udevd[3341824]: link_config: could not get ethtool features for vethbdcc848 Sep 25 05:44:13 sentry-docker00.cs.umd.edu systemd-udevd[3341824]: Could not set offload features of vethbdcc848: No such device Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341855]: Could not generate persistent MAC address for veth43bbb37: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341856]: Could not generate persistent MAC address for vethf1b2a20: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341859]: Could not generate persistent MAC address for veth0617513: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341860]: Could not generate persistent MAC address for veth2bbba25: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341863]: Could not generate persistent MAC address for veth648c694: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341870]: Could not generate persistent MAC address for veth64ebfc3: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341933]: Could not generate persistent MAC address for vethd0b1c71: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341938]: Could not generate persistent MAC address for veth6914ce5: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341968]: Could not generate persistent MAC address for veth9485b09: No such file or directory Sep 25 05:44:14 sentry-docker00.cs.umd.edu systemd-udevd[3341967]: Could not generate persistent MAC address for veth4f5c6ba: No such file or directory Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351221]: link_config: could not get ethtool features for veth0617513 Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351221]: Could not set offload features of veth0617513: No such device Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351253]: Could not generate persistent MAC address for veth0b52c98: No such file or directory Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351254]: Could not generate persistent MAC address for vethd2a0e43: No such file or directory Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351257]: Could not generate persistent MAC address for veth79a40e2: No such file or directory Sep 25 06:04:22 sentry-docker00.cs.umd.edu systemd-udevd[3351258]: Could not generate persistent MAC address for veth24496db: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 25 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 25 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 25 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 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 25 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 25 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 11 total) == Sep 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 [x2] Sep 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 [x2] Sep 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iLc0zv/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iLc0zv. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 25 05:06:45 submit26-b9-f3 setroubleshoot[3340064]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3uRYLZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3uRYLZ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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 25 05:24:48 submit26-b9-f4 setroubleshoot[2440594]: 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