Command: /usr/local/sbin/syslog-digest.py Time : 0.0484s Status : exited 0 Output : Syslog digest — 2026-10-05 23:05 EDT Processed 2,221 lines, filtered 1,869 (84%). 352 unknown (201 distinct) from 24 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 5 22:15:23 b0b02.cs.umd.edu rustdesk[651248]: cannot open display: == cheezit.cs.umd.edu (7 distinct, 9 total) == Oct 5 22:22:24 cheezit.cs.umd.edu sshd-session[2444364]: pam_access(sshd:auth): access denied for user `admin' from `104.199.73.56' Oct 5 22:22:24 cheezit.cs.umd.edu krb5_child[2444369]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Oct 5 22:22:24 cheezit.cs.umd.edu sshd-session[2444361]: error: PAM: System error for admin from 104.199.73.56 Oct 5 22:24:09 cheezit.cs.umd.edu sshd-session[2444468]: error: Protocol major versions differ: 2 vs. 1 [x2] Oct 5 22:47:28 cheezit.cs.umd.edu sshd-session[2450156]: pam_access(sshd:auth): access denied for user `admin' from `34.62.220.24' Oct 5 22:47:28 cheezit.cs.umd.edu sshd-session[2450154]: error: PAM: System error for admin from 34.62.220.24 Oct 5 23:00:16 cheezit.cs.umd.edu sshd-session[2453490]: error: send_error: write: Connection reset by peer == gle-dind02.cs.umd.edu (4 distinct, 4 total) == Oct 5 22:10:21 gle-dind02.cs.umd.edu systemd-udevd[1264570]: Could not generate persistent MAC address for veth67bcb4b: No such file or directory Oct 5 22:10:21 gle-dind02.cs.umd.edu systemd-udevd[1264571]: Could not generate persistent MAC address for veth1175612: No such file or directory Oct 5 22:10:30 gle-dind02.cs.umd.edu systemd-udevd[1264691]: Could not generate persistent MAC address for vethb85261c: No such file or directory Oct 5 22:10:30 gle-dind02.cs.umd.edu systemd-udevd[1264692]: Could not generate persistent MAC address for veth3f0e999: No such file or directory == gle-dind04 (3 distinct, 3 total) == Oct 5 22:39:27 gle-dind04 lldpd[1171]: unable to send packet on real device for veth7d7dc77: No such device or address Oct 5 23:03:27 gle-dind04 lldpd[1171]: unable to send packet on real device for vethabe1ffc: No such device or address Oct 5 23:04:45 gle-dind04 lldpd[1171]: unable to send packet on real device for vethc2b766c: No such device or address == idm00 (1 distinct, 1 total) == Oct 5 22:54:39 idm00 named[4166701]: client @0x7f11a4064588 10.73.240.42#64087: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 5 22:39:23 idmp0 named[1598691]: client @0x7f2d4c000cc8 10.73.240.43#60409: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Oct 5 22:42:56 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (6 distinct, 7 total) == Oct 5 22:28:15 krispykreme.cs.umd.edu sshd-session[2411399]: pam_access(sshd:auth): access denied for user `admin' from `34.22.229.111' Oct 5 22:28:15 krispykreme.cs.umd.edu krb5_child[2411401]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Oct 5 22:28:15 krispykreme.cs.umd.edu sshd-session[2411397]: error: PAM: System error for admin from 34.22.229.111 Oct 5 22:29:04 krispykreme.cs.umd.edu sshd-session[2411556]: error: Protocol major versions differ: 2 vs. 1 Oct 5 22:37:18 krispykreme.cs.umd.edu sshd-session[2413771]: pam_access(sshd:auth): access denied for user `admin' from `34.62.218.88' Oct 5 22:37:19 krispykreme.cs.umd.edu sshd-session[2413769]: error: PAM: System error for admin from 34.62.218.88 == matrix (2 distinct, 3 total) == Oct 5 22:11:46 matrix krb5_child[3402717]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Oct 5 22:11:49 matrix sshd[3402710]: error: PAM: Authentication failure for admin from 35.195.35.96 == mcstic (2 distinct, 5 total) == Oct 5 22:10:56 mcstic krb5_child[1578586]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 5 22:11:02 mcstic sshd[1578580]: error: PAM: Authentication failure for admin from 35.205.193.65 == munin (2 distinct, 2 total) == Oct 5 23:03:16 munin sudo[472111]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Oct 5 23:03:16 munin sudo[472111]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Oct 5 22:13:03 newhonors2 dhcpcd[3613063]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Oct 5 22:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3802) *** Oct 5 22:05:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3802, QN: 61/61, ET: 1) *** Oct 5 22:05:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3802, QN: 4566/4566, ET: 6) *** Oct 5 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3803) *** Oct 5 22:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3803, QN: 3897/3897, ET: 0) *** Oct 5 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3803) *** Oct 5 22:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3803, QN: 56/56, ET: 0) *** Oct 5 22:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3804) *** Oct 5 22:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3804) *** Oct 5 22:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3804, QN: 50/50, ET: 1) *** Oct 5 22:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3804, QN: 3665/3665, ET: 5) *** Oct 5 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3805) *** Oct 5 22:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3805, QN: 58/58, ET: 0) *** Oct 5 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3805) *** Oct 5 22:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3805, QN: 4542/4542, ET: 0) *** Oct 5 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3806) *** Oct 5 22:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3806, QN: 53/53, ET: 0) *** Oct 5 22:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3806) *** Oct 5 22:15:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3806, QN: 4191/4191, ET: 6) *** Oct 5 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3807) *** Oct 5 22:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3807, QN: 4076/4076, ET: 0) *** Oct 5 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3807) *** Oct 5 22:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3807, QN: 55/55, ET: 0) *** Oct 5 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3808) *** Oct 5 22:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3808) *** Oct 5 22:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3808, QN: 61/61, ET: 0) *** Oct 5 22:20:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3808, QN: 4131/4131, ET: 6) *** Oct 5 22:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3809) *** Oct 5 22:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3809, QN: 57/57, ET: 0) *** Oct 5 22:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3809) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 5 22:09:09 outbound00.cs.umd.edu python3[3127593]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 5 22:13:06 outbound01.cs.umd.edu python3[1201848]: ldapdb [x6] == portal (1 distinct, 75 total) == Oct 5 22:05:06 portal setroubleshoot[1289632]: 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 [x75] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 5 22:10:30 sentry-docker00.cs.umd.edu systemd-udevd[2196990]: link_config: could not get ethtool features for veth8ef7055 Oct 5 22:10:30 sentry-docker00.cs.umd.edu systemd-udevd[2196990]: Could not set offload features of veth8ef7055: No such device Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197049]: Could not generate persistent MAC address for vethbc7e537: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197050]: Could not generate persistent MAC address for veth5102881: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197053]: Could not generate persistent MAC address for vethd65b6e6: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197054]: Could not generate persistent MAC address for vethac12c79: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197072]: Could not generate persistent MAC address for veth0c58936: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197067]: Could not generate persistent MAC address for veth700800b: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197079]: Could not generate persistent MAC address for vethb31ea22: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197080]: Could not generate persistent MAC address for vethd1e13b0: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197103]: Could not generate persistent MAC address for vethed95b9f: No such file or directory Oct 5 22:10:31 sentry-docker00.cs.umd.edu systemd-udevd[2197113]: Could not generate persistent MAC address for veth79a7dc1: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206485]: link_config: could not get ethtool features for vethbc7e537 Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206485]: Could not set offload features of vethbc7e537: No such device Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206559]: Could not generate persistent MAC address for veth7a182fb: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206560]: Could not generate persistent MAC address for vethc4abfdd: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206563]: Could not generate persistent MAC address for veth751ffb0: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206564]: Could not generate persistent MAC address for veth5122dd7: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206564]: Could not generate persistent MAC address for veth69becdf: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206571]: Could not generate persistent MAC address for vethbdac39d: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206626]: Could not generate persistent MAC address for vethe1639f2: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206622]: Could not generate persistent MAC address for vetha385a28: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206645]: Could not generate persistent MAC address for veth3f0309c: No such file or directory Oct 5 22:30:39 sentry-docker00.cs.umd.edu systemd-udevd[2206643]: Could not generate persistent MAC address for veth4548093: No such file or directory Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215786]: link_config: could not get ethtool features for vetha385a28 Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215786]: Could not set offload features of vetha385a28: No such device Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215821]: Could not generate persistent MAC address for veth8a6a921: No such file or directory Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215822]: Could not generate persistent MAC address for veth0abd1b8: No such file or directory Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215825]: Could not generate persistent MAC address for veth7c35d64: No such file or directory Oct 5 22:50:47 sentry-docker00.cs.umd.edu systemd-udevd[2215826]: Could not generate persistent MAC address for veth9b8f825: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 5 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 5 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 5 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 5 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 5 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 11 total) == Oct 5 22:20:06 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.s3jrZp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.s3jrZp. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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 Oct 5 22:26:01 submit26-b9-f1 setroubleshoot[1115852]: 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) == Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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 Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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 Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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] Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.10cU3C/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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] Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.10cU3C. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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 Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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 Oct 5 22:06:55 submit26-b9-f2 setroubleshoot[207787]: 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 Oct 5 22:08:10 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (1 distinct, 1 total) == Oct 5 22:50:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == tma-0 (1 distinct, 1 total) == Oct 5 22:12:15 tma-0 sshd[4211]: error: PAM: Authentication failure for admin from 125.243.76.34.bc.googleusercontent.com == vacuum.cs.umd.edu (4 distinct, 4 total) == Oct 5 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[4110]: Process 31934 (driver) of user 33 killed by SIGSEGV - dumping core Oct 5 22:11:59 vacuum.cs.umd.edu abrt-server[4112]: Package 'amanda-backup_server' isn't signed with proper key Oct 5 22:11:59 vacuum.cs.umd.edu abrt-server[4112]: 'post-create' on '/var/spool/abrt/ccpp-2026-10-05-22:11:58-31934' exited with 1 Oct 5 22:11:59 vacuum.cs.umd.edu abrt-server[4112]: Deleting problem directory '/var/spool/abrt/ccpp-2026-10-05-22:11:58-31934' == wraith (2 distinct, 2 total) == Oct 5 22:18:24 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND Oct 5 22:19:47 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND