Command: /usr/local/sbin/syslog-digest.py Time : 7.8321s Status : exited 0 Output : Syslog digest — 2026-09-26 10:05 EDT Processed 120,451 lines, filtered 1,528 (1%). 118,923 unknown (164 distinct) from 16 host(s). == b0b02.cs.umd.edu (2 distinct, 2 total) == Sep 26 09:42:28 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. Sep 26 10:01:23 b0b02.cs.umd.edu rustdesk[1294047]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 1 total) == Sep 26 09:11:22 biggulp.cs.umd.edu sshd-session[185123]: error: send_error: write: Connection reset by peer == idm00 (1 distinct, 1 total) == Sep 26 09:54:09 idm00 named[4166701]: client @0x7f1198541268 10.73.240.42#60910: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 09:39:29 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#57757: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 26 09:28:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == mcstic (1 distinct, 2 total) == Sep 26 09:36:38 mcstic krb5_child[1148061]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == munin (2 distinct, 12 total) == Sep 26 09:08:12 munin sudo[3858966]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 26 09:08:12 munin sudo[3858966]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 26 09:13:03 newhonors2 dhcpcd[3178990]: dhcpcd is not running [x24] == ntop00 (82 distinct, 118756 total) == Sep 26 09:07:21 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 ] [x56665] Sep 26 09:07:21 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 ] [x53732] Sep 26 09:07:21 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 ] [x221] Sep 26 09:07:21 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 ] [x221] Sep 26 09:07:21 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 ] [x7820] Sep 26 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 611) *** Sep 26 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 611, QN: 69/69, ET: 0) *** Sep 26 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 611) *** Sep 26 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 611, QN: 6560/6560, ET: 0) *** Sep 26 09:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 09:10: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 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 612) *** Sep 26 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 612, QN: 0/6654, ET: 0) *** Sep 26 09:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 09:10: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 26 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 612) *** Sep 26 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 612, QN: 0/64, ET: 0) *** Sep 26 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 613) *** Sep 26 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 613, QN: 5738/5738, ET: 0) *** Sep 26 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 613) *** Sep 26 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 613, QN: 62/62, ET: 0) *** Sep 26 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 615) *** Sep 26 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 615, QN: 4872/4872, ET: 0) *** Sep 26 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 615) *** Sep 26 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 615, QN: 59/59, ET: 0) *** Sep 26 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 616) *** Sep 26 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 616, QN: 0/5669, ET: 0) *** Sep 26 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 616) *** Sep 26 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 616, QN: 0/58, ET: 0) *** Sep 26 09:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 617) *** ... 52 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 09:09:09 outbound00.cs.umd.edu python3[4057180]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 09:13:07 outbound01.cs.umd.edu python3[2123863]: ldapdb [x6] == quiss (6 distinct, 10 total) == Sep 26 09:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show Sep 26 09:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding Sep 26 09:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for claude-code Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for perl [x3] Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for kernel [x3] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120939]: link_config: could not get ethtool features for veth835142c Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120939]: Could not set offload features of veth835142c: No such device Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120965]: Could not generate persistent MAC address for veth3e997b3: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120966]: Could not generate persistent MAC address for veth2467fe9: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120991]: Could not generate persistent MAC address for veth2334793: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120993]: Could not generate persistent MAC address for veth4fd7824: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121013]: Could not generate persistent MAC address for vethade818e: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120991]: Could not generate persistent MAC address for veth535e907: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121011]: Could not generate persistent MAC address for vethc8b1a86: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121015]: Could not generate persistent MAC address for veth04551f3: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121060]: Could not generate persistent MAC address for veth68fad4d: No such file or directory Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121055]: Could not generate persistent MAC address for veth51752a3: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130800]: link_config: could not get ethtool features for veth2334793 Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130800]: Could not set offload features of veth2334793: No such device Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130895]: link_config: could not get ethtool features for veth3e997b3 Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130895]: Could not set offload features of veth3e997b3: No such device Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130924]: Could not generate persistent MAC address for vethf601589: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130925]: Could not generate persistent MAC address for vethdcfb3c6: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130928]: Could not generate persistent MAC address for vethb043135: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130939]: Could not generate persistent MAC address for veth82c949d: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130949]: Could not generate persistent MAC address for vethe55c147: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130938]: Could not generate persistent MAC address for vethb9da126: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130948]: Could not generate persistent MAC address for veth6fd4da2: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130931]: Could not generate persistent MAC address for vethc3def5d: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130949]: Could not generate persistent MAC address for vethfb444d1: No such file or directory Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130933]: Could not generate persistent MAC address for vethaff41e7: No such file or directory Sep 26 09:55:52 sentry-docker00.cs.umd.edu systemd-udevd[4140252]: link_config: could not get ethtool features for vethe55c147 Sep 26 09:55:52 sentry-docker00.cs.umd.edu systemd-udevd[4140252]: Could not set offload features of vethe55c147: No such device Sep 26 09:55:53 sentry-docker00.cs.umd.edu systemd-udevd[4140287]: Could not generate persistent MAC address for veth18d7ba7: No such file or directory Sep 26 09:55:53 sentry-docker00.cs.umd.edu systemd-udevd[4140288]: Could not generate persistent MAC address for vethb349a5a: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 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 26 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 26 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 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 26 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 26 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 14 total) == Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.meXjIW/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.meXjIW. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 [x2] Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 [x2] Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.q4xsFl. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd == submit26-b9-f4 (9 distinct, 9 total) == Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.VmKVbq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.VmKVbq. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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