Command: /usr/local/sbin/syslog-digest.py Time : 0.0520s Status : exited 0 Output : Syslog digest — 2026-09-20 19:05 EDT Processed 2,310 lines, filtered 1,772 (76%). 538 unknown (184 distinct) from 16 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 20 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-20T22:10:59.427675008Z" level=info msg="PurgeUploads starting: olderThan=2026-09-13 22:10:59.427564468 +0000 UTC m=+4149420.187492783, actuallyDelete=true" Sep 20 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-20T22:10:59.428165689Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 20 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-20T22:10:59.428185841Z" level=info msg="Starting upload purge in 24h0m0s" go.version=go1.11.2 instance.id=68469aa4-7857-4a69-bf12-c2190b4f96d8 service=registry version=v2.7.1 Sep 20 18:52:44 b0b02.cs.umd.edu rustdesk[3351603]: cannot open display: == bale (5 distinct, 85 total) == Sep 20 18:05:20 bale setroubleshoot[1242410]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 20 18:05:21 bale setroubleshoot[1242410]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x13] Sep 20 18:05:23 bale setroubleshoot[1242410]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 20 18:05:26 bale setroubleshoot[1242410]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11] Sep 20 18:05:38 bale setroubleshoot[1243039]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12] == csfw00a (1 distinct, 146 total) == Sep 20 18:04:27 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x146] == idm00 (1 distinct, 1 total) == Sep 20 18:54:00 idm00 named[4166701]: client @0x7f11980511b8 10.73.240.42#60542: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 18:37:56 idmp0 named[1598691]: client @0x7f2d44005288 10.73.240.43#59178: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 20 18:18:25 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == newhonors2 (1 distinct, 24 total) == Sep 20 18:13:03 newhonors2 dhcpcd[2915509]: dhcpcd is not running [x24] == ntop00 (102 distinct, 146 total) == Sep 20 18:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) *** Sep 20 18:05:50 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 11876/11876, ET: 49) *** Sep 20 18:05:50 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 78/78, ET: 49) *** Sep 20 18:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 20 18:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 8087/8087, ET: 0) *** Sep 20 18:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 20 18:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 77/77, ET: 0) *** Sep 20 18:08:02 ntop00 setroubleshoot[873619]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12] Sep 20 18:08:02 ntop00 setroubleshoot[873619]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12] Sep 20 18:08:02 ntop00 setroubleshoot[873619]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 20 18:08:02 ntop00 setroubleshoot[873619]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12] Sep 20 18:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 20 18:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 20 18:10:31 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 7476/7476, ET: 30) *** Sep 20 18:10:31 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 48/48, ET: 30) *** Sep 20 18:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 20 18:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 7460/7460, ET: 0) *** Sep 20 18:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 20 18:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 49/49, ET: 0) *** Sep 20 18:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 20 18:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 20 18:15:31 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 7328/7328, ET: 30) *** Sep 20 18:15:31 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 48/48, ET: 30) *** Sep 20 18:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 20 18:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 7297/7297, ET: 0) *** Sep 20 18:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 20 18:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 42/42, ET: 0) *** Sep 20 18:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 20 18:20:02 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 20 18:20:32 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 7539/7539, ET: 31) *** ... 72 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 18:09:09 outbound00.cs.umd.edu python3[2117351]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 18:13:06 outbound01.cs.umd.edu python3[183482]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286552]: link_config: could not get ethtool features for veth1c6a207 Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286552]: Could not set offload features of veth1c6a207: No such device Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286587]: Could not generate persistent MAC address for veth342a5c1: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286588]: Could not generate persistent MAC address for vethe745d74: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286591]: Could not generate persistent MAC address for veth51152bd: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286592]: Could not generate persistent MAC address for veth9bfee7b: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286606]: Could not generate persistent MAC address for veth6675d1f: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286597]: Could not generate persistent MAC address for veth48a581f: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286617]: Could not generate persistent MAC address for veth3995cf4: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286618]: Could not generate persistent MAC address for veth5e952c9: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286629]: Could not generate persistent MAC address for vethe2ddda0: No such file or directory Sep 20 18:19:47 sentry-docker00.cs.umd.edu systemd-udevd[286624]: Could not generate persistent MAC address for vethce36039: No such file or directory Sep 20 18:39:55 sentry-docker00.cs.umd.edu systemd-udevd[295827]: link_config: could not get ethtool features for vethce36039 Sep 20 18:39:55 sentry-docker00.cs.umd.edu systemd-udevd[295827]: Could not set offload features of vethce36039: No such device Sep 20 18:39:55 sentry-docker00.cs.umd.edu systemd-udevd[295949]: Could not generate persistent MAC address for vethb0e052a: No such file or directory Sep 20 18:39:55 sentry-docker00.cs.umd.edu systemd-udevd[295950]: Could not generate persistent MAC address for veth76dcd1e: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296002]: Could not generate persistent MAC address for veth59cdc1f: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296003]: Could not generate persistent MAC address for veth07088bc: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296006]: Could not generate persistent MAC address for vethe07e097: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296007]: Could not generate persistent MAC address for vethdd4630e: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296037]: Could not generate persistent MAC address for vethc9767d5: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296038]: Could not generate persistent MAC address for veth6287d70: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296069]: Could not generate persistent MAC address for veth2dec529: No such file or directory Sep 20 18:39:56 sentry-docker00.cs.umd.edu systemd-udevd[296070]: Could not generate persistent MAC address for vetha3991a4: No such file or directory Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305380]: link_config: could not get ethtool features for veth2dec529 Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305380]: Could not set offload features of veth2dec529: No such device Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305406]: Could not generate persistent MAC address for veth7452aee: No such file or directory Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305407]: Could not generate persistent MAC address for vetha2d2750: No such file or directory Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305410]: Could not generate persistent MAC address for veth08f1674: No such file or directory Sep 20 19:00:04 sentry-docker00.cs.umd.edu systemd-udevd[305411]: Could not generate persistent MAC address for veth2d0e75a: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 18:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 18:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (11 distinct, 15 total) == Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 [x2] Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3QNRtl/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 [x2] Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3QNRtl. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 [x2] Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: 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 Sep 20 18:25:54 submit26-b9-f1 setroubleshoot[2616298]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ja69O0/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 20 18:41:44 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (10 distinct, 16 total) == Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 [x2] Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 [x2] Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.FFqwug/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.FFqwug. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 Sep 20 18:06:49 submit26-b9-f2 setroubleshoot[1730335]: 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 Sep 20 18:18:38 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (1 distinct, 7 total) == Sep 20 18:07:58 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f4 (1 distinct, 3 total) == Sep 20 18:23:07 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3]