Command: /usr/local/sbin/syslog-digest.py Time : 0.0413s Status : exited 0 Output : Syslog digest — 2026-09-25 02:05 EDT Processed 1,484 lines, filtered 1,243 (83%). 241 unknown (168 distinct) from 14 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 25 01:59:26 b0b02.cs.umd.edu rustdesk[802813]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 25 01:54:07 idm00 named[4166701]: client @0x7f11a93ed928 10.73.240.42#58086: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 25 01:39:51 idmp0 named[1598691]: client @0x7f2d2401e448 10.73.240.43#55525: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 7 total) == Sep 25 01:07:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x7] == newhonors2 (1 distinct, 24 total) == Sep 25 01:13:03 newhonors2 dhcpcd[3117799]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 25 01:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 25 01:05:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 52/52, ET: 0) *** Sep 25 01:05:09 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 5169/5169, ET: 8) *** Sep 25 01:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 25 01:08:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 4432/4432, ET: 0) *** Sep 25 01:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 25 01:08:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 59/59, ET: 0) *** Sep 25 01:10:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 25 01:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 25 01:10:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 55/55, ET: 0) *** Sep 25 01:10:08 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 4107/4107, ET: 7) *** Sep 25 01:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 25 01:13:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 3747/3747, ET: 0) *** Sep 25 01:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 25 01:13:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 61/61, ET: 0) *** Sep 25 01:15:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 25 01:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 25 01:15:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 51/51, ET: 0) *** Sep 25 01:15:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 3730/3730, ET: 5) *** Sep 25 01:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 25 01:18:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 3394/3394, ET: 0) *** Sep 25 01:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 25 01:18:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 41/41, ET: 0) *** Sep 25 01:20:01 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 25 01:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 25 01:20:01 ntop00 nfacctd[182312]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 47/47, ET: 0) *** Sep 25 01:20:06 ntop00 sfacctd[182241]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 3732/3732, ET: 5) *** Sep 25 01:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 25 01:23:01 ntop00 sfacctd[182241]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 4455/4455, ET: 0) *** Sep 25 01:23:01 ntop00 nfacctd[182312]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 25 01:09:09 outbound00.cs.umd.edu python3[3604862]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 25 01:13:06 outbound01.cs.umd.edu python3[1670726]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 25 01:22:25 sentry-docker00.cs.umd.edu systemd-udevd[3218410]: link_config: could not get ethtool features for veth9e42f28 Sep 25 01:22:25 sentry-docker00.cs.umd.edu systemd-udevd[3218410]: Could not set offload features of veth9e42f28: No such device Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218494]: Could not generate persistent MAC address for veth2ffe616: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218493]: Could not generate persistent MAC address for vethdb34f84: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218497]: Could not generate persistent MAC address for vethaf57375: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218498]: Could not generate persistent MAC address for vethb8e05be: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218521]: Could not generate persistent MAC address for veth1f9cc8b: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218522]: Could not generate persistent MAC address for veth9a9f0ec: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218548]: Could not generate persistent MAC address for veth7390f70: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218549]: Could not generate persistent MAC address for veth31bd4fd: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218567]: Could not generate persistent MAC address for veth1308c16: No such file or directory Sep 25 01:22:26 sentry-docker00.cs.umd.edu systemd-udevd[3218573]: Could not generate persistent MAC address for vethc7233f1: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227902]: link_config: could not get ethtool features for veth1f9cc8b Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227902]: Could not set offload features of veth1f9cc8b: No such device Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227973]: Could not generate persistent MAC address for vethdb0017e: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227974]: Could not generate persistent MAC address for vethee2822e: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227977]: Could not generate persistent MAC address for veth4db53f0: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227978]: Could not generate persistent MAC address for veth3048d6b: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227989]: Could not generate persistent MAC address for veth21a82a9: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227977]: Could not generate persistent MAC address for vetha8c3b83: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227979]: Could not generate persistent MAC address for vethc8c2c80: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3227977]: Could not generate persistent MAC address for vetha95b24f: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3228052]: Could not generate persistent MAC address for vethfba648b: No such file or directory Sep 25 01:42:34 sentry-docker00.cs.umd.edu systemd-udevd[3228054]: Could not generate persistent MAC address for vetha72f6e8: No such file or directory Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237367]: link_config: could not get ethtool features for veth4db53f0 Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237367]: Could not set offload features of veth4db53f0: No such device Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237401]: Could not generate persistent MAC address for veth2c6cf72: No such file or directory Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237402]: Could not generate persistent MAC address for veth1edc464: No such file or directory Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237405]: Could not generate persistent MAC address for veth7ba23ce: No such file or directory Sep 25 02:02:42 sentry-docker00.cs.umd.edu systemd-udevd[3237406]: Could not generate persistent MAC address for vethc0ea967: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 25 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 25 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 25 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 25 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 25 01:18:09 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Sep 25 01:45:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 10 total) == Sep 25 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 25 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.o3U688/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 25 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 25 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.o3U688. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 25 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 01:06:45 submit26-b9-f3 setroubleshoot[3326317]: 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 01:25:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (10 distinct, 13 total) == Sep 25 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EzA0Bb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 25 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EzA0Bb. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 25 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 [x2] Sep 25 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: 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 Sep 25 01:24:49 submit26-b9-f4 setroubleshoot[2429469]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4ORh5j/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0