Command: /usr/local/sbin/syslog-digest.py Time : 0.0513s Status : exited 0 Output : Syslog digest — 2026-09-21 03:05 EDT Processed 2,152 lines, filtered 1,608 (74%). 544 unknown (197 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 02:53:15 b0b02.cs.umd.edu rustdesk[3474254]: cannot open display: == bale (5 distinct, 93 total) == Sep 21 02:05:23 bale setroubleshoot[1344989]: failed to retrieve rpm info for /dev/nvme0 [x40] Sep 21 02:05:24 bale setroubleshoot[1344989]: 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 21 02:05:26 bale setroubleshoot[1344989]: 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 21 02:05:29 bale setroubleshoot[1344989]: 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 21 02:05:41 bale setroubleshoot[1345616]: 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 [x16] == cheezit.cs.umd.edu (6 distinct, 6 total) == Sep 21 03:03:45 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 21 03:03:45 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 21 03:03:47 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 21 03:03:47 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 21 03:03:51 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 21 03:03:51 cheezit.cs.umd.edu sshd-session[1441483]: error: kex_protocol_error: type 30 seq 7 [preauth] == csfw00a (1 distinct, 139 total) == Sep 21 02:03:57 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x139] == idm00 (1 distinct, 1 total) == Sep 21 02:54:01 idm00 named[4166701]: client @0x7f11a0062908 10.73.240.42#64426: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 02:37:56 idmp0 named[1598691]: client @0x7f2d34049808 10.73.240.43#52449: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 21 02:13:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (9 distinct, 10 total) == Sep 21 02:08:09 krispykreme.cs.umd.edu sshd-session[536092]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 21 02:08:10 krispykreme.cs.umd.edu sshd-session[536092]: Error in Duo login for 'larry' from 71.191.93.172 Sep 21 02:08:10 krispykreme.cs.umd.edu sshd-session[536090]: error: PAM: Authentication failure for larry from 71.191.93.172 Sep 21 03:03:42 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 21 03:03:42 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 21 03:03:46 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 21 03:03:46 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 21 03:03:48 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 21 03:03:48 krispykreme.cs.umd.edu sshd-session[551306]: error: kex_protocol_error: type 30 seq 7 [preauth] == matrix (2 distinct, 3 total) == Sep 21 02:51:34 matrix krb5_child[3687972]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 21 02:51:36 matrix sshd[3687966]: error: PAM: Authentication failure for admin from 104.199.98.110 == munin (2 distinct, 8 total) == Sep 21 02:53:43 munin sudo[1110625]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 21 02:53:43 munin sudo[1110625]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 21 02:13:03 newhonors2 dhcpcd[2930551]: dhcpcd is not running [x24] == ntop00 (101 distinct, 145 total) == Sep 21 02:05:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 21 02:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 21 02:05:47 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 10855/10855, ET: 46) *** Sep 21 02:05:47 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 66/66, ET: 46) *** Sep 21 02:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 21 02:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 10859/10859, ET: 0) *** Sep 21 02:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 21 02:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 60/60, ET: 0) *** Sep 21 02:08:02 ntop00 setroubleshoot[937036]: 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 02:08:02 ntop00 setroubleshoot[937036]: 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 02:08:02 ntop00 setroubleshoot[937036]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 02:08:02 ntop00 setroubleshoot[937036]: 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 02:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 21 02:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 21 02:10:51 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 11171/11171, ET: 50) *** Sep 21 02:10:51 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 54/54, ET: 50) *** Sep 21 02:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 21 02:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 11584/11584, ET: 0) *** Sep 21 02:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 21 02:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 61/61, ET: 0) *** Sep 21 02:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 21 02:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 21 02:15:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 11434/11434, ET: 51) *** Sep 21 02:15:52 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 62/62, ET: 51) *** Sep 21 02:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 21 02:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 11123/11123, ET: 0) *** Sep 21 02:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 21 02:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 65/65, ET: 0) *** Sep 21 02:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 21 02:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 02:09:09 outbound00.cs.umd.edu python3[2230633]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 21 02:13:06 outbound01.cs.umd.edu python3[297149]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: link_config: could not get ethtool features for veth8f92d0b Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: Could not set offload features of veth8f92d0b: No such device Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513620]: Could not generate persistent MAC address for vethbbf43a2: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513614]: Could not generate persistent MAC address for veth16820e3: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513662]: Could not generate persistent MAC address for veth725441e: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513663]: Could not generate persistent MAC address for veth3428f23: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513666]: Could not generate persistent MAC address for veth9fcb719: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513671]: Could not generate persistent MAC address for veth1b40c0f: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513686]: Could not generate persistent MAC address for veth81eacfa: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513667]: Could not generate persistent MAC address for vethfd69725: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513727]: Could not generate persistent MAC address for vetha3f1aee: No such file or directory Sep 21 02:23:07 sentry-docker00.cs.umd.edu systemd-udevd[513720]: Could not generate persistent MAC address for vetha8d4201: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523030]: link_config: could not get ethtool features for veth9fcb719 Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523030]: Could not set offload features of veth9fcb719: No such device Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523066]: Could not generate persistent MAC address for vethb94c51d: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523067]: Could not generate persistent MAC address for vethc2a1ef0: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523070]: Could not generate persistent MAC address for veth13cab11: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523071]: Could not generate persistent MAC address for vethbaf54c2: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for veth2e71221: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523081]: Could not generate persistent MAC address for veth86e279f: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523071]: Could not generate persistent MAC address for veth6f2896c: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for vethc8e073d: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523087]: Could not generate persistent MAC address for veth2a6b149: No such file or directory Sep 21 02:43:15 sentry-docker00.cs.umd.edu systemd-udevd[523089]: Could not generate persistent MAC address for vetha2cfbdd: No such file or directory Sep 21 03:03:23 sentry-docker00.cs.umd.edu systemd-udevd[532856]: link_config: could not get ethtool features for vetha2cfbdd Sep 21 03:03:23 sentry-docker00.cs.umd.edu systemd-udevd[532856]: Could not set offload features of vetha2cfbdd: No such device Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532899]: Could not generate persistent MAC address for veth35c8a83: No such file or directory Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532900]: Could not generate persistent MAC address for vethecda9dc: No such file or directory Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532903]: Could not generate persistent MAC address for vethc0b87c8: No such file or directory Sep 21 03:03:24 sentry-docker00.cs.umd.edu systemd-udevd[532904]: Could not generate persistent MAC address for veth39130cb: No such file or directory ... 6 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 21 02:48:51 soul krb5_child[3893543]: Client 'terry@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Sep 21 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 11 total) == Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2] Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.veJuER/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2] Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.veJuER. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Sep 21 02:25:54 submit26-b9-f1 setroubleshoot[2671527]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (10 distinct, 10 total) == Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zGNCBw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.zGNCBw. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 21 02:06:49 submit26-b9-f2 setroubleshoot[1782570]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7 Sep 21 02:55:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (1 distinct, 3 total) == Sep 21 02:27:36 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]