Command: /usr/local/sbin/syslog-digest.py Time : 0.0503s Status : exited 0 Output : Syslog digest — 2026-09-22 02:05 EDT Processed 1,878 lines, filtered 1,339 (71%). 539 unknown (199 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 22 01:54:42 b0b02.cs.umd.edu rustdesk[3826632]: cannot open display: == bachata (10 distinct, 10 total) == Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.248512, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Sep 22 01:52:48 bachata smbd[951283]: 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 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250108, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_tcon_disconnect: disconnect(0x3bcf4414, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250594, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR] Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250693, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x66970deb): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Sep 22 01:52:48 bachata smbd[951283]: [2026/09/22 01:52:48.250793, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Sep 22 01:52:48 bachata smbd[951283]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(1721175531) failed: NT_STATUS_INTERNAL_ERROR == bale (5 distinct, 87 total) == Sep 22 01:05:37 bale setroubleshoot[1639980]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 22 01:05:38 bale setroubleshoot[1639980]: 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 22 01:05:40 bale setroubleshoot[1639980]: 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 22 01:05:43 bale setroubleshoot[1639980]: 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 22 01:05:55 bale setroubleshoot[1640596]: 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] == cheezit.cs.umd.edu (4 distinct, 4 total) == Sep 22 01:27:30 cheezit.cs.umd.edu sshd-session[1757776]: pam_access(sshd:auth): access denied for user `admin' from `34.52.144.133' Sep 22 01:27:30 cheezit.cs.umd.edu krb5_child[1757778]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 22 01:27:30 cheezit.cs.umd.edu sshd-session[1757774]: error: PAM: System error for admin from 34.52.144.133 Sep 22 01:29:01 cheezit.cs.umd.edu sshd-session[1758075]: error: Protocol major versions differ: 2 vs. 1 == csfw00a (2 distinct, 131 total) == Sep 22 01:03:59 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x129] Sep 22 01:14:40 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2] == idm00 (1 distinct, 1 total) == Sep 22 01:54:03 idm00 named[4166701]: client @0x7f11a0057bb8 10.73.240.42#63462: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 22 01:37:55 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#64970: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 22 01:23:03 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 14 total) == Sep 22 01:08:08 munin sudo[1594464]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x7] Sep 22 01:08:08 munin sudo[1594464]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x7] == newhonors2 (1 distinct, 24 total) == Sep 22 01:13:03 newhonors2 dhcpcd[2974078]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 22 01:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 22 01:05:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6083/6083, ET: 31) *** Sep 22 01:05:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 56/56, ET: 31) *** Sep 22 01:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 22 01:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6043/6043, ET: 0) *** Sep 22 01:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 22 01:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 54/54, ET: 0) *** Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12] Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12] Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 22 01:08:02 ntop00 setroubleshoot[1120213]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12] Sep 22 01:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 22 01:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 22 01:10:31 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 5638/5638, ET: 30) *** Sep 22 01:10:31 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 51/51, ET: 30) *** Sep 22 01:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 22 01:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 4789/4789, ET: 0) *** Sep 22 01:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 22 01:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 48/48, ET: 0) *** Sep 22 01:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 22 01:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 22 01:15:25 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 4471/4471, ET: 24) *** Sep 22 01:15:25 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 40/40, ET: 24) *** Sep 22 01:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 22 01:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 4680/4680, ET: 0) *** Sep 22 01:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 22 01:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 37/37, ET: 0) *** Sep 22 01:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 22 01:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 22 01:20:27 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 4792/4792, ET: 26) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (3 distinct, 8 total) == Sep 22 01:09:09 outbound00.cs.umd.edu python3[2555481]: ldapdb [x6] Sep 22 02:02:50 outbound00.cs.umd.edu krb5_child[2568197]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 22 02:02:56 outbound00.cs.umd.edu sshd-session[2568230]: error: Protocol major versions differ: 2 vs. 1 == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 22 01:13:07 outbound01.cs.umd.edu python3[622735]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 22 01:42:59 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 22 01:12:32 sentry-docker00.cs.umd.edu systemd-udevd[1159137]: link_config: could not get ethtool features for vethe0eb035 Sep 22 01:12:32 sentry-docker00.cs.umd.edu systemd-udevd[1159137]: Could not set offload features of vethe0eb035: No such device Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159175]: Could not generate persistent MAC address for vethda633f2: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159176]: Could not generate persistent MAC address for vethc4cbce5: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159179]: Could not generate persistent MAC address for veth658a0ce: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159192]: Could not generate persistent MAC address for vethac85d33: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159176]: Could not generate persistent MAC address for vethdcbb6a1: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159180]: Could not generate persistent MAC address for veth5579e0d: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159191]: Could not generate persistent MAC address for veth66ea1c4: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159196]: Could not generate persistent MAC address for vethd42300e: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159304]: Could not generate persistent MAC address for vethfc18506: No such file or directory Sep 22 01:12:33 sentry-docker00.cs.umd.edu systemd-udevd[1159310]: Could not generate persistent MAC address for veth10bfdf7: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168713]: link_config: could not get ethtool features for vethfc18506 Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168713]: Could not set offload features of vethfc18506: No such device Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168822]: Could not generate persistent MAC address for vethe849b9f: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168823]: Could not generate persistent MAC address for vethc3bf175: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for veth2997f75: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168851]: Could not generate persistent MAC address for veth2be485b: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168859]: Could not generate persistent MAC address for veth4593b36: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168867]: Could not generate persistent MAC address for vethb99dade: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168863]: Could not generate persistent MAC address for vetha878903: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for vethee335aa: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168850]: Could not generate persistent MAC address for veth5685369: No such file or directory Sep 22 01:32:41 sentry-docker00.cs.umd.edu systemd-udevd[1168863]: Could not generate persistent MAC address for veth63b06d1: No such file or directory Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178118]: link_config: could not get ethtool features for vethe849b9f Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178118]: Could not set offload features of vethe849b9f: No such device Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178236]: Could not generate persistent MAC address for vetha18968c: No such file or directory Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178237]: Could not generate persistent MAC address for veth1a67fe9: No such file or directory Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178255]: Could not generate persistent MAC address for vethe045dfd: No such file or directory Sep 22 01:52:49 sentry-docker00.cs.umd.edu systemd-udevd[1178262]: Could not generate persistent MAC address for vetha1bf529: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 22 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 22 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 22 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 22 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 22 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 22 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 22 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 22 01:59:00 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 5 total) == Sep 22 01:05:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (10 distinct, 12 total) == Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1Ltup3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1Ltup3. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:06:43 submit26-b9-f3 setroubleshoot[2438171]: 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 22 01:15:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (10 distinct, 10 total) == Sep 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:48 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aRN0WU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aRN0WU. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:24:49 submit26-b9-f4 setroubleshoot[1777317]: 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 22 01:53:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == teaching-awards (1 distinct, 1 total) == Sep 22 01:05:13 teaching-awards krb5_child[1299444]: Client 'admin@UMD.EDU' not found in Kerberos database