Command: /usr/local/sbin/syslog-digest.py Time : 0.0459s Status : exited 0 Output : Syslog digest — 2026-09-29 23:05 EDT Processed 1,746 lines, filtered 1,406 (80%). 340 unknown (196 distinct) from 24 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 29 22:06:28 b0b02.cs.umd.edu rustdesk[2580744]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 4 total) == Sep 29 23:00:38 biggulp.cs.umd.edu sshd-session[1077206]: error: send_error: write: Connection reset by peer [x4] == cheezit.cs.umd.edu (2 distinct, 2 total) == Sep 29 22:05:02 cheezit.cs.umd.edu sshd-session[299958]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 29 22:05:02 cheezit.cs.umd.edu sshd-session[299958]: error: kex_protocol_error: type 30 seq 7 [preauth] == cmsc436-0101-redis (2 distinct, 2 total) == Sep 29 22:46:47 cmsc436-0101-redis krb5_child[3861542]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 29 22:46:49 cmsc436-0101-redis sshd-session[3861538]: error: PAM: Authentication failure for admin from 34.156.143.100 == galax (1 distinct, 1 total) == Sep 29 23:03:50 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 32771 times, consider switching to WQ_UNBOUND == gle-dind04 (1 distinct, 1 total) == Sep 29 22:58:12 gle-dind04 lldpd[1171]: unable to send packet on real device for vethb88de3a: No such device or address == idm00 (2 distinct, 2 total) == Sep 29 22:08:54 idm00 sshd-session[1602596]: error: Certificate does not contain an authorized principal Sep 29 22:54:22 idm00 named[4166701]: client @0x7f11a40736b8 10.73.240.42#55889: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 29 22:39:27 idmp0 named[1598691]: client @0x7f2d34049808 10.73.240.43#49753: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (2 distinct, 2 total) == Sep 29 22:09:32 inbound01.cs.umd.edu krb5_child[3439261]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 29 22:14:37 inbound01.cs.umd.edu sshd-session[3440421]: error: Protocol major versions differ: 2 vs. 1 == irb2156 (2 distinct, 2 total) == Sep 29 23:01:34 irb2156 systemd-resolved[3579]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.73.244.14. Sep 29 23:01:55 irb2156 systemd-resolved[3579]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.14. == itmon02 (1 distinct, 8 total) == Sep 29 22:07:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x8] == krispykreme.cs.umd.edu (6 distinct, 6 total) == Sep 29 22:07:16 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 29 22:07:16 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 29 22:07:17 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 29 22:07:17 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 29 22:07:19 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 29 22:07:19 krispykreme.cs.umd.edu sshd-session[17994]: error: kex_protocol_error: type 30 seq 7 [preauth] == mcstic (1 distinct, 2 total) == Sep 29 22:08:18 mcstic krb5_child[1313656]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Sep 29 22:13:03 newhonors2 dhcpcd[3339787]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 29 22:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 29 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 29 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 68/68, ET: 0) *** Sep 29 22:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 4585/4585, ET: 7) *** Sep 29 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 29 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 3728/3728, ET: 0) *** Sep 29 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 29 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 72/72, ET: 0) *** Sep 29 22:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 29 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 29 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 58/58, ET: 0) *** Sep 29 22:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 3610/3610, ET: 5) *** Sep 29 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 29 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 3875/3875, ET: 0) *** Sep 29 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 29 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 46/46, ET: 0) *** Sep 29 22:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 29 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 29 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 61/61, ET: 0) *** Sep 29 22:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 3925/3925, ET: 5) *** Sep 29 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 29 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 3657/3657, ET: 0) *** Sep 29 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 29 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 76/76, ET: 0) *** Sep 29 22:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 29 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 29 22:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 72/72, ET: 1) *** Sep 29 22:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 3509/3509, ET: 5) *** Sep 29 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 353) *** Sep 29 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 3724/3724, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 29 22:09:09 outbound00.cs.umd.edu python3[1067989]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Sep 29 22:13:06 outbound01.cs.umd.edu python3[3331943]: ldapdb [x6] Sep 29 22:44:12 outbound01.cs.umd.edu krb5_child[3339146]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 29 22:47:21 outbound01.cs.umd.edu sshd-session[3339790]: error: Protocol major versions differ: 2 vs. 1 == portal (1 distinct, 65 total) == Sep 29 22:06:10 portal setroubleshoot[3580526]: 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 [x65] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328603]: link_config: could not get ethtool features for veth1f67d03 Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328603]: Could not set offload features of veth1f67d03: No such device Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328603]: link_config: could not get ethtool features for vethd676b2d Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328603]: Could not set offload features of vethd676b2d: No such device Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328633]: Could not generate persistent MAC address for vethff629b6: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328634]: Could not generate persistent MAC address for vethcad7652: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328637]: Could not generate persistent MAC address for veth392bd23: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328638]: Could not generate persistent MAC address for vethf70bdc5: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328661]: Could not generate persistent MAC address for veth8863e2c: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328662]: Could not generate persistent MAC address for veth7784952: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328680]: Could not generate persistent MAC address for veth50a21a4: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328668]: Could not generate persistent MAC address for veth073f55c: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328689]: Could not generate persistent MAC address for vethdf246b3: No such file or directory Sep 29 22:10:49 sentry-docker00.cs.umd.edu systemd-udevd[2328690]: Could not generate persistent MAC address for veth5f08e91: No such file or directory Sep 29 22:30:57 sentry-docker00.cs.umd.edu systemd-udevd[2338270]: link_config: could not get ethtool features for vethdf246b3 Sep 29 22:30:57 sentry-docker00.cs.umd.edu systemd-udevd[2338270]: Could not set offload features of vethdf246b3: No such device Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338306]: Could not generate persistent MAC address for veth1694d76: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338307]: Could not generate persistent MAC address for veth32ed079: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338325]: Could not generate persistent MAC address for vethd0af427: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338315]: Could not generate persistent MAC address for veth9986bd2: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338324]: Could not generate persistent MAC address for veth8f6041b: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338315]: Could not generate persistent MAC address for vethe5154b0: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338338]: Could not generate persistent MAC address for veth67b2cc1: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338336]: Could not generate persistent MAC address for veth986bc1e: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338358]: Could not generate persistent MAC address for veth1d6f234: No such file or directory Sep 29 22:30:58 sentry-docker00.cs.umd.edu systemd-udevd[2338373]: Could not generate persistent MAC address for vethb9d822a: No such file or directory Sep 29 22:51:05 sentry-docker00.cs.umd.edu systemd-udevd[2347622]: link_config: could not get ethtool features for veth986bc1e Sep 29 22:51:05 sentry-docker00.cs.umd.edu systemd-udevd[2347622]: Could not set offload features of veth986bc1e: No such device Sep 29 22:51:06 sentry-docker00.cs.umd.edu systemd-udevd[2347693]: Could not generate persistent MAC address for veth7c864ac: No such file or directory Sep 29 22:51:06 sentry-docker00.cs.umd.edu systemd-udevd[2347694]: Could not generate persistent MAC address for vethc5da609: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 29 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 29 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 29 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 29 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 29 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 29 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 29 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.0BAbgD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.0BAbgD. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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 29 22:25:58 submit26-b9-f1 setroubleshoot[207221]: 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, 14 total) == Sep 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: 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 [x2] Sep 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: 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 [x2] Sep 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: 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 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nY32x2/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: 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 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nY32x2. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 29 22:06:52 submit26-b9-f2 setroubleshoot[3477489]: 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 [x2] Sep 29 22:06:53 submit26-b9-f2 setroubleshoot[3477489]: 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 29 22:06:53 submit26-b9-f2 setroubleshoot[3477489]: 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 [x2] Sep 29 22:06:53 submit26-b9-f2 setroubleshoot[3477489]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6kyZ5E. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 == teaching-awards (2 distinct, 3 total) == Sep 29 22:26:03 teaching-awards krb5_child[2008164]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 29 22:39:30 teaching-awards sshd-session[2008850]: error: Protocol major versions differ: 2 vs. 1 == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 29 22:11:57 vacuum.cs.umd.edu abrt-hook-ccpp[19384]: Process 14963 (driver) of user 33 killed by SIGABRT - dumping core Sep 29 22:11:58 vacuum.cs.umd.edu abrt-server[19386]: Package 'amanda-backup_server' isn't signed with proper key Sep 29 22:11:58 vacuum.cs.umd.edu abrt-server[19386]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-29-22:11:57-14963' exited with 1 Sep 29 22:11:58 vacuum.cs.umd.edu abrt-server[19386]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-29-22:11:57-14963'