Command: /usr/local/sbin/syslog-digest.py Time : 0.0418s Status : exited 0 Output : Syslog digest — 2026-09-24 21:05 EDT Processed 1,666 lines, filtered 1,382 (82%). 284 unknown (165 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 24 20:59:05 b0b02.cs.umd.edu rustdesk[725476]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 2 total) == Sep 24 20:11:05 biggulp.cs.umd.edu sshd-session[3994492]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.227.191' [x2] == galax (1 distinct, 1 total) == Sep 24 20:21:38 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 8195 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Sep 24 20:54:06 idm00 named[4166701]: client @0x7f11a93cbc38 10.73.240.42#63905: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 24 20:39:50 idmp0 named[1598691]: client @0x7f2d34017478 10.73.240.43#65323: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 8 total) == Sep 24 20:06:04 inbound00.cs.umd.edu krb5_child[3677952]: Preauthentication failed [x5] Sep 24 20:09:30 inbound00.cs.umd.edu krb5_child[3678578]: Client 'admin@UMD.EDU' not found in Kerberos database [x3] == itmon02 (1 distinct, 5 total) == Sep 24 20:18:43 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == mcstic (1 distinct, 1 total) == Sep 24 20:52:02 mcstic sshd[1074800]: error: maximum authentication attempts exceeded for root from 82.65.35.105 port 57074 ssh2 [preauth] == munin (2 distinct, 40 total) == Sep 24 20:13:15 munin sudo[3053834]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x20] Sep 24 20:13:15 munin sudo[3053834]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x20] == newhonors2 (1 distinct, 24 total) == Sep 24 20:13:03 newhonors2 dhcpcd[3108237]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 24 20:05:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) *** Sep 24 20:05:02 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 61/61, ET: 0) *** Sep 24 20:05:12 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 6741/6741, ET: 11) *** Sep 24 20:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 24 20:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 59/59, ET: 0) *** Sep 24 20:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 24 20:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 6669/6669, ET: 0) *** Sep 24 20:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 24 20:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 24 20:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 47/47, ET: 0) *** Sep 24 20:10:13 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 7642/7642, ET: 12) *** Sep 24 20:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 24 20:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 8137/8137, ET: 0) *** Sep 24 20:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 24 20:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 35/35, ET: 0) *** Sep 24 20:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 24 20:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 24 20:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 32/32, ET: 0) *** Sep 24 20:15:12 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 8487/8487, ET: 11) *** Sep 24 20:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 24 20:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 9742/9742, ET: 0) *** Sep 24 20:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 24 20:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 43/43, ET: 0) *** Sep 24 20:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** Sep 24 20:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** Sep 24 20:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 56/56, ET: 0) *** Sep 24 20:20:13 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 8959/8959, ET: 12) *** Sep 24 20:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 305) *** Sep 24 20:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 305, QN: 7646/7646, ET: 0) *** Sep 24 20:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 305) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 24 20:09:09 outbound00.cs.umd.edu python3[3533165]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 24 20:13:07 outbound01.cs.umd.edu python3[1599805]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 24 20:20:20 sentry-docker00.cs.umd.edu systemd-udevd[3076494]: link_config: could not get ethtool features for vethd96d368 Sep 24 20:20:20 sentry-docker00.cs.umd.edu systemd-udevd[3076494]: Could not set offload features of vethd96d368: No such device Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076582]: Could not generate persistent MAC address for vethe4b2cb7: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076583]: Could not generate persistent MAC address for veth2e3c58a: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076601]: Could not generate persistent MAC address for veth2e0fe65: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076590]: Could not generate persistent MAC address for veth16678a2: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076589]: Could not generate persistent MAC address for veth1b910e5: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076588]: Could not generate persistent MAC address for veth23a8af3: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076588]: Could not generate persistent MAC address for vethd57f9f3: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076597]: Could not generate persistent MAC address for veth1d30878: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076597]: Could not generate persistent MAC address for vethce2090e: No such file or directory Sep 24 20:20:21 sentry-docker00.cs.umd.edu systemd-udevd[3076588]: Could not generate persistent MAC address for vethac92985: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085861]: link_config: could not get ethtool features for vethe4b2cb7 Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085861]: Could not set offload features of vethe4b2cb7: No such device Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085987]: Could not generate persistent MAC address for vethb6a2fc7: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085988]: Could not generate persistent MAC address for veth898d935: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3086009]: Could not generate persistent MAC address for veth1e55bb5: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085987]: Could not generate persistent MAC address for vethd59ebe3: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085992]: Could not generate persistent MAC address for vethcdabbf5: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3086006]: Could not generate persistent MAC address for veth140b2b9: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3085987]: Could not generate persistent MAC address for veth702efd0: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3086009]: Could not generate persistent MAC address for veth8620f63: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3086047]: Could not generate persistent MAC address for vethebcdb4f: No such file or directory Sep 24 20:40:29 sentry-docker00.cs.umd.edu systemd-udevd[3086048]: Could not generate persistent MAC address for vethab86ba2: No such file or directory Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095360]: link_config: could not get ethtool features for vethb6a2fc7 Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095360]: Could not set offload features of vethb6a2fc7: No such device Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095394]: Could not generate persistent MAC address for veth52ced2f: No such file or directory Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095395]: Could not generate persistent MAC address for vethd6cda39: No such file or directory Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095398]: Could not generate persistent MAC address for veth5e7660b: No such file or directory Sep 24 21:00:37 sentry-docker00.cs.umd.edu systemd-udevd[3095417]: Could not generate persistent MAC address for veth7a2e66d: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 24 20: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 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 24 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 24 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 24 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 24 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f2 (1 distinct, 4 total) == Sep 24 20:13:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (1 distinct, 2 total) == Sep 24 20:19:40 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (1 distinct, 3 total) == Sep 24 20:18:15 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-fclone (9 distinct, 9 total) == Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.d920nu/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.d920nu. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c Sep 24 20:21:59 submit26-b9-fclone setroubleshoot[431363]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4