Command: /usr/local/sbin/syslog-digest.py Time : 0.0472s Status : exited 0 Output : Syslog digest — 2026-10-06 06:05 EDT Processed 1,827 lines, filtered 1,459 (79%). 368 unknown (170 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 6 05:15:45 b0b02.cs.umd.edu rustdesk[757863]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Oct 6 05:48:15 grades01.cs.umd.edu puppet-agent[2964]: 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 6 05:54:40 idm00 named[4166701]: client @0x7f11a403a7a8 10.73.240.42#52060: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 6 05:39:24 idmp0 named[1598691]: client @0x7f2d2403ade8 10.73.240.43#65257: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 6 05:13:14 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 58 total) == Oct 6 05:08:03 munin sudo[603514]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x29] Oct 6 05:08:03 munin sudo[603514]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x29] == newhonors2 (1 distinct, 24 total) == Oct 6 05:13:03 newhonors2 dhcpcd[3626218]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 6 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3970) *** Oct 6 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3970, QN: 62/62, ET: 0) *** Oct 6 05:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3970, QN: 3836/3836, ET: 5) *** Oct 6 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3971) *** Oct 6 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3971, QN: 3998/3998, ET: 0) *** Oct 6 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3971) *** Oct 6 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3971, QN: 57/57, ET: 0) *** Oct 6 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3972) *** Oct 6 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3972) *** Oct 6 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3972, QN: 52/52, ET: 0) *** Oct 6 05:10:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3972, QN: 4036/4036, ET: 6) *** Oct 6 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3973) *** Oct 6 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3973, QN: 3992/3992, ET: 0) *** Oct 6 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3973) *** Oct 6 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3973, QN: 71/71, ET: 0) *** Oct 6 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3974) *** Oct 6 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3974) *** Oct 6 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3974, QN: 79/79, ET: 0) *** Oct 6 05:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3974, QN: 3991/3991, ET: 7) *** Oct 6 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3975) *** Oct 6 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3975, QN: 3949/3949, ET: 0) *** Oct 6 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3975) *** Oct 6 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3975, QN: 64/64, ET: 0) *** Oct 6 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3976) *** Oct 6 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3976) *** Oct 6 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3976, QN: 66/66, ET: 0) *** Oct 6 05:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3976, QN: 4128/4128, ET: 7) *** Oct 6 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3977) *** Oct 6 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3977, QN: 4530/4530, ET: 0) *** Oct 6 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3977) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 6 05:09:09 outbound00.cs.umd.edu python3[3227711]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Oct 6 05:08:12 outbound01.cs.umd.edu python3[1300240]: ldapdb [x7] Oct 6 05:10:29 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 6 05:05:18 portal setroubleshoot[1384750]: 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 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394924]: link_config: could not get ethtool features for veth341ede2 Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394924]: Could not set offload features of veth341ede2: No such device Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394961]: Could not generate persistent MAC address for veth9dc3b59: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394962]: Could not generate persistent MAC address for veth59a47b3: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394965]: Could not generate persistent MAC address for vethb9c62e1: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394966]: Could not generate persistent MAC address for veth178d1e3: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394966]: Could not generate persistent MAC address for vethd0402e3: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394984]: Could not generate persistent MAC address for veth5931d9a: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394966]: Could not generate persistent MAC address for veth6595b49: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394978]: Could not generate persistent MAC address for veth60a226f: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394984]: Could not generate persistent MAC address for vethb19532c: No such file or directory Oct 6 05:13:29 sentry-docker00.cs.umd.edu systemd-udevd[2394962]: Could not generate persistent MAC address for veth379776e: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404580]: link_config: could not get ethtool features for vethb19532c Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404580]: Could not set offload features of vethb19532c: No such device Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404610]: Could not generate persistent MAC address for vethaadda72: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404611]: Could not generate persistent MAC address for veth1adeafa: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404614]: Could not generate persistent MAC address for veth5853143: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404626]: Could not generate persistent MAC address for veth347ef55: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404616]: Could not generate persistent MAC address for veth4e4d43d: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404629]: Could not generate persistent MAC address for veth0a181ab: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404640]: Could not generate persistent MAC address for veth120b82d: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404641]: Could not generate persistent MAC address for veth2f55936: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404663]: Could not generate persistent MAC address for veth31a4206: No such file or directory Oct 6 05:33:38 sentry-docker00.cs.umd.edu systemd-udevd[2404657]: Could not generate persistent MAC address for vethb3a7d51: No such file or directory Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413879]: link_config: could not get ethtool features for veth4e4d43d Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413879]: Could not set offload features of veth4e4d43d: No such device Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413956]: Could not generate persistent MAC address for veth0370c34: No such file or directory Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413957]: Could not generate persistent MAC address for veth79e730d: No such file or directory Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413960]: Could not generate persistent MAC address for veth653aca8: No such file or directory Oct 6 05:53:46 sentry-docker00.cs.umd.edu systemd-udevd[2413961]: Could not generate persistent MAC address for veth47472f6: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 6 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 6 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 6 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 6 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 6 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 6 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 6 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bbSEOb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bbSEOb. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:06:48 submit26-b9-f3 setroubleshoot[1413772]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iBKFWB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iBKFWB. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 6 05:24:52 submit26-b9-f4 setroubleshoot[4074795]: 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 == wraith (1 distinct, 1 total) == Oct 6 05:47:34 wraith kernel: set_capacity_and_notify: 29 callbacks suppressed