Command: /usr/local/sbin/syslog-digest.py Time : 0.0470s Status : exited 0 Output : Syslog digest — 2026-09-24 02:05 EDT Processed 2,633 lines, filtered 2,336 (88%). 297 unknown (185 distinct) from 20 host(s). == alec.cs.umd.edu (1 distinct, 1 total) == Sep 24 01:57:51 alec.cs.umd.edu mariadb-drupal[3120]: 2026-09-24 5:57:51 18338 [Warning] Aborted connection 18338 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets) == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 24 01:57:49 b0b02.cs.umd.edu rustdesk[434483]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Sep 24 01:38:36 cheezit.cs.umd.edu sshd-session[2522212]: error: send_error: write: Connection reset by peer == galax (1 distinct, 1 total) == Sep 24 01:53:17 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND == gle-dind04 (2 distinct, 2 total) == Sep 24 01:32:25 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 24 01:32:25 gle-dind04 falcon-sensor-bpf[1017]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == idm00 (1 distinct, 1 total) == Sep 24 01:54:06 idm00 named[4166701]: client @0x7f119806f9c8 10.73.240.42#49394: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 24 01:39:31 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#51759: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Sep 24 01:56:44 inbound00.cs.umd.edu krb5_child[3416924]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 3 total) == Sep 24 01:08:17 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (4 distinct, 5 total) == Sep 24 01:20:47 krispykreme.cs.umd.edu sshd-session[1850526]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 24 01:20:48 krispykreme.cs.umd.edu sshd-session[1850526]: Error in Duo login for 'larry' from 71.191.93.172 Sep 24 01:20:48 krispykreme.cs.umd.edu sshd-session[1850339]: error: PAM: Authentication failure for larry from 71.191.93.172 Sep 24 01:38:35 krispykreme.cs.umd.edu sshd-session[1855763]: error: send_error: write: Connection reset by peer == munin (2 distinct, 44 total) == Sep 24 01:08:32 munin sudo[2638787]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x22] Sep 24 01:08:32 munin sudo[2638787]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x22] == netman.cs.umd.edu (3 distinct, 6 total) == Sep 24 01:13:14 netman.cs.umd.edu krb5_child[7660]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 24 01:13:18 netman.cs.umd.edu sshd[7657]: error: PAM: Authentication failure for admin from 34.38.77.240 Sep 24 01:15:16 netman.cs.umd.edu sshd[8196]: error: Protocol major versions differ: 2 vs. 1 == newhonors2 (1 distinct, 24 total) == Sep 24 01:13:02 newhonors2 dhcpcd[3065676]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 24 01:05:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 52) *** Sep 24 01:05:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 52) *** Sep 24 01:05:04 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 52, QN: 41/41, ET: 3) *** Sep 24 01:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 53) *** Sep 24 01:06:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 53, QN: 4851/4851, ET: 0) *** Sep 24 01:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 53) *** Sep 24 01:06:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 53, QN: 47/47, ET: 0) *** Sep 24 01:07:03 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 52, QN: 5551/5551, ET: 122) *** Sep 24 01:10:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) *** Sep 24 01:10:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 54) *** Sep 24 01:10:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 59/59, ET: 1) *** Sep 24 01:10:40 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 54, QN: 4372/4372, ET: 39) *** Sep 24 01:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 55) *** Sep 24 01:11:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 5056/5056, ET: 0) *** Sep 24 01:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 55) *** Sep 24 01:11:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 55, QN: 53/53, ET: 0) *** Sep 24 01:15:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 56) *** Sep 24 01:15:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 56) *** Sep 24 01:15:02 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 56, QN: 41/41, ET: 1) *** Sep 24 01:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 57) *** Sep 24 01:16:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 57, QN: 6399/6399, ET: 0) *** Sep 24 01:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 57) *** Sep 24 01:16:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - END (PID: 57, QN: 49/49, ET: 0) *** Sep 24 01:16:07 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - END (PID: 56, QN: 6378/6378, ET: 66) *** Sep 24 01:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - START (PID: 58) *** Sep 24 01:20:01 ntop00 sfacctd[108049]: INFO ( m1/mysql ): *** Purging cache - START (PID: 58) *** Sep 24 01:20:01 ntop00 nfacctd[108120]: INFO ( m1/mysql ): *** Purging cache - END (PID: 58, QN: 63/63, ET: 0) *** Sep 24 01:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - START (PID: 59) *** Sep 24 01:21:01 ntop00 sfacctd[108049]: INFO ( p1/print ): *** Purging cache - END (PID: 59, QN: 5501/5501, ET: 0) *** Sep 24 01:21:01 ntop00 nfacctd[108120]: INFO ( p1/print ): *** Purging cache - START (PID: 59) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 24 01:09:09 outbound00.cs.umd.edu python3[3265216]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 24 01:13:07 outbound01.cs.umd.edu python3[1331182]: ldapdb [x6] Sep 24 02:04:25 outbound01.cs.umd.edu krb5_child[1343497]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 24 01:12:22 sentry-docker00.cs.umd.edu systemd-udevd[2534572]: link_config: could not set ethtool features for vethbb1f5db Sep 24 01:12:22 sentry-docker00.cs.umd.edu systemd-udevd[2534572]: Could not set offload features of vethbb1f5db: Operation not permitted Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534609]: Could not generate persistent MAC address for vethe96f173: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534610]: Could not generate persistent MAC address for vethfca6af9: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534613]: Could not generate persistent MAC address for veth3d42057: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534614]: Could not generate persistent MAC address for veth921d466: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534627]: Could not generate persistent MAC address for veth7a24734: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534634]: Could not generate persistent MAC address for veth248086a: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534625]: Could not generate persistent MAC address for veth610db5c: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534623]: Could not generate persistent MAC address for veth1274925: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534619]: Could not generate persistent MAC address for vethf1123a3: No such file or directory Sep 24 01:12:23 sentry-docker00.cs.umd.edu systemd-udevd[2534635]: Could not generate persistent MAC address for veth9ab4a12: No such file or directory Sep 24 01:32:30 sentry-docker00.cs.umd.edu systemd-udevd[2544175]: link_config: could not get ethtool features for vethe96f173 Sep 24 01:32:30 sentry-docker00.cs.umd.edu systemd-udevd[2544175]: Could not set offload features of vethe96f173: No such device Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544179]: link_config: could not get ethtool features for vethf1123a3 Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544179]: Could not set offload features of vethf1123a3: No such device Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544209]: Could not generate persistent MAC address for veth4830e5a: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544210]: Could not generate persistent MAC address for veth747043d: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544228]: Could not generate persistent MAC address for veth74ce034: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544215]: Could not generate persistent MAC address for vethb276d3e: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544215]: Could not generate persistent MAC address for veth6da9592: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544213]: Could not generate persistent MAC address for vethefc04ee: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544225]: Could not generate persistent MAC address for vethf9c55a9: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544213]: Could not generate persistent MAC address for veth4d3eeca: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544267]: Could not generate persistent MAC address for vetha9144c7: No such file or directory Sep 24 01:32:31 sentry-docker00.cs.umd.edu systemd-udevd[2544270]: Could not generate persistent MAC address for veth28e9970: No such file or directory Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553480]: link_config: could not get ethtool features for veth74ce034 Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553480]: Could not set offload features of veth74ce034: No such device Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553577]: link_config: could not get ethtool features for vetha9144c7 Sep 24 01:52:39 sentry-docker00.cs.umd.edu systemd-udevd[2553577]: Could not set offload features of vetha9144c7: No such device ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 24 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 01:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 01:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 01:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 24 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LBRYMq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 24 01:06:44 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Sep 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LBRYMq. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Sep 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Sep 24 01:06:45 submit26-b9-f3 setroubleshoot[2917160]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 == submit26-b9-f4 (9 distinct, 9 total) == Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.x88Cq1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x88Cq1. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Sep 24 01:24:48 submit26-b9-f4 setroubleshoot[2143790]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915