Command: /usr/local/sbin/syslog-digest.py Time : 0.0558s Status : exited 0 Output : Syslog digest — 2026-09-21 02:05 EDT Processed 3,142 lines, filtered 2,554 (81%). 588 unknown (203 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 01:53:12 b0b02.cs.umd.edu rustdesk[3459018]: cannot open display: == bale (5 distinct, 86 total) == Sep 21 01:05:15 bale setroubleshoot[1332102]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 21 01:05:16 bale setroubleshoot[1332102]: 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 01:05:18 bale setroubleshoot[1332102]: 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 01:05:21 bale setroubleshoot[1332102]: 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 01:05:33 bale setroubleshoot[1332719]: 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] == biggulp.cs.umd.edu (3 distinct, 3 total) == Sep 21 01:57:57 biggulp.cs.umd.edu sshd-session[2949804]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214' Sep 21 01:57:58 biggulp.cs.umd.edu krb5_child[2949822]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 21 01:57:58 biggulp.cs.umd.edu sshd-session[2949802]: error: PAM: System error for admin from 193.187.110.214 == cmsc436-0101-redis (1 distinct, 1 total) == Sep 21 01:15:55 cmsc436-0101-redis sshd-session[3364158]: error: PAM: Authentication failure for operator from 193.187.110.214 == csfw00a (1 distinct, 127 total) == Sep 21 01:03:48 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x127] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 21 01:16:51 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 21 01:54:01 idm00 named[4166701]: client @0x7f1198079d88 10.73.240.42#52035: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 01:37:56 idmp0 named[1598691]: client @0x7f2d2c0368e8 10.73.240.43#60956: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 2 total) == Sep 21 01:11:10 inbound00.cs.umd.edu krb5_child[2350790]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 21 01:11:39 inbound00.cs.umd.edu sshd-session[2350826]: error: Protocol major versions differ: 2 vs. 1 == inbound01.cs.umd.edu (2 distinct, 2 total) == Sep 21 01:22:46 inbound01.cs.umd.edu krb5_child[377095]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 21 01:23:06 inbound01.cs.umd.edu sshd-session[377104]: error: Protocol major versions differ: 2 vs. 1 == itmon02 (1 distinct, 7 total) == Sep 21 01:14:00 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7] == munin (2 distinct, 8 total) == Sep 21 01:18:09 munin sudo[1075241]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 21 01:18:09 munin sudo[1075241]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 21 01:13:03 newhonors2 dhcpcd[2928706]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 21 01:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 21 01:05:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 7248/7248, ET: 31) *** Sep 21 01:05:32 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 42/42, ET: 31) *** Sep 21 01:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 21 01:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 7315/7315, ET: 0) *** Sep 21 01:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 21 01:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 40/40, ET: 0) *** Sep 21 01:08:02 ntop00 setroubleshoot[928991]: 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 01:08:02 ntop00 setroubleshoot[928991]: 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 01:08:02 ntop00 setroubleshoot[928991]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 01:08:02 ntop00 setroubleshoot[928991]: 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 01:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 21 01:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 21 01:10:35 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 7580/7580, ET: 34) *** Sep 21 01:10:35 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 52/52, ET: 34) *** Sep 21 01:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 21 01:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 7635/7635, ET: 0) *** Sep 21 01:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 21 01:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 44/44, ET: 0) *** Sep 21 01:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 21 01:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 21 01:15:35 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 7296/7296, ET: 34) *** Sep 21 01:15:35 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 36/36, ET: 34) *** Sep 21 01:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 21 01:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 35/35, ET: 0) *** Sep 21 01:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 21 01:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 7553/7553, ET: 0) *** Sep 21 01:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 21 01:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 21 01:20:37 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 7850/7850, ET: 36) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 01:09:09 outbound00.cs.umd.edu python3[2216669]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 21 01:13:06 outbound01.cs.umd.edu python3[283029]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485315]: link_config: could not get ethtool features for vetheadb795 Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485315]: Could not set offload features of vetheadb795: No such device Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485379]: Could not generate persistent MAC address for veth7561f77: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485380]: Could not generate persistent MAC address for veth779dadb: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485383]: Could not generate persistent MAC address for veth8641e88: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485384]: Could not generate persistent MAC address for veth4f86a53: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485407]: Could not generate persistent MAC address for vethdbdeaf6: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485408]: Could not generate persistent MAC address for veth47a2a63: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485426]: Could not generate persistent MAC address for veth88c53d0: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485433]: Could not generate persistent MAC address for vethf3b2e4e: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485440]: Could not generate persistent MAC address for vethb671a97: No such file or directory Sep 21 01:22:42 sentry-docker00.cs.umd.edu systemd-udevd[485446]: Could not generate persistent MAC address for veth4ed4f22: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494790]: link_config: could not get ethtool features for veth7561f77 Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494790]: Could not set offload features of veth7561f77: No such device Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494792]: link_config: could not get ethtool features for veth8641e88 Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494792]: Could not set offload features of veth8641e88: No such device Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494833]: Could not generate persistent MAC address for vethc8a6ab4: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494834]: Could not generate persistent MAC address for veth44af3e2: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494837]: Could not generate persistent MAC address for vethad21fb4: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494838]: Could not generate persistent MAC address for vethb5f3226: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494861]: Could not generate persistent MAC address for veth32f2656: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494862]: Could not generate persistent MAC address for veth4862a45: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494885]: Could not generate persistent MAC address for vethab0f164: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494871]: Could not generate persistent MAC address for veth3689c81: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494869]: Could not generate persistent MAC address for veth0fbc5af: No such file or directory Sep 21 01:42:50 sentry-docker00.cs.umd.edu systemd-udevd[494861]: Could not generate persistent MAC address for veth6b91818: No such file or directory Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504140]: link_config: could not get ethtool features for veth3689c81 Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504140]: Could not set offload features of veth3689c81: No such device Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504171]: link_config: could not set ethtool features for vethc8a6ab4 Sep 21 02:02:58 sentry-docker00.cs.umd.edu systemd-udevd[504171]: Could not set offload features of vethc8a6ab4: Operation not permitted ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 21 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 21 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 21 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 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 21 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 21 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Sep 21 01:08:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 2 total) == Sep 21 01:23:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (10 distinct, 11 total) == Sep 21 01:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.OIYCwp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.OIYCwp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 21 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2213617]: 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, 10 total) == Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DBMvD3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.DBMvD3. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 21 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1592053]: 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 01:24:48 submit26-b9-f4 setroubleshoot[1592053]: 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 Sep 21 01:43:08 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == tma-0 (1 distinct, 1 total) == Sep 21 01:12:53 tma-0 sshd[13127]: error: PAM: Authentication failure for admin from 79.62.62.34.bc.googleusercontent.com