Command: /usr/local/sbin/syslog-digest.py Time : 0.0424s Status : exited 0 Output : Syslog digest — 2026-09-25 22:05 EDT Processed 1,686 lines, filtered 1,409 (83%). 277 unknown (174 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 25 22:00:38 b0b02.cs.umd.edu rustdesk[1109223]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Sep 25 21:27:16 biggulp.cs.umd.edu sshd-session[64386]: error: send_error: write: Connection reset by peer == galax (2 distinct, 2 total) == Sep 25 21:08:45 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 259 times, consider switching to WQ_UNBOUND Sep 25 21:54:55 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 515 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Sep 25 21:54:07 idm00 named[4166701]: client @0x7f11980104c8 10.73.240.42#55055: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 21:39:29 idmp0 named[1598691]: client @0x7f2d4c01bf08 10.73.240.43#61505: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 25 21:58:49 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == munin (2 distinct, 14 total) == Sep 25 21:08:28 munin sudo[3596321]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7] Sep 25 21:08:28 munin sudo[3596321]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7] == newhonors2 (1 distinct, 24 total) == Sep 25 21:13:03 newhonors2 dhcpcd[3155452]: dhcpcd is not running [x24] == ntop00 (97 distinct, 97 total) == Sep 25 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 25 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 58/58, ET: 0) *** Sep 25 21:05:16 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 10783/10783, ET: 15) *** Sep 25 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 25 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6829/6829, ET: 0) *** Sep 25 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 25 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 54/54, ET: 0) *** Sep 25 21:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 25 21:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 25 21:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 42/42, ET: 0) *** Sep 25 21:10:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 4318/4318, ET: 7) *** Sep 25 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 25 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 4779/4779, ET: 0) *** Sep 25 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 25 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 47/47, ET: 0) *** Sep 25 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 25 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 61/61, ET: 0) *** Sep 25 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 25 21:15:08 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 4926/4926, ET: 7) *** Sep 25 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 25 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 5294/5294, ET: 0) *** Sep 25 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 25 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 59/59, ET: 0) *** Sep 25 21:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 25 21:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 25 21:20:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 61/61, ET: 1) *** Sep 25 21:20:07 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 4805/4805, ET: 6) *** Sep 25 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 329) *** Sep 25 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 329, QN: 3997/3997, ET: 0) *** Sep 25 21:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 329) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 21:09:09 outbound00.cs.umd.edu python3[3886689]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 25 21:13:06 outbound01.cs.umd.edu python3[1952861]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778388]: link_config: could not get ethtool features for vethaff3c50 Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778388]: Could not set offload features of vethaff3c50: No such device Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778554]: Could not generate persistent MAC address for vethfc33202: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778555]: Could not generate persistent MAC address for veth6100919: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778580]: Could not generate persistent MAC address for vethe9b11d7: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778581]: Could not generate persistent MAC address for veth45db6f0: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778584]: Could not generate persistent MAC address for veth271b1b2: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778585]: Could not generate persistent MAC address for veth5c63b37: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778614]: Could not generate persistent MAC address for vethb63cba4: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778613]: Could not generate persistent MAC address for vethd28dca3: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778617]: Could not generate persistent MAC address for veth8e55669: No such file or directory Sep 25 21:10:36 sentry-docker00.cs.umd.edu systemd-udevd[3778614]: Could not generate persistent MAC address for vethe6eab97: No such file or directory Sep 25 21:30:44 sentry-docker00.cs.umd.edu systemd-udevd[3788408]: link_config: could not get ethtool features for vethe9b11d7 Sep 25 21:30:44 sentry-docker00.cs.umd.edu systemd-udevd[3788408]: Could not set offload features of vethe9b11d7: No such device Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788437]: Could not generate persistent MAC address for vethc276090: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788438]: Could not generate persistent MAC address for veth17731a4: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788441]: Could not generate persistent MAC address for vethcf03cee: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788442]: Could not generate persistent MAC address for veth4e5003d: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for vethad9f0b0: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for veth1481b88: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for veth524f058: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for veth1c243c5: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788447]: Could not generate persistent MAC address for vethf67fc5a: No such file or directory Sep 25 21:30:45 sentry-docker00.cs.umd.edu systemd-udevd[3788460]: Could not generate persistent MAC address for vethceed3c4: No such file or directory Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797757]: link_config: could not get ethtool features for vethc276090 Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797757]: Could not set offload features of vethc276090: No such device Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797793]: Could not generate persistent MAC address for veth94cfe54: No such file or directory Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797794]: Could not generate persistent MAC address for veth3f4dbd3: No such file or directory Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797797]: Could not generate persistent MAC address for veth8c5fe41: No such file or directory Sep 25 21:50:53 sentry-docker00.cs.umd.edu systemd-udevd[3797798]: Could not generate persistent MAC address for veth4604142: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 25 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 25 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 25 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 8 total) == Sep 25 21:19:50 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f2 (1 distinct, 5 total) == Sep 25 21:10:16 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (10 distinct, 20 total) == Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 [x2] Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.f0iQKA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 [x2] Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.f0iQKA. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 25 21:06:45 submit26-b9-f3 setroubleshoot[3462154]: 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 Sep 25 21:13:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f4 (10 distinct, 16 total) == Sep 25 21:08:13 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 25 21:24:48 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 [x2] Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.5CWXGp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 [x2] Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.5CWXGp. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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 25 21:24:49 submit26-b9-f4 setroubleshoot[2528623]: 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