Command: /usr/local/sbin/syslog-digest.py Time : 0.0547s Status : exited 0 Output : Syslog digest — 2026-09-19 10:05 EDT Processed 2,933 lines, filtered 2,416 (82%). 517 unknown (198 distinct) from 21 host(s). == b0b02.cs.umd.edu (2 distinct, 2 total) == Sep 19 09:07:09 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. Sep 19 09:50:45 b0b02.cs.umd.edu rustdesk[2847205]: cannot open display: == bachata (10 distinct, 10 total) == Sep 19 09:48:01 bachata smbd[815649]: [2026/09/19 09:48:01.527821, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Sep 19 09:48:01 bachata smbd[815649]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026 Sep 19 09:48:01 bachata smbd[815649]: [2026/09/19 09:48:01.528610, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Sep 19 09:48:01 bachata smbd[815649]: smbXsrv_tcon_disconnect: disconnect(0x893c7d8c, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Sep 19 09:48:01 bachata smbd[815649]: [2026/09/19 09:48:01.529733, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Sep 19 09:48:01 bachata smbd[815649]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR] Sep 19 09:48:01 bachata smbd[815649]: [2026/09/19 09:48:01.529841, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Sep 19 09:48:01 bachata smbd[815649]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x247bf92a): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Sep 19 09:48:01 bachata smbd[815649]: [2026/09/19 09:48:01.529977, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Sep 19 09:48:01 bachata smbd[815649]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(612104490) failed: NT_STATUS_INTERNAL_ERROR == bale (5 distinct, 88 total) == Sep 19 09:05:29 bale setroubleshoot[819418]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 19 09:05:30 bale setroubleshoot[819418]: 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 09:05:32 bale setroubleshoot[819418]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 19 09:05:35 bale setroubleshoot[819418]: 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 [x12] Sep 19 09:05:47 bale setroubleshoot[820047]: 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, 118 total) == Sep 19 09:03:46 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] == idm00 (1 distinct, 1 total) == Sep 19 09:53:59 idm00 named[4166701]: client @0x7f11a8045438 10.73.240.42#63126: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 09:37:58 idmp0 named[1598691]: client @0x7f2d500408e8 10.73.240.43#56219: update '73.10.in-addr.arpa/IN' denied == irb2156 (3 distinct, 5 total) == Sep 19 09:55:03 irb2156 packagekitd[524951]: Failed to get cache filename for firefox-nightly Sep 19 09:55:03 irb2156 packagekitd[524951]: Failed to get cache filename for google-chrome-stable Sep 19 09:55:03 irb2156 packagekitd[524951]: Failed to get cache filename for kernel [x3] == itmon02 (1 distinct, 2 total) == Sep 19 09:43:12 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == mcstic (1 distinct, 2 total) == Sep 19 09:08:56 mcstic sshd[808130]: fatal: userauth_finish: send failure packet: Broken pipe [preauth] [x2] == munin (2 distinct, 4 total) == Sep 19 09:07:57 munin sudo[202634]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 19 09:07:57 munin sudo[202634]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == netman.cs.umd.edu (1 distinct, 1 total) == Sep 19 09:16:11 netman.cs.umd.edu sshd[2345399]: fatal: userauth_finish: Broken pipe [preauth] == newhonors2 (1 distinct, 24 total) == Sep 19 09:13:03 newhonors2 dhcpcd[2852942]: dhcpcd is not running [x24] == ntop00 (102 distinct, 146 total) == Sep 19 09:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) *** Sep 19 09:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) *** Sep 19 09:05:19 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 5438/5438, ET: 18) *** Sep 19 09:05:19 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 43/43, ET: 18) *** Sep 19 09:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 19 09:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 5124/5124, ET: 0) *** Sep 19 09:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 19 09:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 52/52, ET: 0) *** Sep 19 09:08:02 ntop00 setroubleshoot[611237]: 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 09:08:02 ntop00 setroubleshoot[611237]: 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 09:08:03 ntop00 setroubleshoot[611237]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 09:08:03 ntop00 setroubleshoot[611237]: 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 09:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 19 09:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 19 09:10:17 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 4962/4962, ET: 16) *** Sep 19 09:10:17 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 54/54, ET: 16) *** Sep 19 09:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 19 09:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 5126/5126, ET: 0) *** Sep 19 09:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 19 09:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 47/47, ET: 0) *** Sep 19 09:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 19 09:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 19 09:15:17 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 5144/5144, ET: 16) *** Sep 19 09:15:17 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 43/43, ET: 16) *** Sep 19 09:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 19 09:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 4767/4767, ET: 0) *** Sep 19 09:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 19 09:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 57/57, ET: 0) *** Sep 19 09:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** Sep 19 09:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** ... 72 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 09:09:09 outbound00.cs.umd.edu python3[1652548]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 09:13:06 outbound01.cs.umd.edu python3[3911166]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 09:06:03 sentry-docker00.cs.umd.edu systemd-udevd[3539841]: link_config: could not set ethtool features for veth0dfcfe5 Sep 19 09:06:03 sentry-docker00.cs.umd.edu systemd-udevd[3539841]: Could not set offload features of veth0dfcfe5: Operation not permitted Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539911]: Could not generate persistent MAC address for veth5cb986e: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539912]: Could not generate persistent MAC address for veth134a64a: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539915]: Could not generate persistent MAC address for vethb54c531: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539916]: Could not generate persistent MAC address for veth7acd24d: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539939]: Could not generate persistent MAC address for veth097bf1a: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539940]: Could not generate persistent MAC address for vethd237eb7: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539943]: Could not generate persistent MAC address for veth30f8750: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539959]: Could not generate persistent MAC address for veth0b50abd: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539960]: Could not generate persistent MAC address for veth93ae0a9: No such file or directory Sep 19 09:06:04 sentry-docker00.cs.umd.edu systemd-udevd[3539957]: Could not generate persistent MAC address for veth773ddd6: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549519]: link_config: could not get ethtool features for veth5cb986e Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549519]: Could not set offload features of veth5cb986e: No such device Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549550]: Could not generate persistent MAC address for veth6b7d0bb: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549551]: Could not generate persistent MAC address for veth8c2b5b4: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549554]: Could not generate persistent MAC address for veth4bb6dd4: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549555]: Could not generate persistent MAC address for veth34b616d: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549578]: Could not generate persistent MAC address for vethed461cc: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549579]: Could not generate persistent MAC address for veth9588bfe: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549597]: Could not generate persistent MAC address for veth7fbc606: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549592]: Could not generate persistent MAC address for veth850fde4: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549592]: Could not generate persistent MAC address for vethcc24022: No such file or directory Sep 19 09:26:12 sentry-docker00.cs.umd.edu systemd-udevd[3549589]: Could not generate persistent MAC address for vethbd39efc: No such file or directory Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3558982]: link_config: could not get ethtool features for vethed461cc Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3558982]: Could not set offload features of vethed461cc: No such device Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3559012]: Could not generate persistent MAC address for veth356dcf6: No such file or directory Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3559013]: Could not generate persistent MAC address for veth6331061: No such file or directory Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3559031]: Could not generate persistent MAC address for vethfbc50f4: No such file or directory Sep 19 09:46:20 sentry-docker00.cs.umd.edu systemd-udevd[3559022]: Could not generate persistent MAC address for vethf6280f9: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 09: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 09: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 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 09: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 09: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 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 19 09:18:06 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Sep 19 09:18:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 14 total) == Sep 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 [x2] Sep 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 [x2] Sep 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.u2ir00/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.u2ir00. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 19 09:06:42 submit26-b9-f3 setroubleshoot[1960842]: 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 19 09:15:32 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (10 distinct, 11 total) == Sep 19 09:18:07 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 19 09:24:45 submit26-b9-f4 setroubleshoot[1422558]: 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 19 09:24:45 submit26-b9-f4 setroubleshoot[1422558]: 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 19 09:24:45 submit26-b9-f4 setroubleshoot[1422558]: 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 Sep 19 09:24:45 submit26-b9-f4 setroubleshoot[1422558]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.6HqVAk/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 19 09:24:46 submit26-b9-f4 setroubleshoot[1422558]: 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 Sep 19 09:24:46 submit26-b9-f4 setroubleshoot[1422558]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6HqVAk. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 19 09:24:46 submit26-b9-f4 setroubleshoot[1422558]: 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 19 09:24:46 submit26-b9-f4 setroubleshoot[1422558]: 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 19 09:24:46 submit26-b9-f4 setroubleshoot[1422558]: 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