Command: /usr/local/sbin/syslog-digest.py Time : 0.0577s Status : exited 0 Output : Syslog digest — 2026-09-19 02:05 EDT Processed 3,385 lines, filtered 2,789 (82%). 596 unknown (199 distinct) from 20 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Sep 19 01:31:35 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 01:50:15 b0b02.cs.umd.edu rustdesk[2724185]: cannot open display: == bale (6 distinct, 84 total) == Sep 19 01:05:23 bale setroubleshoot[716468]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 19 01:05:23 bale setroubleshoot[716468]: 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 19 01:05:26 bale setroubleshoot[716468]: 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 19 01:05:29 bale setroubleshoot[716468]: 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 19 01:05:41 bale setroubleshoot[717095]: 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] Sep 19 01:45:36 bale setroubleshoot[724876]: SELinux is preventing smartctl from 'read, open' accesses on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 1e5089ac-b715-4395-b985-b89be7cbd438 == csfw00a (1 distinct, 139 total) == Sep 19 01:03:48 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 19 01:21:02 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 19 01:53:58 idm00 named[4166701]: client @0x7f11a4006dd8 10.73.240.42#59602: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 01:37:58 idmp0 named[1598691]: client @0x7f2d200319e8 10.73.240.43#55122: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 19 01:13:31 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (6 distinct, 7 total) == Sep 19 01:37:24 krispykreme.cs.umd.edu sshd-session[3911559]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 19 01:37:25 krispykreme.cs.umd.edu sshd-session[3911559]: Error in Duo login for 'larry' from 71.191.93.172 Sep 19 01:37:25 krispykreme.cs.umd.edu sshd-session[3911557]: error: PAM: Authentication failure for larry from 71.191.93.172 Sep 19 01:51:01 krispykreme.cs.umd.edu sshd-session[3914764]: pam_access(sshd:auth): access denied for user `admin' from `35.187.108.183' Sep 19 01:51:01 krispykreme.cs.umd.edu krb5_child[3914766]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 19 01:51:01 krispykreme.cs.umd.edu sshd-session[3914762]: error: PAM: System error for admin from 35.187.108.183 == munin (2 distinct, 12 total) == Sep 19 01:09:01 munin sudo[28312]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 19 01:09:01 munin sudo[28312]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 19 01:13:02 newhonors2 dhcpcd[2838016]: dhcpcd is not running [x24] == ntop00 (101 distinct, 145 total) == Sep 19 01:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 19 01:05:22 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6847/6847, ET: 21) *** Sep 19 01:05:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 59/59, ET: 22) *** Sep 19 01:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 19 01:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6992/6992, ET: 0) *** Sep 19 01:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 19 01:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 48/48, ET: 0) *** Sep 19 01:08:02 ntop00 setroubleshoot[546990]: 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 19 01:08:02 ntop00 setroubleshoot[546990]: 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 19 01:08:02 ntop00 setroubleshoot[546990]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 01:08:02 ntop00 setroubleshoot[546990]: 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 19 01:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 19 01:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 19 01:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 51/51, ET: 0) *** Sep 19 01:10:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 7276/7276, ET: 23) *** Sep 19 01:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 19 01:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 61/61, ET: 0) *** Sep 19 01:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 19 01:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 7545/7545, ET: 0) *** Sep 19 01:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 19 01:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 19 01:15:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 7872/7872, ET: 24) *** Sep 19 01:15:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 59/59, ET: 24) *** Sep 19 01:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 19 01:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 63/63, ET: 0) *** Sep 19 01:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 19 01:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 7844/7844, ET: 0) *** Sep 19 01:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 19 01:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 19 01:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 72/72, ET: 0) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 01:09:09 outbound00.cs.umd.edu python3[1539422]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 01:13:06 outbound01.cs.umd.edu python3[3797657]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320634]: link_config: could not get ethtool features for vethd4d10cc Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320634]: Could not set offload features of vethd4d10cc: No such device Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320668]: Could not generate persistent MAC address for veth0e90554: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320669]: Could not generate persistent MAC address for veth9b9a303: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320672]: Could not generate persistent MAC address for vethbaf7ddc: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320673]: Could not generate persistent MAC address for vethb357ffb: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320696]: Could not generate persistent MAC address for vethf2425ef: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320697]: Could not generate persistent MAC address for veth4eaf0f2: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320696]: Could not generate persistent MAC address for veth496652a: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320701]: Could not generate persistent MAC address for vethd579039: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320704]: Could not generate persistent MAC address for veth6ea75d5: No such file or directory Sep 19 01:22:52 sentry-docker00.cs.umd.edu systemd-udevd[3320710]: Could not generate persistent MAC address for veth5e78a7e: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330081]: link_config: could not set ethtool features for vethbaf7ddc Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330081]: Could not set offload features of vethbaf7ddc: Operation not permitted Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330121]: Could not generate persistent MAC address for veth3b9eae2: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330122]: Could not generate persistent MAC address for veth9ecbc95: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330126]: Could not generate persistent MAC address for veth7e857c7: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330125]: Could not generate persistent MAC address for veth5cbc686: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330125]: Could not generate persistent MAC address for vethad4adde: No such file or directory Sep 19 01:43:00 sentry-docker00.cs.umd.edu systemd-udevd[3330146]: Could not generate persistent MAC address for vetha4ee9d3: No such file or directory Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330152]: Could not generate persistent MAC address for veth707a0c5: No such file or directory Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330156]: Could not generate persistent MAC address for veth9b9d969: No such file or directory Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330189]: Could not generate persistent MAC address for veth9820e61: No such file or directory Sep 19 01:43:01 sentry-docker00.cs.umd.edu systemd-udevd[3330186]: Could not generate persistent MAC address for veth23689d8: No such file or directory Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339491]: link_config: could not set ethtool features for veth707a0c5 Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339491]: Could not set offload features of veth707a0c5: Operation not permitted Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339528]: Could not generate persistent MAC address for veth347fdab: No such file or directory Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339529]: Could not generate persistent MAC address for veth421aa8d: No such file or directory Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339532]: Could not generate persistent MAC address for veth04643e7: No such file or directory Sep 19 02:03:09 sentry-docker00.cs.umd.edu systemd-udevd[3339533]: Could not generate persistent MAC address for veth2f1fe34: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 12 total) == Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.IkqhPV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.IkqhPV. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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 19 01:06:42 submit26-b9-f3 setroubleshoot[1938437]: 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, 9 total) == Sep 19 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:46 submit26-b9-f4 setroubleshoot[1401957]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WsFtHa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WsFtHa. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 19 01:24:47 submit26-b9-f4 setroubleshoot[1401957]: 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 == teaching-awards (2 distinct, 2 total) == Sep 19 01:24:51 teaching-awards krb5_child[1064258]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 19 01:25:10 teaching-awards sshd-session[1064266]: error: Protocol major versions differ: 2 vs. 1 == tma-0 (1 distinct, 1 total) == Sep 19 01:49:40 tma-0 sshd[24870]: error: PAM: Authentication failure for admin from 71.221.175.207.bc.googleusercontent.com