Command: /usr/local/sbin/syslog-digest.py Time : 0.0456s Status : exited 0 Output : Syslog digest — 2026-09-30 03:05 EDT Processed 1,773 lines, filtered 1,447 (81%). 326 unknown (184 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 30 02:06:39 b0b02.cs.umd.edu rustdesk[2642552]: cannot open display: == biggulp.cs.umd.edu (6 distinct, 6 total) == Sep 30 02:57:19 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 02:57:19 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 02:57:20 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 02:57:20 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 02:57:22 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 02:57:22 biggulp.cs.umd.edu sshd-session[1125318]: error: kex_protocol_error: type 30 seq 7 [preauth] == cheezit.cs.umd.edu (7 distinct, 14 total) == Sep 30 02:24:39 cheezit.cs.umd.edu sshd-session[361364]: error: send_error: write: Connection reset by peer [x2] Sep 30 02:33:27 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 20 seq 2 [preauth] [x2] Sep 30 02:33:27 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 30 seq 3 [preauth] [x2] Sep 30 02:33:29 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 20 seq 4 [preauth] [x2] Sep 30 02:33:29 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 30 seq 5 [preauth] [x2] Sep 30 02:33:31 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 20 seq 6 [preauth] [x2] Sep 30 02:33:31 cheezit.cs.umd.edu sshd-session[364193]: error: kex_protocol_error: type 30 seq 7 [preauth] [x2] == idm00 (1 distinct, 1 total) == Sep 30 02:54:22 idm00 named[4166701]: client @0x7f11a40736b8 10.73.240.42#51228: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 02:39:27 idmp0 named[1598691]: client @0x7f2d3c0747e8 10.73.240.43#65144: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 30 02:38:01 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == newhonors2 (1 distinct, 24 total) == Sep 30 02:13:03 newhonors2 dhcpcd[3347342]: dhcpcd is not running [x24] == ntop00 (99 distinct, 99 total) == Sep 30 02:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 30 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 30 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 68/68, ET: 0) *** Sep 30 02:05:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 4113/4113, ET: 6) *** Sep 30 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 30 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 3960/3960, ET: 0) *** Sep 30 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 30 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 57/57, ET: 0) *** Sep 30 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 30 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 30 02:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 45/45, ET: 1) *** Sep 30 02:10:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 3946/3946, ET: 6) *** Sep 30 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 30 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 3850/3850, ET: 0) *** Sep 30 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 30 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 43/43, ET: 0) *** Sep 30 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 30 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 30 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 45/45, ET: 0) *** Sep 30 02:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 3867/3867, ET: 7) *** Sep 30 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 30 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4126/4126, ET: 0) *** Sep 30 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 30 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 48/48, ET: 0) *** Sep 30 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 30 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 30 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 58/58, ET: 0) *** Sep 30 02:20:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 4018/4018, ET: 6) *** Sep 30 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 449) *** Sep 30 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 449, QN: 3790/3790, ET: 0) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 30 02:09:09 outbound00.cs.umd.edu python3[1124832]: ldapdb [x6] Sep 30 02:52:34 outbound00.cs.umd.edu krb5_child[1134784]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 30 02:13:06 outbound01.cs.umd.edu python3[3388884]: ldapdb [x6] == portal (1 distinct, 69 total) == Sep 30 02:05:50 portal setroubleshoot[3631313]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x69] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442133]: link_config: could not get ethtool features for veth4e12018 Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442133]: Could not set offload features of veth4e12018: No such device Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442164]: Could not generate persistent MAC address for vethc91b699: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442165]: Could not generate persistent MAC address for veth656a09b: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442168]: Could not generate persistent MAC address for veth8c5a3d2: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442165]: Could not generate persistent MAC address for vethaec0f56: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442186]: Could not generate persistent MAC address for vethfcd2a20: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442181]: Could not generate persistent MAC address for veth08353ba: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442181]: Could not generate persistent MAC address for veth416f64f: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442186]: Could not generate persistent MAC address for vethf04d288: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442249]: Could not generate persistent MAC address for vethf73bb45: No such file or directory Sep 30 02:12:29 sentry-docker00.cs.umd.edu systemd-udevd[2442251]: Could not generate persistent MAC address for veth872b750: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451777]: link_config: could not get ethtool features for vethfcd2a20 Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451777]: Could not set offload features of vethfcd2a20: No such device Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451811]: Could not generate persistent MAC address for veth052ef0c: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451812]: Could not generate persistent MAC address for veth2b4eb0b: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451815]: Could not generate persistent MAC address for vetheb8fe1d: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451816]: Could not generate persistent MAC address for vethe3d354e: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451839]: Could not generate persistent MAC address for vethd1c1c22: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451840]: Could not generate persistent MAC address for veth06abc7e: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451858]: Could not generate persistent MAC address for veth93f7b08: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451856]: Could not generate persistent MAC address for veth93f8a15: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451850]: Could not generate persistent MAC address for veth683ab40: No such file or directory Sep 30 02:32:37 sentry-docker00.cs.umd.edu systemd-udevd[2451856]: Could not generate persistent MAC address for vethb1c50ee: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461458]: Could not generate persistent MAC address for veth32ee38a: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461459]: Could not generate persistent MAC address for veth79f7fdb: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461477]: Could not generate persistent MAC address for vethd8c2cf6: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461470]: Could not generate persistent MAC address for veth64f20da: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461476]: Could not generate persistent MAC address for vethe8118d7: No such file or directory Sep 30 02:52:46 sentry-docker00.cs.umd.edu systemd-udevd[2461484]: Could not generate persistent MAC address for vetha5186ad: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 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 30 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 30 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 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 30 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 30 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 12 total) == Sep 30 02:08:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: 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 [x2] Sep 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: 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 [x2] Sep 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: 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 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Z2bSGZ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: 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 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Z2bSGZ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 30 02:25:58 submit26-b9-f1 setroubleshoot[282651]: 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 30 02:25:59 submit26-b9-f1 setroubleshoot[282651]: 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 30 02:25:59 submit26-b9-f1 setroubleshoot[282651]: 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, 11 total) == Sep 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.HBXTOK/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.HBXTOK. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:06:52 submit26-b9-f2 setroubleshoot[3587969]: 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 30 02:20:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (1 distinct, 1 total) == Sep 30 02:25:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (1 distinct, 1 total) == Sep 30 02:20:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL