Command: /usr/local/sbin/syslog-digest.py Time : 0.0450s Status : exited 0 Output : Syslog digest — 2026-10-03 06:05 EDT Processed 1,650 lines, filtered 1,323 (80%). 327 unknown (173 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 3 05:11:15 b0b02.cs.umd.edu rustdesk[3855417]: cannot open display: == grades01.cs.umd.edu (4 distinct, 10 total) == Oct 3 05:48:19 grades01.cs.umd.edu puppet-agent[6430]: 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 Oct 3 05:49:57 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:16] Unknown lvalue 'ProtectKernelTunables' in section 'Service' [x3] Oct 3 05:49:57 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:17] Unknown lvalue 'ProtectControlGroups' in section 'Service' [x3] Oct 3 05:49:57 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:18] Unknown lvalue 'ProtectKernelModules' in section 'Service' [x3] == idm00 (1 distinct, 1 total) == Oct 3 05:54:36 idm00 named[4166701]: client @0x7f11a8c67778 10.73.240.42#53780: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 3 05:39:25 idmp0 named[1598691]: client @0x7f2d2401f488 10.73.240.43#57740: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Oct 3 05:52:57 itmon02 sshd[805675]: error: beginning MaxStartups throttling == munin (2 distinct, 8 total) == Oct 3 05:13:20 munin sudo[3237286]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Oct 3 05:13:20 munin sudo[3237286]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == neodontcare.cs.umd.edu (1 distinct, 2 total) == Oct 3 06:04:51 neodontcare.cs.umd.edu packagekitd[567965]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2] == newhonors2 (1 distinct, 24 total) == Oct 3 05:13:03 newhonors2 dhcpcd[3490008]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Oct 3 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2242) *** Oct 3 05:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2242, QN: 64/64, ET: 0) *** Oct 3 05:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2242, QN: 3303/3303, ET: 5) *** Oct 3 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2243) *** Oct 3 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2243, QN: 3074/3074, ET: 0) *** Oct 3 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2243) *** Oct 3 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2243, QN: 56/56, ET: 0) *** Oct 3 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2244) *** Oct 3 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2244) *** Oct 3 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2244, QN: 66/66, ET: 0) *** Oct 3 05:10:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2244, QN: 3196/3196, ET: 4) *** Oct 3 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2245) *** Oct 3 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2245, QN: 3282/3282, ET: 0) *** Oct 3 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2245) *** Oct 3 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2245, QN: 61/61, ET: 0) *** Oct 3 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2246) *** Oct 3 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2246) *** Oct 3 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2246, QN: 60/60, ET: 0) *** Oct 3 05:15:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2246, QN: 3206/3206, ET: 4) *** Oct 3 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2247) *** Oct 3 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2247, QN: 3269/3269, ET: 0) *** Oct 3 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2247) *** Oct 3 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2247, QN: 58/58, ET: 0) *** Oct 3 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2248) *** Oct 3 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2248) *** Oct 3 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2248, QN: 59/59, ET: 0) *** Oct 3 05:20:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2248, QN: 3379/3379, ET: 4) *** Oct 3 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2249) *** Oct 3 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2249, QN: 3184/3184, ET: 0) *** Oct 3 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2249) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 3 05:09:08 outbound00.cs.umd.edu python3[2213562]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 11 total) == Oct 3 05:08:28 outbound01.cs.umd.edu python3[283713]: ldapdb [x7] Oct 3 05:10:48 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. [x4] == portal (1 distinct, 73 total) == Oct 3 05:05:14 portal setroubleshoot[420992]: 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 [x73] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373207]: link_config: could not get ethtool features for veth96c8a55 Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373207]: Could not set offload features of veth96c8a55: No such device Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373240]: Could not generate persistent MAC address for veth2072f53: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373239]: Could not generate persistent MAC address for veth6dc23bd: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373243]: Could not generate persistent MAC address for veth617e948: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373244]: Could not generate persistent MAC address for veth984641d: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373261]: Could not generate persistent MAC address for veth4c9fbb7: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373240]: Could not generate persistent MAC address for veth83cd72e: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373269]: Could not generate persistent MAC address for veth57c9869: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373270]: Could not generate persistent MAC address for veth96ec670: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373288]: Could not generate persistent MAC address for veth932870a: No such file or directory Oct 3 05:23:41 sentry-docker00.cs.umd.edu systemd-udevd[373280]: Could not generate persistent MAC address for vethb47290c: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382630]: link_config: could not get ethtool features for veth932870a Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382630]: Could not set offload features of veth932870a: No such device Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382667]: Could not generate persistent MAC address for veth5f92291: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382668]: Could not generate persistent MAC address for veth581e85d: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382693]: Could not generate persistent MAC address for vethe4c6c3e: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382694]: Could not generate persistent MAC address for veth167c7bd: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382719]: Could not generate persistent MAC address for veth531b710: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382720]: Could not generate persistent MAC address for vethbd94c15: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382738]: Could not generate persistent MAC address for vethd3f9fdb: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382745]: Could not generate persistent MAC address for veth89dba5d: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382723]: Could not generate persistent MAC address for veth35c0c0f: No such file or directory Oct 3 05:43:49 sentry-docker00.cs.umd.edu systemd-udevd[382745]: Could not generate persistent MAC address for veth84e4ee1: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392045]: Could not generate persistent MAC address for veth9a58448: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392046]: Could not generate persistent MAC address for vethe269ee3: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392049]: Could not generate persistent MAC address for veth0cf0b6e: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392049]: Could not generate persistent MAC address for vethcf5319b: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392050]: Could not generate persistent MAC address for veth58d4119: No such file or directory Oct 3 06:03:58 sentry-docker00.cs.umd.edu systemd-udevd[392057]: Could not generate persistent MAC address for veth9773898: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 3 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 3 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 3 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 3 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 3 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 3 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 3 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 11 total) == Oct 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.k6ZqeA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.k6ZqeA. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 3 05:06:47 submit26-b9-f3 setroubleshoot[675509]: 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 Oct 3 05:23:32 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (9 distinct, 9 total) == Oct 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.IW2WKO/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.IW2WKO. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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 3 05:24:52 submit26-b9-f4 setroubleshoot[3528853]: 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