Command: /usr/local/sbin/syslog-digest.py Time : 7.4640s Status : exited 0 Output : Syslog digest — 2026-09-27 19:05 EDT Processed 119,186 lines, filtered 1,258 (1%). 117,928 unknown (150 distinct) from 14 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 27 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-27T22:10:59.433778444Z" level=info msg="PurgeUploads starting: olderThan=2026-09-20 22:10:59.433411624 +0000 UTC m=+4754220.193339961, actuallyDelete=true" Sep 27 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-27T22:10:59.434423121Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 27 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-27T22:10:59.434450668Z" 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 27 19:03:27 b0b02.cs.umd.edu rustdesk[1799033]: cannot open display: == bachata (19 distinct, 20 total) == Sep 27 18:16:03 bachata smbd[1294707]: [2026/09/27 18:16:03.961079, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Sep 27 18:16:03 bachata smbd[1294707]: 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 27 18:16:03 bachata smbd[1294707]: [2026/09/27 18:16:03.961845, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Sep 27 18:16:03 bachata smbd[1294707]: smbXsrv_tcon_disconnect: disconnect(0xb63afd6e, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Sep 27 18:16:03 bachata smbd[1294707]: [2026/09/27 18:16:03.962149, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Sep 27 18:16:03 bachata smbd[1294707]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR] [x2] Sep 27 18:16:03 bachata smbd[1294707]: [2026/09/27 18:16:03.962223, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Sep 27 18:16:03 bachata smbd[1294707]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x6ced1deb): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Sep 27 18:16:03 bachata smbd[1294707]: [2026/09/27 18:16:03.962319, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Sep 27 18:16:03 bachata smbd[1294707]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(1827479019) failed: NT_STATUS_INTERNAL_ERROR Sep 27 18:29:10 bachata smbd[1280263]: [2026/09/27 18:29:10.393579, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Sep 27 18:29:10 bachata smbd[1280263]: chdir_current_service: vfs_ChDir(/fs/junkfood/nelson) failed: Permission denied. Current token: uid=20608, gid=20608, 19 groups: 20608 31006 30043 319050000 30736 30871 25274 15248 15206 25025 15294 15228 319000009 30872 25057 30742 25200 25038 25195 Sep 27 18:29:10 bachata smbd[1280263]: [2026/09/27 18:29:10.394227, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Sep 27 18:29:10 bachata smbd[1280263]: smbXsrv_tcon_disconnect: disconnect(0xfe41637f, 'nelson'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Sep 27 18:29:10 bachata smbd[1280263]: [2026/09/27 18:29:10.394363, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Sep 27 18:29:10 bachata smbd[1280263]: [2026/09/27 18:29:10.394418, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Sep 27 18:29:10 bachata smbd[1280263]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xa4ecb5be): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Sep 27 18:29:10 bachata smbd[1280263]: [2026/09/27 18:29:10.394472, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Sep 27 18:29:10 bachata smbd[1280263]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(2766976446) failed: NT_STATUS_INTERNAL_ERROR == idm00 (1 distinct, 1 total) == Sep 27 18:54:09 idm00 named[4166701]: client @0x7f11a006da58 10.73.240.42#62727: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 18:39:28 idmp0 named[1598691]: client @0x7f2d34106cd8 10.73.240.43#51120: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 27 18:08:07 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == newhonors2 (1 distinct, 24 total) == Sep 27 18:13:02 newhonors2 dhcpcd[3241176]: dhcpcd is not running [x24] == ntop00 (56 distinct, 117750 total) == Sep 27 18:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 18:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x6] Sep 27 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1402) *** Sep 27 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1402, QN: 0/57, ET: 0) *** Sep 27 18:05:10 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56216] Sep 27 18:05:10 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x53584] Sep 27 18:05:10 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7428] Sep 27 18:05:16 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223] Sep 27 18:05:16 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x223] Sep 27 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1405) *** Sep 27 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1405, QN: 61/61, ET: 0) *** Sep 27 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1405) *** Sep 27 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1405, QN: 7520/7520, ET: 0) *** Sep 27 18:14:02 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x8] Sep 27 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1406) *** Sep 27 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1406, QN: 0/58, ET: 0) *** Sep 27 18:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x5] Sep 27 18:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x5] Sep 27 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1406) *** Sep 27 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1406, QN: 0/7313, ET: 0) *** Sep 27 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1409) *** Sep 27 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1409, QN: 8149/8149, ET: 0) *** Sep 27 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1409) *** Sep 27 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1409, QN: 74/74, ET: 0) *** Sep 27 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1410) *** Sep 27 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1410, QN: 0/7506, ET: 0) *** Sep 27 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1410) *** Sep 27 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1410, QN: 0/67, ET: 0) *** Sep 27 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1413) *** Sep 27 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1413, QN: 7323/7323, ET: 0) *** ... 26 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 18:09:09 outbound00.cs.umd.edu python3[328724]: ldapdb [x6] == outbound01.cs.umd.edu (5 distinct, 22 total) == Sep 27 18:13:06 outbound01.cs.umd.edu python3[2592116]: ldapdb [x6] Sep 27 18:30:01 outbound01.cs.umd.edu krb5_child[2596282]: Client 'backup@UMD.EDU' not found in Kerberos database Sep 27 18:31:48 outbound01.cs.umd.edu krb5_child[2596831]: Client 'admin@UMD.EDU' not found in Kerberos database [x8] Sep 27 18:38:56 outbound01.cs.umd.edu krb5_child[2598423]: Preauthentication failed [x6] Sep 27 18:51:01 outbound01.cs.umd.edu krb5_child[2601325]: Client 'test1@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857893]: link_config: could not get ethtool features for veth2e1f765 Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857893]: Could not set offload features of veth2e1f765: No such device Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857928]: Could not generate persistent MAC address for veth661ebf5: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857929]: Could not generate persistent MAC address for veth0a0dfb1: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857932]: Could not generate persistent MAC address for veth2475e7d: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857933]: Could not generate persistent MAC address for veth0c4fd3a: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857955]: Could not generate persistent MAC address for vethe3138af: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857936]: Could not generate persistent MAC address for vethaa5b198: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857936]: Could not generate persistent MAC address for vethbd1e5bd: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857955]: Could not generate persistent MAC address for veth2c8151d: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857933]: Could not generate persistent MAC address for veth391f408: No such file or directory Sep 27 18:09:11 sentry-docker00.cs.umd.edu systemd-udevd[857944]: Could not generate persistent MAC address for veth15b1f7c: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867258]: Could not generate persistent MAC address for veth70f7d9a: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867259]: Could not generate persistent MAC address for vethe6c5148: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867262]: Could not generate persistent MAC address for veth344b101: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867263]: Could not generate persistent MAC address for veth74307b7: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867281]: Could not generate persistent MAC address for veth65b36ab: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867278]: Could not generate persistent MAC address for veth349ee98: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867268]: Could not generate persistent MAC address for veth128eca5: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867267]: Could not generate persistent MAC address for veth9c8a91b: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867338]: Could not generate persistent MAC address for vethd03a1f2: No such file or directory Sep 27 18:29:20 sentry-docker00.cs.umd.edu systemd-udevd[867342]: Could not generate persistent MAC address for veth99a11da: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876668]: link_config: could not get ethtool features for veth344b101 Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876668]: Could not set offload features of veth344b101: No such device Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876706]: Could not generate persistent MAC address for vethf300d93: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876707]: Could not generate persistent MAC address for vethf523663: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876710]: Could not generate persistent MAC address for veth4281332: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876711]: Could not generate persistent MAC address for veth0d369fa: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876721]: Could not generate persistent MAC address for veth4442c80: No such file or directory Sep 27 18:49:28 sentry-docker00.cs.umd.edu systemd-udevd[876716]: Could not generate persistent MAC address for vethce3e3e1: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 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 27 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 27 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 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 27 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 27 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 18:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 14 total) == Sep 27 18:25:57 submit26-b9-f1 setroubleshoot[3962930]: 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 [x2] Sep 27 18:25:57 submit26-b9-f1 setroubleshoot[3962930]: 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 [x2] Sep 27 18:25:57 submit26-b9-f1 setroubleshoot[3962930]: 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 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WYxKH9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: 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 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WYxKH9. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: 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 [x2] Sep 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: 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 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: 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 [x2] Sep 27 18:25:58 submit26-b9-f1 setroubleshoot[3962930]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x0fdqi. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (9 distinct, 9 total) == Sep 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vsUpY9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vsUpY9. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 27 18:06:51 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:52 submit26-b9-f2 setroubleshoot[3043108]: 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 27 18:06:52 submit26-b9-f2 setroubleshoot[3043108]: 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 == unknown (1 distinct, 1 total) == using-explainable-ai