Command: /usr/local/sbin/syslog-digest.py Time : 0.0490s Status : exited 0 Output : Syslog digest — 2026-09-23 06:05 EDT Processed 1,942 lines, filtered 1,541 (79%). 401 unknown (185 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 23 05:56:33 b0b02.cs.umd.edu rustdesk[127949]: cannot open display: == bale (5 distinct, 91 total) == Sep 23 05:05:23 bale setroubleshoot[2027744]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 23 05:05:24 bale setroubleshoot[2027744]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13] Sep 23 05:05:27 bale setroubleshoot[2027744]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 23 05:05:30 bale setroubleshoot[2027744]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11] Sep 23 05:05:41 bale setroubleshoot[2028371]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x15] == galax (1 distinct, 6 total) == Sep 23 05:10:06 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6] == grades01.cs.umd.edu (2 distinct, 2 total) == Sep 23 05:48:43 grades01.cs.umd.edu puppet-agent[10922]: 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 23 05:50:31 grades01.cs.umd.edu sudo[12787]: root : problem with defaults entries ; TTY=unknown ; PWD=/ ; USER=root ; == idm00 (1 distinct, 1 total) == Sep 23 05:54:26 idm00 named[4166701]: client @0x7f11a406bb48 10.73.240.42#52341: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 05:37:55 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#63651: update '73.10.in-addr.arpa/IN' denied == irb2156 (1 distinct, 1 total) == Sep 23 05:26:43 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 100.100.100.100. == itmon02 (1 distinct, 5 total) == Sep 23 05:33:42 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == mcstic (3 distinct, 6 total) == Sep 23 05:47:28 mcstic krb5_child[990618]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 23 05:47:32 mcstic sshd[990613]: error: PAM: Authentication failure for admin from 34.77.23.255 Sep 23 05:47:42 mcstic sshd[990626]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 4 total) == Sep 23 05:13:02 munin sudo[2204919]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 23 05:13:02 munin sudo[2204919]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 23 05:13:03 newhonors2 dhcpcd[3027555]: dhcpcd is not running [x24] == ntop00 (98 distinct, 142 total) == Sep 23 05:05:26 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 4448/4448, ET: 25) *** Sep 23 05:05:26 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 48/48, ET: 25) *** Sep 23 05:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 23 05:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 4519/4519, ET: 0) *** Sep 23 05:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 23 05:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 46/46, ET: 0) *** Sep 23 05:08:02 ntop00 setroubleshoot[1342978]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l af369431-37df-4ac9-9292-5066d38787e5 [x12] Sep 23 05:08:02 ntop00 setroubleshoot[1342978]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 244a2465-7b27-44c9-bda6-9cd4f2dd6cbc [x12] Sep 23 05:08:02 ntop00 setroubleshoot[1342978]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 23 05:08:02 ntop00 setroubleshoot[1342978]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l ba3a59c0-2cfe-4a84-9a21-86479d1517da [x12] Sep 23 05:10:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 23 05:10:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 23 05:10:31 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 5403/5403, ET: 30) *** Sep 23 05:10:31 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 49/49, ET: 30) *** Sep 23 05:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 23 05:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 5574/5574, ET: 0) *** Sep 23 05:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 23 05:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 43/43, ET: 0) *** Sep 23 05:15:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 23 05:15:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 23 05:15:28 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 4812/4812, ET: 27) *** Sep 23 05:15:28 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 49/49, ET: 27) *** Sep 23 05:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 23 05:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 4535/4535, ET: 0) *** Sep 23 05:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 23 05:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 68/68, ET: 0) *** Sep 23 05:20:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 23 05:20:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 23 05:20:27 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 4495/4495, ET: 26) *** Sep 23 05:20:27 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 54/54, ET: 26) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 23 05:09:09 outbound00.cs.umd.edu python3[2983132]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 23 05:08:18 outbound01.cs.umd.edu python3[1047015]: ldapdb [x7] Sep 23 05:09: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. == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974536]: link_config: could not get ethtool features for vethb193eb7 Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974536]: Could not set offload features of vethb193eb7: No such device Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974606]: Could not generate persistent MAC address for vethb38bf18: No such file or directory Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974607]: Could not generate persistent MAC address for veth8b31ff3: No such file or directory Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974622]: Could not generate persistent MAC address for veth4ab9cbf: No such file or directory Sep 23 05:24:11 sentry-docker00.cs.umd.edu systemd-udevd[1974615]: Could not generate persistent MAC address for veth214e423: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974612]: Could not generate persistent MAC address for vethfa5774c: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974607]: Could not generate persistent MAC address for vethe7d9f15: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974627]: Could not generate persistent MAC address for veth037b34d: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974618]: Could not generate persistent MAC address for veth8dfc46f: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974706]: Could not generate persistent MAC address for veth6c334ad: No such file or directory Sep 23 05:24:12 sentry-docker00.cs.umd.edu systemd-udevd[1974707]: Could not generate persistent MAC address for veth39c19b9: No such file or directory Sep 23 05:44:19 sentry-docker00.cs.umd.edu systemd-udevd[1983896]: link_config: could not get ethtool features for veth037b34d Sep 23 05:44:19 sentry-docker00.cs.umd.edu systemd-udevd[1983896]: Could not set offload features of veth037b34d: No such device Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984027]: link_config: could not get ethtool features for veth6c334ad Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984027]: Could not set offload features of veth6c334ad: No such device Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984059]: Could not generate persistent MAC address for vethc4d99de: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984058]: Could not generate persistent MAC address for veth572caaf: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984077]: Could not generate persistent MAC address for veth0e0c7a2: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984073]: Could not generate persistent MAC address for vethcdc9b4e: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984065]: Could not generate persistent MAC address for veth8d3c694: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984073]: Could not generate persistent MAC address for veth378ea78: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984067]: Could not generate persistent MAC address for vetha2e80f1: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984064]: Could not generate persistent MAC address for vethffbd640: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984187]: Could not generate persistent MAC address for vethfe6e83a: No such file or directory Sep 23 05:44:20 sentry-docker00.cs.umd.edu systemd-udevd[1984189]: Could not generate persistent MAC address for veth5e00274: No such file or directory Sep 23 06:04:28 sentry-docker00.cs.umd.edu systemd-udevd[1993454]: link_config: could not get ethtool features for vethffbd640 Sep 23 06:04:28 sentry-docker00.cs.umd.edu systemd-udevd[1993454]: Could not set offload features of vethffbd640: No such device Sep 23 06:04:28 sentry-docker00.cs.umd.edu systemd-udevd[1993484]: Could not generate persistent MAC address for veth1b88fac: No such file or directory Sep 23 06:04:28 sentry-docker00.cs.umd.edu systemd-udevd[1993485]: Could not generate persistent MAC address for veth1021eb6: No such file or directory ... 8 more distinct messages not shown == strawberry (8 distinct, 39 total) == Sep 23 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 23 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 23 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 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 23 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 23 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] Sep 23 06:03:51 strawberry rsyslogd[3420262]: imjournal: filecreatemode is not set, using default 0644 [v8.2312.0 try https://www.rsyslog.com/e/2186 ] == submit26-b9-f3 (9 distinct, 12 total) == Sep 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 [x2] Sep 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5AbMPr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 [x2] Sep 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5AbMPr. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 23 05:06:44 submit26-b9-f3 setroubleshoot[2667103]: 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 (10 distinct, 14 total) == Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 [x2] Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 [x2] Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nXtIZN/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nXtIZN. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 [x2] Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: 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 [x2] Sep 23 05:24:49 submit26-b9-f4 setroubleshoot[1961390]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.C09Fc2. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c