Command: /usr/local/sbin/syslog-digest.py Time : 0.0542s Status : exited 0 Output : Syslog digest — 2026-09-18 22:05 EDT Processed 2,596 lines, filtered 2,023 (77%). 573 unknown (190 distinct) from 22 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 18 21:50:06 b0b02.cs.umd.edu rustdesk[2662125]: cannot open display: == bale (5 distinct, 87 total) == Sep 18 21:05:47 bale setroubleshoot[664853]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 18 21:05:47 bale setroubleshoot[664853]: 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 18 21:05:50 bale setroubleshoot[664853]: 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 18 21:05:53 bale setroubleshoot[664853]: 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 18 21:06:05 bale setroubleshoot[665467]: 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 [x13] == csfw00a (1 distinct, 137 total) == Sep 18 21:03:56 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x137] == idm00 (1 distinct, 1 total) == Sep 18 21:53:57 idm00 named[4166701]: client @0x7f11a4006dd8 10.73.240.42#64664: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 18 21:37:58 idmp0 named[1598691]: client @0x7f2d2401e448 10.73.240.43#60756: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (5 distinct, 29 total) == Sep 18 21:19:17 inbound00.cs.umd.edu krb5_child[1610304]: Preauthentication failed [x17] Sep 18 21:22:02 inbound00.cs.umd.edu krb5_child[1611265]: Client 'admin@UMD.EDU' not found in Kerberos database [x9] Sep 18 21:57:39 inbound00.cs.umd.edu krb5_child[1620778]: Client 'george@UMD.EDU' not found in Kerberos database Sep 18 21:59:18 inbound00.cs.umd.edu krb5_child[1621211]: Client 'anton@UMD.EDU' not found in Kerberos database Sep 18 21:59:58 inbound00.cs.umd.edu krb5_child[1621341]: Client 'gitlab@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 2 total) == Sep 18 21:08:49 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 2 total) == Sep 18 21:41:26 krispykreme.cs.umd.edu sshd-session[3845849]: pam_access(sshd:auth): access denied for user `rztao' from `52.119.65.102' [x2] == munin (2 distinct, 28 total) == Sep 18 21:08:54 munin sudo[4135202]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14] Sep 18 21:08:54 munin sudo[4135202]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14] == netman.cs.umd.edu (1 distinct, 2 total) == Sep 18 21:08:38 netman.cs.umd.edu krb5_child[2142809]: Preauthentication failed [x2] == newhonors2 (1 distinct, 24 total) == Sep 18 21:13:03 newhonors2 dhcpcd[2830440]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 18 21:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 18 21:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 18 21:05:38 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 12888/12888, ET: 37) *** Sep 18 21:05:38 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 56/56, ET: 37) *** Sep 18 21:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 18 21:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 55/55, ET: 0) *** Sep 18 21:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 18 21:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 12946/12946, ET: 0) *** Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12] Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12] Sep 18 21:08:02 ntop00 setroubleshoot[515285]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 18 21:08:02 ntop00 setroubleshoot[515285]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12] Sep 18 21:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 18 21:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 18 21:10:40 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 13114/13114, ET: 39) *** Sep 18 21:10:40 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 62/62, ET: 39) *** Sep 18 21:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 18 21:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 69/69, ET: 0) *** Sep 18 21:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 18 21:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 13069/13069, ET: 0) *** Sep 18 21:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 18 21:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 18 21:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 65/65, ET: 0) *** Sep 18 21:15:36 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 12799/12799, ET: 35) *** Sep 18 21:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 18 21:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 18 21:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 65/65, ET: 0) *** Sep 18 21:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 11811/11811, ET: 0) *** Sep 18 21:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 18 21:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 18 21:09:09 outbound00.cs.umd.edu python3[1481503]: ldapdb [x6] Sep 18 22:01:23 outbound00.cs.umd.edu krb5_child[1494051]: Preauthentication failed == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 18 21:13:06 outbound01.cs.umd.edu python3[3740033]: ldapdb [x6] Sep 18 21:27:22 outbound01.cs.umd.edu krb5_child[3743721]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207098]: Could not generate persistent MAC address for veth399b566: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207099]: Could not generate persistent MAC address for vethc5dba78: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207123]: Could not generate persistent MAC address for veth1c2519f: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207117]: Could not generate persistent MAC address for veth2924a8d: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207126]: Could not generate persistent MAC address for vethe882141: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207127]: Could not generate persistent MAC address for veth0133c31: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207126]: Could not generate persistent MAC address for veth13791d1: No such file or directory Sep 18 21:21:12 sentry-docker00.cs.umd.edu systemd-udevd[3207146]: Could not generate persistent MAC address for veth4dc0625: No such file or directory Sep 18 21:21:13 sentry-docker00.cs.umd.edu systemd-udevd[3207186]: Could not generate persistent MAC address for veth26d56b8: No such file or directory Sep 18 21:21:13 sentry-docker00.cs.umd.edu systemd-udevd[3207190]: Could not generate persistent MAC address for vethc0968dd: No such file or directory Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216734]: link_config: could not get ethtool features for veth26d56b8 Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216734]: Could not set offload features of veth26d56b8: No such device Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216758]: Could not generate persistent MAC address for vethbece149: No such file or directory Sep 18 21:41:20 sentry-docker00.cs.umd.edu systemd-udevd[3216759]: Could not generate persistent MAC address for vethb6af48c: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216806]: Could not generate persistent MAC address for veth4edf6a8: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216807]: Could not generate persistent MAC address for veth2ea7a3c: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216818]: Could not generate persistent MAC address for vethe6d40f8: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216819]: Could not generate persistent MAC address for vethf45f226: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216849]: Could not generate persistent MAC address for veth258af61: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216851]: Could not generate persistent MAC address for vethb7a86bd: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216883]: Could not generate persistent MAC address for vetha230122: No such file or directory Sep 18 21:41:21 sentry-docker00.cs.umd.edu systemd-udevd[3216884]: Could not generate persistent MAC address for veth5aeb518: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226161]: link_config: could not get ethtool features for vetha230122 Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226161]: Could not set offload features of vetha230122: No such device Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226231]: Could not generate persistent MAC address for veth4415fcf: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226232]: Could not generate persistent MAC address for vethc6ab66f: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226235]: Could not generate persistent MAC address for veth5f8d8e9: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226236]: Could not generate persistent MAC address for vethfc3a163: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226284]: Could not generate persistent MAC address for veth3761173: No such file or directory Sep 18 22:01:29 sentry-docker00.cs.umd.edu systemd-udevd[3226285]: Could not generate persistent MAC address for vethe499e41: No such file or directory ... 4 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 18 21:08:54 soul krb5_child[3382092]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Sep 18 21: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 21: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 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 18 21: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 21: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 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 18 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 3 total) == Sep 18 21:08:05 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 1 total) == Sep 18 21:28:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 12 total) == Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NPFxXF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NPFxXF. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 18 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 21:06:42 submit26-b9-f3 setroubleshoot[1880948]: 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 18 21:08:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (10 distinct, 10 total) == Sep 18 21:08:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.8mcYH8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.8mcYH8. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 18 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 21:24:45 submit26-b9-f4 setroubleshoot[1363701]: 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 == tma-0 (2 distinct, 2 total) == Sep 18 21:37:36 tma-0 sshd[29335]: error: maximum authentication attempts exceeded for root from 129.151.171.7 port 41164 ssh2 [preauth] Sep 18 21:37:36 tma-0 sshd[29335]: PAM service(sshd) ignoring max retries; 6 > 3