Command: /usr/local/sbin/syslog-digest.py Time : 7.4710s Status : exited 0 Output : Syslog digest — 2026-09-26 19:05 EDT Processed 119,167 lines, filtered 1,292 (1%). 117,875 unknown (154 distinct) from 18 host(s). == b0b02.cs.umd.edu (4 distinct, 4 total) == Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.432674077Z" level=info msg="PurgeUploads starting: olderThan=2026-09-19 22:10:59.432582124 +0000 UTC m=+4667820.192510430, actuallyDelete=true" Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.433177891Z" level=info msg="Purge uploads finished. Num deleted=0, num errors=1" Sep 26 18:10:59 b0b02.cs.umd.edu csregistry[5224]: time="2026-09-26T22:10:59.433198191Z" 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 26 19:01:53 b0b02.cs.umd.edu rustdesk[1431264]: cannot open display: == bachata (10 distinct, 10 total) == Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.015446, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Sep 26 18:31:45 bachata smbd[1238547]: 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 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017071, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect) Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_tcon_disconnect: disconnect(0x33599d29, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017314, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all) Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR] Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017378, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff) Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_session_logoff: smbXsrv_session_logoff(0xb34c0db1): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR Sep 26 18:31:45 bachata smbd[1238547]: [2026/09/26 18:31:45.017480, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) Sep 26 18:31:45 bachata smbd[1238547]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(3008105905) failed: NT_STATUS_INTERNAL_ERROR == galax (1 distinct, 1 total) == Sep 26 18:54:54 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK == idm00 (1 distinct, 1 total) == Sep 26 18:54:08 idm00 named[4166701]: client @0x7f11a429b368 10.73.240.42#51239: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 18:39:28 idmp0 named[1598691]: client @0x7f2d4c0213e8 10.73.240.43#51841: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 2 total) == Sep 26 18:06:58 inbound01.cs.umd.edu krb5_child[2353005]: Preauthentication failed [x2] == itmon02 (1 distinct, 4 total) == Sep 26 18:28:07 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 4 total) == Sep 26 18:43:15 munin sudo[4067370]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 26 18:43:15 munin sudo[4067370]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 26 18:13:03 newhonors2 dhcpcd[3195748]: dhcpcd is not running [x24] == ntop00 (59 distinct, 117703 total) == Sep 26 18:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7] Sep 26 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) [x7] Sep 26 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 826) *** Sep 26 18:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 826, QN: 0/75, ET: 0) *** Sep 26 18:05:08 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 ] [x7498] Sep 26 18:05:08 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 ] [x56157] Sep 26 18:05:08 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 ] [x53500] Sep 26 18:05:08 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 ] [x236] Sep 26 18:05:08 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 ] [x236] Sep 26 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 829) *** Sep 26 18:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 74/74, ET: 0) *** Sep 26 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 829) *** Sep 26 18:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 829, QN: 14603/14603, ET: 0) *** Sep 26 18:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 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) [x6] Sep 26 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) *** Sep 26 18:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 0/15080, ET: 0) *** Sep 26 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 830) *** Sep 26 18:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 830, QN: 0/62, ET: 0) *** Sep 26 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 833) *** Sep 26 18:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 833, QN: 11982/11982, ET: 0) *** Sep 26 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 833) *** Sep 26 18:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 833, QN: 54/54, ET: 0) *** Sep 26 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 834) *** Sep 26 18:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 834, QN: 0/12326, ET: 0) *** Sep 26 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 834) *** Sep 26 18:25:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 834, QN: 0/51, ET: 0) *** Sep 26 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 837) *** Sep 26 18:33:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 837, QN: 13345/13345, ET: 0) *** Sep 26 18:33:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 837) *** ... 29 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 18:09:09 outbound00.cs.umd.edu python3[4183303]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 10 total) == Sep 26 18:05:25 outbound01.cs.umd.edu krb5_child[2249448]: Client 'admin@UMD.EDU' not found in Kerberos database [x3] Sep 26 18:13:06 outbound01.cs.umd.edu python3[2251251]: ldapdb [x6] Sep 26 18:25:49 outbound01.cs.umd.edu krb5_child[2254648]: Preauthentication failed == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: link_config: could not get ethtool features for veth61e1ba7 Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: Could not set offload features of veth61e1ba7: No such device Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: link_config: could not get ethtool features for veth2d0190e Sep 26 18:19:20 sentry-docker00.cs.umd.edu systemd-udevd[183981]: Could not set offload features of veth2d0190e: No such device Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184104]: Could not generate persistent MAC address for veth9ba8551: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184103]: Could not generate persistent MAC address for vethff86a8f: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184107]: Could not generate persistent MAC address for vetha89d4cd: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184108]: Could not generate persistent MAC address for veth7699f67: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184129]: Could not generate persistent MAC address for veth894f636: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184128]: Could not generate persistent MAC address for veth563736b: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184133]: Could not generate persistent MAC address for veth5abad6b: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184134]: Could not generate persistent MAC address for veth59b201e: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184193]: Could not generate persistent MAC address for veth3158d12: No such file or directory Sep 26 18:19:21 sentry-docker00.cs.umd.edu systemd-udevd[184197]: Could not generate persistent MAC address for vethe91f429: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193545]: link_config: could not get ethtool features for vetha89d4cd Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193545]: Could not set offload features of vetha89d4cd: No such device Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193550]: link_config: could not set ethtool features for veth5abad6b Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193550]: Could not set offload features of veth5abad6b: Operation not permitted Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193583]: Could not generate persistent MAC address for vethbdfa9d4: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193584]: Could not generate persistent MAC address for vethe441da5: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193587]: Could not generate persistent MAC address for veth41c81c7: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193588]: Could not generate persistent MAC address for vethc42657c: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193602]: Could not generate persistent MAC address for vethca493be: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193605]: Could not generate persistent MAC address for vetha1e8baf: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193606]: Could not generate persistent MAC address for veth36a3406: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193603]: Could not generate persistent MAC address for veth29de73e: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193587]: Could not generate persistent MAC address for vethc9e4e70: No such file or directory Sep 26 18:39:29 sentry-docker00.cs.umd.edu systemd-udevd[193603]: Could not generate persistent MAC address for veth9132a1c: No such file or directory Sep 26 18:59:37 sentry-docker00.cs.umd.edu systemd-udevd[202932]: link_config: could not get ethtool features for veth9132a1c Sep 26 18:59:37 sentry-docker00.cs.umd.edu systemd-udevd[202932]: Could not set offload features of veth9132a1c: No such device ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 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 26 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 26 18:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 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 26 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 26 18:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.U2SsKm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.U2SsKm. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: 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 26 18:25:57 submit26-b9-f1 setroubleshoot[3802851]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.D3pnXd. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (10 distinct, 11 total) == Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XC0XgU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XC0XgU. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:06:51 submit26-b9-f2 setroubleshoot[2879654]: 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 26 18:28:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (1 distinct, 1 total) == Sep 26 18:07:40 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == wraith (1 distinct, 1 total) == Sep 26 18:56:31 wraith kernel: kauditd_printk_skb: 20 callbacks suppressed