Command: /usr/local/sbin/syslog-digest.py Time : 0.0485s Status : exited 0 Output : Syslog digest — 2026-09-21 06:05 EDT Processed 1,825 lines, filtered 1,329 (72%). 496 unknown (175 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 05:53:27 b0b02.cs.umd.edu rustdesk[3520111]: cannot open display: == bale (5 distinct, 84 total) == Sep 21 05:05:10 bale setroubleshoot[1384075]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 21 05:05:10 bale setroubleshoot[1384075]: 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 [x12] Sep 21 05:05:13 bale setroubleshoot[1384075]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 21 05:05:16 bale setroubleshoot[1384075]: 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 [x12] Sep 21 05:05:28 bale setroubleshoot[1384691]: 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 [x12] == csfw00a (1 distinct, 118 total) == Sep 21 05:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 21 05:48:27 grades01.cs.umd.edu puppet-agent[5295]: 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 21 05:54:01 idm00 named[4166701]: client @0x7f11a429b368 10.73.240.42#64009: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 05:37:56 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#60614: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 21 05:08:01 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 12 total) == Sep 21 05:08:12 munin sudo[1160012]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 21 05:08:12 munin sudo[1160012]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 21 05:13:03 newhonors2 dhcpcd[2936136]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 21 05:05:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 5322/5322, ET: 26) *** Sep 21 05:05:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 48/48, ET: 26) *** Sep 21 05:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 21 05:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 40/40, ET: 0) *** Sep 21 05:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 21 05:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5462/5462, ET: 0) *** Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12] Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12] Sep 21 05:08:02 ntop00 setroubleshoot[960715]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 05:08:02 ntop00 setroubleshoot[960715]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12] Sep 21 05:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 21 05:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 21 05:10:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 5614/5614, ET: 27) *** Sep 21 05:10:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 37/37, ET: 27) *** Sep 21 05:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 21 05:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 5661/5661, ET: 0) *** Sep 21 05:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 517) *** Sep 21 05:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 517, QN: 48/48, ET: 0) *** Sep 21 05:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 21 05:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 21 05:15:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 5620/5620, ET: 26) *** Sep 21 05:15:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 54/54, ET: 26) *** Sep 21 05:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 21 05:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 21 05:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 48/48, ET: 0) *** Sep 21 05:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 5358/5358, ET: 0) *** Sep 21 05:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 21 05:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 21 05:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 46/46, ET: 0) *** Sep 21 05:20:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 5029/5029, ET: 23) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 05:09:09 outbound00.cs.umd.edu python3[2273430]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 21 05:08:33 outbound01.cs.umd.edu python3[338371]: ldapdb [x7] Sep 21 05:09:41 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 (34 distinct, 34 total) == Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599245]: link_config: could not get ethtool features for veth4273c1b Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599245]: Could not set offload features of veth4273c1b: No such device Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599282]: Could not generate persistent MAC address for veth54bac89: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599283]: Could not generate persistent MAC address for veth22c806b: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599286]: Could not generate persistent MAC address for veth9e271f8: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599287]: Could not generate persistent MAC address for veth78b58f7: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599310]: Could not generate persistent MAC address for veth193a7b3: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599311]: Could not generate persistent MAC address for veth45f5af6: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599329]: Could not generate persistent MAC address for veth0855e6f: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599331]: Could not generate persistent MAC address for veth0fd0f54: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599317]: Could not generate persistent MAC address for vethc8dae42: No such file or directory Sep 21 05:24:22 sentry-docker00.cs.umd.edu systemd-udevd[599316]: Could not generate persistent MAC address for veth28b2b73: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608760]: Could not generate persistent MAC address for vethf9fecbe: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608759]: Could not generate persistent MAC address for vethadc78c3: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608785]: Could not generate persistent MAC address for veth2919437: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608786]: Could not generate persistent MAC address for veth5a41864: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608804]: Could not generate persistent MAC address for veth3aabfe0: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608793]: Could not generate persistent MAC address for veth635bd94: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608833]: Could not generate persistent MAC address for veth5351b51: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608839]: Could not generate persistent MAC address for veth6b25e7e: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608902]: Could not generate persistent MAC address for vethb83feca: No such file or directory Sep 21 05:44:30 sentry-docker00.cs.umd.edu systemd-udevd[608890]: Could not generate persistent MAC address for veth9b47cfc: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618163]: link_config: could not get ethtool features for veth5351b51 Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618163]: Could not set offload features of veth5351b51: No such device Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618236]: Could not generate persistent MAC address for veth8ec0c93: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618235]: Could not generate persistent MAC address for veth3d0d1bb: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618235]: Could not generate persistent MAC address for vethdcc6535: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618252]: Could not generate persistent MAC address for veth00b3a78: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618236]: Could not generate persistent MAC address for veth03447fd: No such file or directory Sep 21 06:04:38 sentry-docker00.cs.umd.edu systemd-udevd[618255]: Could not generate persistent MAC address for vetha5ac0b0: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 21 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 21 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 21 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 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 21 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 21 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5PoudU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5PoudU. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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 21 05:06:43 submit26-b9-f3 setroubleshoot[2226020]: 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, 12 total) == Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 [x2] Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iHUiXb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 [x2] Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iHUiXb. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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 21 05:24:47 submit26-b9-f4 setroubleshoot[1602043]: 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