Command: /usr/local/sbin/syslog-digest.py Time : 0.0471s Status : exited 0 Output : Syslog digest — 2026-09-30 06:05 EDT Processed 1,980 lines, filtered 1,643 (82%). 337 unknown (186 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 30 05:06:48 b0b02.cs.umd.edu rustdesk[2688434]: cannot open display: == grades01.cs.umd.edu (4 distinct, 4 total) == Sep 30 05:49:27 grades01.cs.umd.edu puppet-agent[11807]: 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 Sep 30 05:52:20 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:16] Unknown lvalue 'ProtectKernelTunables' in section 'Service' Sep 30 05:52:20 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:17] Unknown lvalue 'ProtectControlGroups' in section 'Service' Sep 30 05:52:20 grades01.cs.umd.edu systemd[1]: [/usr/lib/systemd/system/lldpd.service:18] Unknown lvalue 'ProtectKernelModules' in section 'Service' == idm00 (1 distinct, 1 total) == Sep 30 05:54:23 idm00 named[4166701]: client @0x7f11a0068ca8 10.73.240.42#63607: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 05:39:27 idmp0 named[1598691]: client @0x7f2d3c070a68 10.73.240.43#64365: update '73.10.in-addr.arpa/IN' denied == irb2156 (10 distinct, 10 total) == Sep 30 05:11:15 irb2156 systemd-resolved[3579]: Using degraded feature set TCP instead of UDP for DNS server 128.8.76.3. Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for openvox-agent Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for firefox Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for firefox-nightly Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for google-chrome-stable Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for gh Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for claude-code Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for cosmic-ext-tasks Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for cosmic-greeter Sep 30 06:03:08 irb2156 packagekitd[231475]: Failed to get cache filename for kernel == itmon02 (1 distinct, 2 total) == Sep 30 05:23:30 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 2 total) == Sep 30 05:28:10 krispykreme.cs.umd.edu sshd-session[138471]: error: send_error: write: Connection reset by peer [x2] == munin (2 distinct, 16 total) == Sep 30 05:08:39 munin sudo[1669229]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Sep 30 05:08:39 munin sudo[1669229]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == newhonors2 (1 distinct, 24 total) == Sep 30 05:13:03 newhonors2 dhcpcd[3353506]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 30 05:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 3917/3917, ET: 5) *** Sep 30 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 30 05:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 3996/3996, ET: 0) *** Sep 30 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 30 05:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 47/47, ET: 0) *** Sep 30 05:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 30 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 30 05:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 43/43, ET: 0) *** Sep 30 05:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 3864/3864, ET: 5) *** Sep 30 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 30 05:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 3876/3876, ET: 0) *** Sep 30 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 30 05:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 51/51, ET: 0) *** Sep 30 05:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 30 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 30 05:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 56/56, ET: 0) *** Sep 30 05:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 4080/4080, ET: 7) *** Sep 30 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 30 05:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4242/4242, ET: 0) *** Sep 30 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 30 05:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 65/65, ET: 0) *** Sep 30 05:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 30 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 30 05:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 72/72, ET: 0) *** Sep 30 05:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 3930/3930, ET: 6) *** Sep 30 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** Sep 30 05:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 521, QN: 3661/3661, ET: 0) *** Sep 30 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 521) *** Sep 30 05:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 521, QN: 72/72, ET: 0) *** Sep 30 05:25:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 522) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 30 05:09:09 outbound00.cs.umd.edu python3[1167762]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 9 total) == Sep 30 05:08:19 outbound01.cs.umd.edu python3[3430031]: ldapdb [x7] Sep 30 05:09:28 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. [x2] == portal (1 distinct, 68 total) == Sep 30 05:06:03 portal setroubleshoot[3668924]: 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 [x68] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 30 06:01:45 sebatinsky.cs.umd.edu kernel: hpet1: lost 7 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527345]: link_config: could not get ethtool features for vethc240d2c Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527345]: Could not set offload features of vethc240d2c: No such device Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527430]: Could not generate persistent MAC address for veth98351f0: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527429]: Could not generate persistent MAC address for vethe24fb29: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527433]: Could not generate persistent MAC address for veth879f624: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527453]: Could not generate persistent MAC address for veth2c84716: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527448]: Could not generate persistent MAC address for veth9cd2167: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527434]: Could not generate persistent MAC address for vethe3619ee: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527434]: Could not generate persistent MAC address for veth5271041: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527448]: Could not generate persistent MAC address for vethf5b2506: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527486]: Could not generate persistent MAC address for veth8dec71a: No such file or directory Sep 30 05:13:44 sentry-docker00.cs.umd.edu systemd-udevd[2527488]: Could not generate persistent MAC address for vethdfcc1cb: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537010]: link_config: could not get ethtool features for veth5271041 Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537010]: Could not set offload features of veth5271041: No such device Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537091]: Could not generate persistent MAC address for veth5726724: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537092]: Could not generate persistent MAC address for vethe642978: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537095]: Could not generate persistent MAC address for veth8508d70: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537096]: Could not generate persistent MAC address for veth740bb84: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537098]: Could not generate persistent MAC address for vetha1e6f92: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537117]: Could not generate persistent MAC address for veth3ee9016: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537117]: Could not generate persistent MAC address for vetha2efba4: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537098]: Could not generate persistent MAC address for veth7a7661a: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537117]: Could not generate persistent MAC address for vethef463a0: No such file or directory Sep 30 05:33:52 sentry-docker00.cs.umd.edu systemd-udevd[2537115]: Could not generate persistent MAC address for veth37f4d8d: No such file or directory Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546456]: link_config: could not get ethtool features for veth5726724 Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546456]: Could not set offload features of veth5726724: No such device Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546492]: Could not generate persistent MAC address for veth88e9ae1: No such file or directory Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546493]: Could not generate persistent MAC address for veth6f604d6: No such file or directory Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546496]: Could not generate persistent MAC address for vethbeacb58: No such file or directory Sep 30 05:54:00 sentry-docker00.cs.umd.edu systemd-udevd[2546497]: Could not generate persistent MAC address for veth87e8583: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 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 30 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 30 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 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 30 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 30 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 30 05:38:17 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 12 total) == Sep 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ZVxSAs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ZVxSAs. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 30 05:06:46 submit26-b9-f3 setroubleshoot[243287]: 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 Sep 30 05:51:24 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (9 distinct, 9 total) == Sep 30 05:24:49 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:49 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:49 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.H2u5Ys/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.H2u5Ys. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: 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 30 05:24:50 submit26-b9-f4 setroubleshoot[3213175]: 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