Command: /usr/local/sbin/syslog-digest.py Time : 0.0526s Status : exited 0 Output : Syslog digest — 2026-09-19 19:05 EDT Processed 2,553 lines, filtered 2,043 (80%). 510 unknown (184 distinct) from 19 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.426919828Z" level=info msg="PurgeUploads starting: olderThan=2026-09-12 22:10:59.426842535 +0000 UTC m=+4063020.186770847, actuallyDelete=true" Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427410979Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 19 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-19T22:10:59.427430854Z" 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 19 18:51:16 b0b02.cs.umd.edu rustdesk[2984122]: cannot open display: == bale (5 distinct, 87 total) == Sep 19 18:06:04 bale setroubleshoot[934499]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 19 18:06:05 bale setroubleshoot[934499]: 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 [x12] Sep 19 18:06:07 bale setroubleshoot[934499]: 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 19 18:06:10 bale setroubleshoot[934499]: 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 19 18:06:22 bale setroubleshoot[935113]: 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 [x14] == csfw00a (1 distinct, 128 total) == Sep 19 18:04:09 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x128] == idm00 (1 distinct, 1 total) == Sep 19 18:53:59 idm00 named[4166701]: client @0x7f11980184a8 10.73.240.42#64044: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 18:37:56 idmp0 named[1598691]: client @0x7f2d3c076558 10.73.240.43#63053: update '73.10.in-addr.arpa/IN' denied == irb2156 (1 distinct, 1 total) == Sep 19 18:08:41 irb2156 systemd-tmpfiles[572914]: Opening file "/tmp/org.chromium.Chromium.pnSOAt/SingletonSocket" failed, proceeding without lock: No such device or address == itmon02 (1 distinct, 2 total) == Sep 19 18:18:25 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 4 total) == Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 19 18:28:59 munin sudo[405059]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == neoavion (1 distinct, 1 total) == Sep 19 18:32:35 neoavion krb5_child[3630822]: No credentials cache found == newhonors2 (1 distinct, 24 total) == Sep 19 18:13:03 newhonors2 dhcpcd[2870113]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 19 18:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 250) *** Sep 19 18:05:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 7481/7481, ET: 28) *** Sep 19 18:05:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 250, QN: 45/45, ET: 28) *** Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 19 18:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 9416/9416, ET: 0) *** Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 251) *** Sep 19 18:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 251, QN: 58/58, ET: 0) *** Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12] Sep 19 18:08:02 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12] Sep 19 18:08:03 ntop00 setroubleshoot[682597]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 18:08:03 ntop00 setroubleshoot[682597]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12] Sep 19 18:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 19 18:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 252) *** Sep 19 18:10:29 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 8306/8306, ET: 28) *** Sep 19 18:10:29 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 252, QN: 71/71, ET: 28) *** Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 19 18:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 14544/14544, ET: 0) *** Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 253) *** Sep 19 18:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 253, QN: 82/82, ET: 0) *** Sep 19 18:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 19 18:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 254) *** Sep 19 18:16:07 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 19635/19635, ET: 66) *** Sep 19 18:16:08 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 254, QN: 78/78, ET: 67) *** Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 19 18:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 24509/24509, ET: 0) *** Sep 19 18:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 255) *** Sep 19 18:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 255, QN: 68/68, ET: 1) *** Sep 19 18:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 19 18:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 256) *** Sep 19 18:21:33 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 256, QN: 26844/26844, ET: 92) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 18:09:09 outbound00.cs.umd.edu python3[1778552]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 18:13:06 outbound01.cs.umd.edu python3[4037632]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: link_config: could not get ethtool features for veth69ad032 Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796075]: Could not set offload features of veth69ad032: No such device Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796106]: Could not generate persistent MAC address for veth99cdb86: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796107]: Could not generate persistent MAC address for veth97ebd42: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796110]: Could not generate persistent MAC address for vethe7f36d9: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth1c82051: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796111]: Could not generate persistent MAC address for veth20702d5: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796121]: Could not generate persistent MAC address for veth63f8e31: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796122]: Could not generate persistent MAC address for vethcb15d1a: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796129]: Could not generate persistent MAC address for vetha53d8f6: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796152]: Could not generate persistent MAC address for veth5fd93ec: No such file or directory Sep 19 18:09:48 sentry-docker00.cs.umd.edu systemd-udevd[3796151]: Could not generate persistent MAC address for veth4c6561c: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: link_config: could not get ethtool features for vethe7f36d9 Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805464]: Could not set offload features of vethe7f36d9: No such device Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805537]: Could not generate persistent MAC address for vethc5f68d5: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805538]: Could not generate persistent MAC address for vethd3bc0eb: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805541]: Could not generate persistent MAC address for veth875e42f: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805542]: Could not generate persistent MAC address for veth3acfc7d: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805565]: Could not generate persistent MAC address for vethf2f220c: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805566]: Could not generate persistent MAC address for vethae3f43a: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805611]: Could not generate persistent MAC address for veth2be16b5: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805622]: Could not generate persistent MAC address for vetha339108: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805639]: Could not generate persistent MAC address for veth4674d73: No such file or directory Sep 19 18:29:56 sentry-docker00.cs.umd.edu systemd-udevd[3805662]: Could not generate persistent MAC address for vethb8400f8: No such file or directory Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: link_config: could not get ethtool features for veth875e42f Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814913]: Could not set offload features of veth875e42f: No such device Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814982]: Could not generate persistent MAC address for vethfbbb2b4: No such file or directory Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814983]: Could not generate persistent MAC address for veth96a93c2: No such file or directory Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814986]: Could not generate persistent MAC address for vethb85b833: No such file or directory Sep 19 18:50:05 sentry-docker00.cs.umd.edu systemd-udevd[3814995]: Could not generate persistent MAC address for veth21c3f98: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 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 19 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 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 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 19 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 19 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 12 total) == Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: 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 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: 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 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: 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 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.R33FVJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d [x2] Sep 19 18:25:53 submit26-b9-f1 setroubleshoot[2528254]: 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 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.R33FVJ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: 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 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: 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 Sep 19 18:25:54 submit26-b9-f1 setroubleshoot[2528254]: 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 == submit26-b9-f2 (10 distinct, 13 total) == Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: 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 Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: 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 Sep 19 18:06:48 submit26-b9-f2 setroubleshoot[1640177]: 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 [x2] Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Cd0ZAk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: 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 [x2] Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Cd0ZAk. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: 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 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: 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 [x2] Sep 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: 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 19 18:06:49 submit26-b9-f2 setroubleshoot[1640177]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.F0sZXe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 == submit26-b9-f3 (1 distinct, 1 total) == Sep 19 18:08:07 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (1 distinct, 1 total) == Sep 19 18:23:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL