Command: /usr/local/sbin/syslog-digest.py Time : 0.0473s Status : exited 0 Output : Syslog digest — 2026-09-30 23:05 EDT Processed 1,898 lines, filtered 1,540 (81%). 358 unknown (194 distinct) from 24 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 30 22:07:46 b0b02.cs.umd.edu rustdesk[2948837]: cannot open display: == cheezit.cs.umd.edu (3 distinct, 3 total) == Sep 30 22:53:54 cheezit.cs.umd.edu sshd-session[684032]: pam_access(sshd:auth): access denied for user `admin' from `34.53.254.172' Sep 30 22:53:54 cheezit.cs.umd.edu krb5_child[684034]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 30 22:53:54 cheezit.cs.umd.edu sshd-session[684030]: error: PAM: System error for admin from 34.53.254.172 == idm00 (1 distinct, 1 total) == Sep 30 22:54:24 idm00 named[4166701]: client @0x7f11980727c8 10.73.240.42#53353: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 22:39:27 idmp0 named[1598691]: client @0x7f2d3c082968 10.73.240.43#52591: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (3 distinct, 4 total) == Sep 30 22:06:50 inbound00.cs.umd.edu krb5_child[1572101]: Preauthentication failed Sep 30 22:11:47 inbound00.cs.umd.edu krb5_child[1573244]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 30 22:31:26 inbound00.cs.umd.edu sshd-session[1578275]: error: Protocol major versions differ: 2 vs. 1 == inbound01.cs.umd.edu (3 distinct, 4 total) == Sep 30 22:30:26 inbound01.cs.umd.edu krb5_child[3788253]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 30 22:34:09 inbound01.cs.umd.edu krb5_child[3788994]: Preauthentication failed Sep 30 22:51:41 inbound01.cs.umd.edu sshd-session[3792518]: error: Protocol major versions differ: 2 vs. 1 == itmon02 (1 distinct, 3 total) == Sep 30 22:13:31 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (3 distinct, 3 total) == Sep 30 22:46:36 krispykreme.cs.umd.edu sshd-session[435010]: pam_access(sshd:auth): access denied for user `admin' from `34.76.242.54' Sep 30 22:46:36 krispykreme.cs.umd.edu krb5_child[435012]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 30 22:46:36 krispykreme.cs.umd.edu sshd-session[435008]: error: PAM: System error for admin from 34.76.242.54 == mcstic (3 distinct, 6 total) == Sep 30 22:45:57 mcstic krb5_child[1363122]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 30 22:46:02 mcstic sshd[1363117]: error: PAM: Authentication failure for admin from 34.52.250.155 Sep 30 22:46:21 mcstic sshd[1363131]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 16 total) == Sep 30 22:08:11 munin sudo[2040608]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Sep 30 22:08:11 munin sudo[2040608]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == newhonors2 (1 distinct, 24 total) == Sep 30 22:13:02 newhonors2 dhcpcd[3385709]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 30 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) *** Sep 30 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 60/60, ET: 0) *** Sep 30 22:05:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 3764/3764, ET: 6) *** Sep 30 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 923) *** Sep 30 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 3443/3443, ET: 0) *** Sep 30 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 923) *** Sep 30 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 54/54, ET: 0) *** Sep 30 22:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 924) *** Sep 30 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 924) *** Sep 30 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 924, QN: 55/55, ET: 0) *** Sep 30 22:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 924, QN: 3590/3590, ET: 5) *** Sep 30 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 925) *** Sep 30 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 3631/3631, ET: 0) *** Sep 30 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 925) *** Sep 30 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 72/72, ET: 0) *** Sep 30 22:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) *** Sep 30 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) *** Sep 30 22:15:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 80/80, ET: 1) *** Sep 30 22:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 3467/3467, ET: 5) *** Sep 30 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 927) *** Sep 30 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 52/52, ET: 0) *** Sep 30 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 927) *** Sep 30 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 3112/3112, ET: 0) *** Sep 30 22:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 928) *** Sep 30 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 928) *** Sep 30 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 928, QN: 41/41, ET: 0) *** Sep 30 22:20:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 928, QN: 3236/3236, ET: 4) *** Sep 30 22:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 929) *** Sep 30 22:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 929, QN: 69/69, ET: 0) *** Sep 30 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 929) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 30 22:09:09 outbound00.cs.umd.edu python3[1407843]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 30 22:13:06 outbound01.cs.umd.edu python3[3673351]: ldapdb [x6] == portal (1 distinct, 74 total) == Sep 30 22:05:54 portal setroubleshoot[3885975]: 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 [x74] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 30 23:02:46 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012275]: link_config: could not get ethtool features for veth8d55f19 Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012275]: Could not set offload features of veth8d55f19: No such device Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012314]: Could not generate persistent MAC address for veth807b691: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012315]: Could not generate persistent MAC address for veth38430d0: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012318]: Could not generate persistent MAC address for veth3ab4a13: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012322]: Could not generate persistent MAC address for veth4548fdb: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012337]: Could not generate persistent MAC address for veth66f8f92: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012324]: Could not generate persistent MAC address for veth40f93b8: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012337]: Could not generate persistent MAC address for veth42a9e1d: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012335]: Could not generate persistent MAC address for veth3ba2875: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012363]: Could not generate persistent MAC address for vethec5ebf1: No such file or directory Sep 30 22:20:48 sentry-docker00.cs.umd.edu systemd-udevd[3012368]: Could not generate persistent MAC address for vethe2b0a35: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021691]: link_config: could not get ethtool features for veth3ba2875 Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021691]: Could not set offload features of veth3ba2875: No such device Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021692]: link_config: could not get ethtool features for veth807b691 Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021692]: Could not set offload features of veth807b691: No such device Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021728]: Could not generate persistent MAC address for vethf42ccab: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021729]: Could not generate persistent MAC address for vethd3a36aa: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021732]: Could not generate persistent MAC address for veth23ea4ad: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021733]: Could not generate persistent MAC address for veth610b848: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021749]: Could not generate persistent MAC address for veth4092bb4: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021750]: Could not generate persistent MAC address for veth2dd437c: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021792]: Could not generate persistent MAC address for vethc65be28: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021800]: Could not generate persistent MAC address for vetha1893b3: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021809]: Could not generate persistent MAC address for vethfff8bdd: No such file or directory Sep 30 22:40:56 sentry-docker00.cs.umd.edu systemd-udevd[3021811]: Could not generate persistent MAC address for veth41c5084: No such file or directory Sep 30 23:01:05 sentry-docker00.cs.umd.edu systemd-udevd[3031130]: link_config: could not get ethtool features for veth23ea4ad Sep 30 23:01:05 sentry-docker00.cs.umd.edu systemd-udevd[3031130]: Could not set offload features of veth23ea4ad: No such device Sep 30 23:01:05 sentry-docker00.cs.umd.edu systemd-udevd[3031164]: Could not generate persistent MAC address for veth435ad20: No such file or directory Sep 30 23:01:05 sentry-docker00.cs.umd.edu systemd-udevd[3031165]: Could not generate persistent MAC address for veth391f37c: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 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 30 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 30 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 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 30 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 30 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 13 total) == Sep 30 22:10:06 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 30 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 30 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 30 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 22:25:59 submit26-b9-f1 setroubleshoot[374491]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.36hDIy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 30 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 22:25:59 submit26-b9-f1 setroubleshoot[374491]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.36hDIy. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 30 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 22:25:59 submit26-b9-f1 setroubleshoot[374491]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.uKX04g/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 30 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.uKX04g. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 30 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:06:53 submit26-b9-f2 setroubleshoot[3675754]: 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 22:08:09 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (1 distinct, 3 total) == Sep 30 22:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (1 distinct, 1 total) == Sep 30 22:18:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == tma-0 (1 distinct, 1 total) == Sep 30 22:37:15 tma-0 sshd[16006]: error: PAM: Authentication failure for admin from 84.146.52.34.bc.googleusercontent.com == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 30 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[7983]: Process 3511 (driver) of user 33 killed by SIGSEGV - dumping core Sep 30 22:11:58 vacuum.cs.umd.edu abrt-server[7985]: Package 'amanda-backup_server' isn't signed with proper key Sep 30 22:11:58 vacuum.cs.umd.edu abrt-server[7985]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-30-22:11:58-3511' exited with 1 Sep 30 22:11:58 vacuum.cs.umd.edu abrt-server[7985]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-30-22:11:58-3511'