Command: /usr/local/sbin/syslog-digest.py Time : 0.0553s Status : exited 0 Output : Syslog digest — 2026-09-20 15:05 EDT Processed 3,300 lines, filtered 2,774 (84%). 526 unknown (200 distinct) from 22 host(s). == abadi-computer (1 distinct, 1 total) == Sep 20 15:00:37 abadi-computer kernel: kauditd_printk_skb: 5 callbacks suppressed == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 20 14:15:41 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed Sep 20 14:24:54 atif01.cs.umd.edu kernel: net_ratelimit: 12 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 14:52:30 b0b02.cs.umd.edu rustdesk[3290658]: cannot open display: == bale (5 distinct, 83 total) == Sep 20 14:05:09 bale setroubleshoot[1191280]: failed to retrieve rpm info for /dev/nvme0 [x35] Sep 20 14:05:10 bale setroubleshoot[1191280]: 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 20 14:05:12 bale setroubleshoot[1191280]: 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 20 14:05:15 bale setroubleshoot[1191280]: 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 20 14:05:27 bale setroubleshoot[1191895]: 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] == biggulp.cs.umd.edu (6 distinct, 6 total) == Sep 20 14:34:54 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 14:34:54 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 14:34:55 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 14:34:55 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 14:34:57 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 14:34:57 biggulp.cs.umd.edu sshd-session[2832024]: error: kex_protocol_error: type 30 seq 7 [preauth] == cheezit.cs.umd.edu (6 distinct, 6 total) == Sep 20 14:28:45 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 14:28:45 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 14:28:45 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 14:28:45 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 14:28:47 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 14:28:47 cheezit.cs.umd.edu sshd-session[1265807]: error: kex_protocol_error: type 30 seq 7 [preauth] == csfw00a (2 distinct, 129 total) == Sep 20 14:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125] Sep 20 14:44:07 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x4] == idm00 (1 distinct, 1 total) == Sep 20 14:54:01 idm00 named[4166701]: client @0x7f11a00732a8 10.73.240.42#50241: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 14:37:56 idmp0 named[1598691]: client @0x7f2d24019b88 10.73.240.43#63722: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 20 14:08:49 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (6 distinct, 6 total) == Sep 20 14:27:45 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 14:27:45 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 14:27:47 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 14:27:47 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 14:27:49 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 14:27:49 krispykreme.cs.umd.edu sshd-session[337242]: error: kex_protocol_error: type 30 seq 7 [preauth] == newhonors2 (1 distinct, 24 total) == Sep 20 14:13:03 newhonors2 dhcpcd[2908126]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 20 14:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 154) *** Sep 20 14:05:37 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 9342/9342, ET: 36) *** Sep 20 14:05:37 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 68/68, ET: 36) *** Sep 20 14:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 155) *** Sep 20 14:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 9116/9116, ET: 0) *** Sep 20 14:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 155) *** Sep 20 14:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 76/76, ET: 0) *** Sep 20 14:08:02 ntop00 setroubleshoot[841961]: 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 20 14:08:02 ntop00 setroubleshoot[841961]: 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 20 14:08:02 ntop00 setroubleshoot[841961]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 20 14:08:02 ntop00 setroubleshoot[841961]: 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 20 14:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) *** Sep 20 14:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) *** Sep 20 14:10:34 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 8684/8684, ET: 33) *** Sep 20 14:10:35 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 67/67, ET: 34) *** Sep 20 14:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 157) *** Sep 20 14:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 9750/9750, ET: 0) *** Sep 20 14:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 157) *** Sep 20 14:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 88/88, ET: 0) *** Sep 20 14:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) *** Sep 20 14:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) *** Sep 20 14:15:40 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 10118/10118, ET: 39) *** Sep 20 14:15:40 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 76/76, ET: 39) *** Sep 20 14:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 159) *** Sep 20 14:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 9143/9143, ET: 0) *** Sep 20 14:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 159) *** Sep 20 14:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 74/74, ET: 0) *** Sep 20 14:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) *** Sep 20 14:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) *** Sep 20 14:20:33 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 160, QN: 8641/8641, ET: 32) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 14:09:09 outbound00.cs.umd.edu python3[2060742]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 14:13:06 outbound01.cs.umd.edu python3[126563]: ldapdb [x6] == portal (1 distinct, 2 total) == Sep 20 14:34:55 portal setroubleshoot[1849005]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l 7fd47d7d-0597-41f1-9a89-8a4911d8024d [x2] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172744]: link_config: could not get ethtool features for vethfe03e6d Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172744]: Could not set offload features of vethfe03e6d: No such device Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172790]: Could not generate persistent MAC address for vethd06d1b2: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172791]: Could not generate persistent MAC address for veth38f3dcc: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172794]: Could not generate persistent MAC address for vethf0b9bde: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172795]: Could not generate persistent MAC address for vethe4b6904: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172826]: Could not generate persistent MAC address for veth583b732: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172824]: Could not generate persistent MAC address for veth269da76: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172857]: Could not generate persistent MAC address for veth8c50a2e: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172860]: Could not generate persistent MAC address for vethff0e72d: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172907]: Could not generate persistent MAC address for vetha357f44: No such file or directory Sep 20 14:18:07 sentry-docker00.cs.umd.edu systemd-udevd[172908]: Could not generate persistent MAC address for vethcce5d08: No such file or directory Sep 20 14:38:15 sentry-docker00.cs.umd.edu systemd-udevd[182722]: link_config: could not get ethtool features for vethf0b9bde Sep 20 14:38:15 sentry-docker00.cs.umd.edu systemd-udevd[182722]: Could not set offload features of vethf0b9bde: No such device Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182760]: Could not generate persistent MAC address for veth43209b3: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182761]: Could not generate persistent MAC address for veth55c0a6d: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182779]: Could not generate persistent MAC address for vetha4a90d6: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182771]: Could not generate persistent MAC address for veth565ec09: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182784]: Could not generate persistent MAC address for vethdf982d4: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182785]: Could not generate persistent MAC address for veth1e73027: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182792]: Could not generate persistent MAC address for veth3f3f093: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182809]: Could not generate persistent MAC address for vethc8a7f74: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182784]: Could not generate persistent MAC address for veth2742700: No such file or directory Sep 20 14:38:16 sentry-docker00.cs.umd.edu systemd-udevd[182791]: Could not generate persistent MAC address for vethfcc93e1: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192145]: Could not generate persistent MAC address for veth575487d: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192146]: Could not generate persistent MAC address for veth7e08009: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192149]: Could not generate persistent MAC address for veth6e8f3bb: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192166]: Could not generate persistent MAC address for veth3087275: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192161]: Could not generate persistent MAC address for veth1305bfc: No such file or directory Sep 20 14:58:24 sentry-docker00.cs.umd.edu systemd-udevd[192162]: Could not generate persistent MAC address for veth8e2676e: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 Sep 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.i6TNz9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.i6TNz9. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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 20 14:25:54 submit26-b9-f1 setroubleshoot[2598198]: 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, 16 total) == Sep 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 [x2] Sep 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EHUVNH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Sep 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 [x2] Sep 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EHUVNH. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 20 14:06:49 submit26-b9-f2 setroubleshoot[1711523]: 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 20 14:13:55 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (1 distinct, 5 total) == Sep 20 14:15:00 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == wraith (3 distinct, 3 total) == Sep 20 14:30:03 wraith kernel: nvme 10000:e1:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Sep 20 14:30:03 wraith kernel: nvme 10000:e1:00.0: device [15b7:5015] error status/mask=00000001/0000e000 Sep 20 14:30:03 wraith kernel: nvme 10000:e1:00.0: [ 0] RxErr (First)