Command: /usr/local/sbin/syslog-digest.py Time : 0.0456s Status : exited 0 Output : Syslog digest — 2026-09-27 23:05 EDT Processed 2,518 lines, filtered 2,238 (88%). 280 unknown (191 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 23:03:40 b0b02.cs.umd.edu rustdesk[1859985]: cannot open display: == biggulp.cs.umd.edu (6 distinct, 7 total) == Sep 27 22:25:29 biggulp.cs.umd.edu sshd-session[566278]: pam_access(sshd:auth): access denied for user `admin' from `35.187.23.210' Sep 27 22:25:29 biggulp.cs.umd.edu krb5_child[566280]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 27 22:25:29 biggulp.cs.umd.edu sshd-session[566276]: error: PAM: System error for admin from 35.187.23.210 Sep 27 22:35:47 biggulp.cs.umd.edu sshd-session[567517]: pam_access(sshd:auth): access denied for user `admin' from `34.38.247.68' Sep 27 22:35:47 biggulp.cs.umd.edu sshd-session[567515]: error: PAM: System error for admin from 34.38.247.68 Sep 27 22:36:51 biggulp.cs.umd.edu sshd-session[567904]: error: Protocol major versions differ: 2 vs. 1 == cheezit.cs.umd.edu (6 distinct, 7 total) == Sep 27 22:29:22 cheezit.cs.umd.edu sshd-session[3826790]: pam_access(sshd:auth): access denied for user `admin' from `34.62.60.95' Sep 27 22:29:22 cheezit.cs.umd.edu krb5_child[3826792]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 27 22:29:22 cheezit.cs.umd.edu sshd-session[3826788]: error: PAM: System error for admin from 34.62.60.95 Sep 27 22:35:49 cheezit.cs.umd.edu sshd-session[3828531]: pam_access(sshd:auth): access denied for user `admin' from `207.175.19.77' Sep 27 22:35:49 cheezit.cs.umd.edu sshd-session[3828524]: error: PAM: System error for admin from 207.175.19.77 Sep 27 22:36:30 cheezit.cs.umd.edu sshd-session[3828583]: error: Protocol major versions differ: 2 vs. 1 == idm00 (1 distinct, 1 total) == Sep 27 22:54:09 idm00 named[4166701]: client @0x7f11a00742e8 10.73.240.42#56119: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 22:39:27 idmp0 named[1598691]: client @0x7f2d200347e8 10.73.240.43#58237: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 27 22:28:12 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == mcstic (3 distinct, 6 total) == Sep 27 22:24:24 mcstic krb5_child[1219449]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 27 22:24:28 mcstic sshd[1219444]: error: PAM: Authentication failure for admin from 35.240.102.59 Sep 27 22:28:16 mcstic sshd[1219688]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 18 total) == Sep 27 22:23:13 munin sudo[475778]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x9] Sep 27 22:23:13 munin sudo[475778]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x9] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 27 23:04:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. == newhonors2 (1 distinct, 24 total) == Sep 27 22:13:02 newhonors2 dhcpcd[3248566]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 27 22:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 48) *** Sep 27 22:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 48, QN: 57/57, ET: 0) *** Sep 27 22:05:09 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 49, QN: 5158/5158, ET: 8) *** Sep 27 22:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 49) *** Sep 27 22:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 49, QN: 49/49, ET: 0) *** Sep 27 22:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 50) *** Sep 27 22:10:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 51) *** Sep 27 22:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 50, QN: 3687/3687, ET: 0) *** Sep 27 22:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 50) *** Sep 27 22:10:02 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 50, QN: 79/79, ET: 1) *** Sep 27 22:10:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 51, QN: 3687/3687, ET: 6) *** Sep 27 22:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 51) *** Sep 27 22:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 51, QN: 78/78, ET: 0) *** Sep 27 22:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 52) *** Sep 27 22:15:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 53) *** Sep 27 22:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 52, QN: 3614/3614, ET: 0) *** Sep 27 22:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 52) *** Sep 27 22:15:02 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 52, QN: 62/62, ET: 1) *** Sep 27 22:15:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 53, QN: 3614/3614, ET: 6) *** Sep 27 22:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 53) *** Sep 27 22:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 53, QN: 67/67, ET: 0) *** Sep 27 22:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) *** Sep 27 22:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 55) *** Sep 27 22:20:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) *** Sep 27 22:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 66/66, ET: 0) *** Sep 27 22:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 3906/3906, ET: 0) *** Sep 27 22:20:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 3906/3906, ET: 6) *** Sep 27 22:21:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 55) *** Sep 27 22:21:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 69/69, ET: 0) *** Sep 27 22:25:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 56) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 22:09:09 outbound00.cs.umd.edu python3[384652]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 27 22:13:06 outbound01.cs.umd.edu python3[2650929]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971330]: link_config: could not get ethtool features for veth1e6e7ba Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971330]: Could not set offload features of veth1e6e7ba: No such device Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971404]: Could not generate persistent MAC address for vethfa41776: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971405]: Could not generate persistent MAC address for veth5dbedaf: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971408]: Could not generate persistent MAC address for vethe1fb3b9: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971409]: Could not generate persistent MAC address for veth4f6e472: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971416]: Could not generate persistent MAC address for veth31f3f05: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971411]: Could not generate persistent MAC address for veth3eade16: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971486]: Could not generate persistent MAC address for veth296d917: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971487]: Could not generate persistent MAC address for veth308a737: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971490]: Could not generate persistent MAC address for veth5a7bac5: No such file or directory Sep 27 22:10:51 sentry-docker00.cs.umd.edu systemd-udevd[971491]: Could not generate persistent MAC address for veth29e58fe: No such file or directory Sep 27 22:30:59 sentry-docker00.cs.umd.edu systemd-udevd[980822]: link_config: could not get ethtool features for vethfa41776 Sep 27 22:30:59 sentry-docker00.cs.umd.edu systemd-udevd[980822]: Could not set offload features of vethfa41776: No such device Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980852]: Could not generate persistent MAC address for vetha76d3ef: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980853]: Could not generate persistent MAC address for veth61d3a35: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980856]: Could not generate persistent MAC address for vethe61402b: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980857]: Could not generate persistent MAC address for veth949440e: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980880]: Could not generate persistent MAC address for vetha79010f: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980881]: Could not generate persistent MAC address for veth2a18057: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980899]: Could not generate persistent MAC address for vethf4b0cd1: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980896]: Could not generate persistent MAC address for veth11ce15a: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980934]: Could not generate persistent MAC address for vethcf8a3c9: No such file or directory Sep 27 22:31:00 sentry-docker00.cs.umd.edu systemd-udevd[980937]: Could not generate persistent MAC address for veth9a05134: No such file or directory Sep 27 22:51:07 sentry-docker00.cs.umd.edu systemd-udevd[990210]: link_config: could not get ethtool features for vetha76d3ef Sep 27 22:51:07 sentry-docker00.cs.umd.edu systemd-udevd[990210]: Could not set offload features of vetha76d3ef: No such device Sep 27 22:51:08 sentry-docker00.cs.umd.edu systemd-udevd[990248]: link_config: could not get ethtool features for vethe61402b Sep 27 22:51:08 sentry-docker00.cs.umd.edu systemd-udevd[990248]: Could not set offload features of vethe61402b: No such device Sep 27 22:51:08 sentry-docker00.cs.umd.edu systemd-udevd[990294]: Could not generate persistent MAC address for vethf02a805: No such file or directory Sep 27 22:51:08 sentry-docker00.cs.umd.edu systemd-udevd[990295]: Could not generate persistent MAC address for vethf34bb4c: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QmGl0N/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QmGl0N. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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 27 22:25:57 submit26-b9-f1 setroubleshoot[4022805]: 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, 12 total) == Sep 27 22:06:51 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:51 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:51 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:51 submit26-b9-f2 setroubleshoot[3098757]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.UFMl6M/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 27 22:06:51 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:52 submit26-b9-f2 setroubleshoot[3098757]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.UFMl6M. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 27 22:06:52 submit26-b9-f2 setroubleshoot[3098757]: SELinux is preventing /usr/bin/python3.9 from read access on the directory /tmp/libdnf.UFMl6M. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 27 22:06:52 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:52 submit26-b9-f2 setroubleshoot[3098757]: 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 27 22:06:52 submit26-b9-f2 setroubleshoot[3098757]: 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 == teaching-awards (1 distinct, 1 total) == Sep 27 22:30:31 teaching-awards krb5_child[1840805]: Client 'admin@UMD.EDU' not found in Kerberos database == unknown (1 distinct, 1 total) == using-explainable-ai == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 27 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[9804]: Process 5370 (driver) of user 33 killed by SIGABRT - dumping core Sep 27 22:11:59 vacuum.cs.umd.edu abrt-server[9806]: Package 'amanda-backup_server' isn't signed with proper key Sep 27 22:11:59 vacuum.cs.umd.edu abrt-server[9806]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-27-22:11:58-5370' exited with 1 Sep 27 22:11:59 vacuum.cs.umd.edu abrt-server[9806]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-27-22:11:58-5370'