Command: /usr/local/sbin/syslog-digest.py Time : 0.0582s Status : exited 0 Output : Syslog digest — 2026-09-18 06:05 EDT Processed 3,306 lines, filtered 2,728 (82%). 578 unknown (190 distinct) from 19 host(s). == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 18 05:31:51 atif01.cs.umd.edu kernel: net_ratelimit: 32 callbacks suppressed Sep 18 05:31:51 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 18 05:49:06 b0b02.cs.umd.edu rustdesk[2416102]: cannot open display: == bale (5 distinct, 90 total) == Sep 18 05:05:18 bale setroubleshoot[460574]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 18 05:05:18 bale setroubleshoot[460574]: 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 18 05:05:21 bale setroubleshoot[460574]: 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 18 05:05:24 bale setroubleshoot[460574]: 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 18 05:05:36 bale setroubleshoot[461201]: 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] == csfw00a (1 distinct, 126 total) == Sep 18 05:04:20 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x126] == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 18 05:48:17 grades01.cs.umd.edu puppet-agent[9239]: 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 18 05:54:08 idm00 named[4166701]: client @0x7f11a4042778 10.73.240.42#56226: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 18 05:37:58 idmp0 named[1598691]: client @0x7f2d50036288 10.73.240.43#55497: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 18 05:27:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 40 total) == Sep 18 05:23:35 munin sudo[3785629]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x20] Sep 18 05:23:35 munin sudo[3785629]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x20] == newhonors2 (1 distinct, 24 total) == Sep 18 05:13:03 newhonors2 dhcpcd[2800574]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 18 05:05:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 202) *** Sep 18 05:05:12 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 202, QN: 5351/5351, ET: 11) *** Sep 18 05:05:12 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 202, QN: 86/86, ET: 11) *** Sep 18 05:06:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 203) *** Sep 18 05:06:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 203, QN: 5291/5291, ET: 0) *** Sep 18 05:06:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 203) *** Sep 18 05:06:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 203, QN: 83/83, ET: 0) *** Sep 18 05:06:02 ntop00 setroubleshoot[388160]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 58e35a5d-c7c9-4337-868c-bb9d5ac2e29f [x12] Sep 18 05:06:02 ntop00 setroubleshoot[388160]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 369b1df3-2c9d-461b-8b1c-2fcd48dc737c [x12] Sep 18 05:06:02 ntop00 setroubleshoot[388160]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 18 05:06:02 ntop00 setroubleshoot[388160]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 481e7e24-3846-4790-b17b-9e44a5f5b5d6 [x12] Sep 18 05:10:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 204) *** Sep 18 05:10:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 204) *** Sep 18 05:10:12 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 204, QN: 5467/5467, ET: 11) *** Sep 18 05:10:12 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 204, QN: 50/50, ET: 11) *** Sep 18 05:11:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 205) *** Sep 18 05:11:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 205, QN: 5481/5481, ET: 0) *** Sep 18 05:11:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 205) *** Sep 18 05:11:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 205, QN: 55/55, ET: 0) *** Sep 18 05:15:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 206) *** Sep 18 05:15:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 206) *** Sep 18 05:15:13 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 206, QN: 5276/5276, ET: 12) *** Sep 18 05:15:13 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - END (PID: 206, QN: 88/88, ET: 12) *** Sep 18 05:16:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - START (PID: 207) *** Sep 18 05:16:01 ntop00 sfacctd[323304]: INFO ( p1/print ): *** Purging cache - END (PID: 207, QN: 5143/5143, ET: 0) *** Sep 18 05:16:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - START (PID: 207) *** Sep 18 05:16:01 ntop00 nfacctd[323381]: INFO ( p1/print ): *** Purging cache - END (PID: 207, QN: 72/72, ET: 0) *** Sep 18 05:20:01 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - START (PID: 208) *** Sep 18 05:20:01 ntop00 nfacctd[323381]: INFO ( m1/mysql ): *** Purging cache - START (PID: 208) *** Sep 18 05:20:12 ntop00 sfacctd[323304]: INFO ( m1/mysql ): *** Purging cache - END (PID: 208, QN: 4687/4687, ET: 11) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (5 distinct, 32 total) == Sep 18 05:05:58 outbound00.cs.umd.edu krb5_child[1252503]: Preauthentication failed [x12] Sep 18 05:09:09 outbound00.cs.umd.edu python3[1253403]: ldapdb [x6] Sep 18 05:09:22 outbound00.cs.umd.edu krb5_child[1253497]: Client 'admin@UMD.EDU' not found in Kerberos database [x9] Sep 18 05:10:39 outbound00.cs.umd.edu krb5_child[1253674]: Client 'test1@UMD.EDU' not found in Kerberos database [x3] Sep 18 05:51:50 outbound00.cs.umd.edu krb5_child[1264205]: Client 'george@UMD.EDU' not found in Kerberos database [x2] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 18 05:08:18 outbound01.cs.umd.edu python3[3511149]: ldapdb [x7] Sep 18 05:09:58 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 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750457]: link_config: could not get ethtool features for vethaa51905 Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750457]: Could not set offload features of vethaa51905: No such device Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750575]: Could not generate persistent MAC address for veth5885e1a: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750576]: Could not generate persistent MAC address for veth0104abd: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750579]: Could not generate persistent MAC address for veth64b2356: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750596]: Could not generate persistent MAC address for veth7b0596e: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750585]: Could not generate persistent MAC address for veth8b156d6: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750582]: Could not generate persistent MAC address for veth5099ab1: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750598]: Could not generate persistent MAC address for veth846984b: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750582]: Could not generate persistent MAC address for vethea6e619: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750576]: Could not generate persistent MAC address for vethca7f88c: No such file or directory Sep 18 05:14:33 sentry-docker00.cs.umd.edu systemd-udevd[2750585]: Could not generate persistent MAC address for veth12bd568: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760173]: link_config: could not get ethtool features for veth64b2356 Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760173]: Could not set offload features of veth64b2356: No such device Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760206]: Could not generate persistent MAC address for veth75dfb65: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760207]: Could not generate persistent MAC address for veth8b95a3d: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760210]: Could not generate persistent MAC address for veth9579528: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760211]: Could not generate persistent MAC address for veth63f18aa: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760234]: Could not generate persistent MAC address for vethfc0b830: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760235]: Could not generate persistent MAC address for veth8867fe3: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760250]: Could not generate persistent MAC address for veth1b12782: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760256]: Could not generate persistent MAC address for veth2b81e00: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760267]: Could not generate persistent MAC address for vetha2c96b9: No such file or directory Sep 18 05:34:41 sentry-docker00.cs.umd.edu systemd-udevd[2760266]: Could not generate persistent MAC address for veth0b38d99: No such file or directory Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769561]: link_config: could not get ethtool features for veth9579528 Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769561]: Could not set offload features of veth9579528: No such device Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769637]: link_config: could not set ethtool features for veth75dfb65 Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769637]: Could not set offload features of veth75dfb65: Operation not permitted Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769659]: Could not generate persistent MAC address for veth77bde7a: No such file or directory Sep 18 05:54:49 sentry-docker00.cs.umd.edu systemd-udevd[2769660]: Could not generate persistent MAC address for veth093c218: No such file or directory ... 8 more distinct messages not shown == soul (2 distinct, 4 total) == Sep 18 05:09:59 soul krb5_child[3230594]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 18 05:20:23 soul krb5_child[3231870]: Preauthentication failed [x2] == strawberry (7 distinct, 38 total) == Sep 18 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 18 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 18 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 18 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 18 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 18 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 18 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.AM9Ydi/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.AM9Ydi. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:06:42 submit26-b9-f3 setroubleshoot[1751765]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.sKcigQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sKcigQ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:24:45 submit26-b9-f4 setroubleshoot[1280964]: 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 18 05:25:19 submit26-b9-f4 setroubleshoot[1281018]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Fby2ky. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c == teaching-awards (2 distinct, 2 total) == Sep 18 05:28:17 teaching-awards krb5_child[1004056]: Preauthentication failed Sep 18 05:43:00 teaching-awards krb5_child[1004909]: Client 'admin@UMD.EDU' not found in Kerberos database