Command: /usr/local/sbin/syslog-digest.py Time : 0.0552s Status : exited 0 Output : Syslog digest — 2026-09-18 15:05 EDT Processed 2,858 lines, filtered 2,334 (81%). 524 unknown (188 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 18 14:49:40 b0b02.cs.umd.edu rustdesk[2555525]: cannot open display: == bale (5 distinct, 86 total) == Sep 18 14:05:35 bale setroubleshoot[575608]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 18 14:05:36 bale setroubleshoot[575608]: 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 18 14:05:38 bale setroubleshoot[575608]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x14] Sep 18 14:05:41 bale setroubleshoot[575608]: 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 [x10] Sep 18 14:05:53 bale setroubleshoot[576224]: 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] == borealis (3 distinct, 3 total) == Sep 18 15:05:00 borealis gsd-subman[945996]: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Sep 18 15:05:00 borealis gsd-color[531248]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2412M_7WFG152E149L_cmevans_119720851 Sep 18 15:05:00 borealis gsd-color[531248]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2412M_4V35D7133HNU_cmevans_119720851 == csfw00a (1 distinct, 140 total) == Sep 18 14:03:42 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x140] == idm00 (1 distinct, 1 total) == Sep 18 14:54:09 idm00 named[4166701]: client @0x7f11a0059348 10.73.240.42#65533: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 18 14:37:57 idmp0 named[1598691]: client @0x7f2d34043a38 10.73.240.43#63885: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 2 total) == Sep 18 14:21:56 inbound00.cs.umd.edu krb5_child[1511503]: Preauthentication failed Sep 18 14:32:38 inbound00.cs.umd.edu krb5_child[1514591]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (2 distinct, 2 total) == Sep 18 14:23:53 itmon02 gearmand[1857]: ERROR 2026-09-18 14:23:52.000000 [ 3 ] lost connection to client during send(EPIPE || ECONNRESET || EHOSTDOWN)(Broken pipe) -> libgearman-server/io.cc:397 Sep 18 15:03:35 itmon02 sshd[1750555]: error: beginning MaxStartups throttling == munin (2 distinct, 8 total) == Sep 18 14:24:11 munin sudo[3988821]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 18 14:24:11 munin sudo[3988821]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 18 14:13:02 newhonors2 dhcpcd[2817408]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 18 14:05:21 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 7999/7999, ET: 20) *** Sep 18 14:05:21 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 154, QN: 64/64, ET: 20) *** Sep 18 14:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 155) *** Sep 18 14:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 7322/7322, ET: 0) *** Sep 18 14:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 155) *** Sep 18 14:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 155, QN: 63/63, ET: 0) *** Sep 18 14:08:02 ntop00 setroubleshoot[459959]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12] Sep 18 14:08:02 ntop00 setroubleshoot[459959]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12] Sep 18 14:08:02 ntop00 setroubleshoot[459959]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 18 14:08:02 ntop00 setroubleshoot[459959]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12] Sep 18 14:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) *** Sep 18 14:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 156) *** Sep 18 14:10:22 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 8110/8110, ET: 21) *** Sep 18 14:10:22 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 156, QN: 61/61, ET: 21) *** Sep 18 14:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 157) *** Sep 18 14:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 9410/9410, ET: 0) *** Sep 18 14:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 157) *** Sep 18 14:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 157, QN: 70/70, ET: 0) *** Sep 18 14:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) *** Sep 18 14:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 158) *** Sep 18 14:15:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 9021/9021, ET: 23) *** Sep 18 14:15:24 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 158, QN: 72/72, ET: 23) *** Sep 18 14:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 159) *** Sep 18 14:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 9337/9337, ET: 0) *** Sep 18 14:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 159) *** Sep 18 14:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 159, QN: 53/53, ET: 0) *** Sep 18 14:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) *** Sep 18 14:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 160) *** Sep 18 14:20:26 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 160, QN: 9496/9496, ET: 25) *** Sep 18 14:20:27 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 160, QN: 63/63, ET: 26) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 8 total) == Sep 18 14:09:09 outbound00.cs.umd.edu python3[1383215]: ldapdb [x6] Sep 18 14:51:51 outbound00.cs.umd.edu krb5_child[1393162]: Preauthentication failed [x2] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 18 14:13:06 outbound01.cs.umd.edu python3[3641539]: ldapdb [x6] Sep 18 14:57:15 outbound01.cs.umd.edu krb5_child[3652316]: Preauthentication failed [x2] == portal (1 distinct, 1 total) == Sep 18 14:34:48 portal setroubleshoot[1538049]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l 7fd47d7d-0597-41f1-9a89-8a4911d8024d == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008516]: link_config: could not get ethtool features for veth719c6b4 Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008516]: Could not set offload features of veth719c6b4: No such device Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008539]: Could not generate persistent MAC address for vethe7b79cf: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008538]: Could not generate persistent MAC address for veth6b8538b: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008566]: Could not generate persistent MAC address for veth0c09a03: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008567]: Could not generate persistent MAC address for vethdc61430: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008570]: Could not generate persistent MAC address for vethd45afe5: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008583]: Could not generate persistent MAC address for vetha375b8c: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008594]: Could not generate persistent MAC address for veth2726b25: No such file or directory Sep 18 14:18:17 sentry-docker00.cs.umd.edu systemd-udevd[3008595]: Could not generate persistent MAC address for vethc577a22: No such file or directory Sep 18 14:18:18 sentry-docker00.cs.umd.edu systemd-udevd[3008613]: Could not generate persistent MAC address for vethd9e7416: No such file or directory Sep 18 14:18:18 sentry-docker00.cs.umd.edu systemd-udevd[3008604]: Could not generate persistent MAC address for veth20cedd5: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3017906]: link_config: could not get ethtool features for vethd45afe5 Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3017906]: Could not set offload features of vethd45afe5: No such device Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018020]: Could not generate persistent MAC address for veth36fa3cc: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018021]: Could not generate persistent MAC address for veth4995c6f: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018024]: Could not generate persistent MAC address for veth60bcb47: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018039]: Could not generate persistent MAC address for vethae70834: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018049]: Could not generate persistent MAC address for veth2ada42c: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018048]: Could not generate persistent MAC address for vethd8e3923: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018077]: Could not generate persistent MAC address for vethfbcede8: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018076]: Could not generate persistent MAC address for vetha38c2b5: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018130]: Could not generate persistent MAC address for veth195634f: No such file or directory Sep 18 14:38:26 sentry-docker00.cs.umd.edu systemd-udevd[3018131]: Could not generate persistent MAC address for vethd88d26e: No such file or directory Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027450]: link_config: could not get ethtool features for veth36fa3cc Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027450]: Could not set offload features of veth36fa3cc: No such device Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027491]: Could not generate persistent MAC address for vethf7419f6: No such file or directory Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027492]: Could not generate persistent MAC address for veth28cb41f: No such file or directory Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027495]: Could not generate persistent MAC address for veth3e178cc: No such file or directory Sep 18 14:58:34 sentry-docker00.cs.umd.edu systemd-udevd[3027496]: Could not generate persistent MAC address for veth6389fa6: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 18 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 14:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 18 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 14:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 18 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 10 total) == Sep 18 14:23:06 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 Sep 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.hqjFxG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 Sep 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hqjFxG. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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 18 14:25:53 submit26-b9-f1 setroubleshoot[2324512]: 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, 10 total) == Sep 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ARnup9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ARnup9. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:06:48 submit26-b9-f2 setroubleshoot[1465814]: 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 18 14:40:40 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (1 distinct, 1 total) == Sep 18 15:03:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL