Command: /usr/local/sbin/syslog-digest.py Time : 7.8511s Status : exited 0 Output : Syslog digest — 2026-09-27 10:05 EDT Processed 120,654 lines, filtered 1,760 (1%). 118,894 unknown (162 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 10:02:50 b0b02.cs.umd.edu rustdesk[1661932]: cannot open display: == emaar (1 distinct, 1 total) == Sep 27 09:52:59 emaar systemd[1]: insights-client.service: Start request repeated too quickly. == idm00 (1 distinct, 1 total) == Sep 27 09:54:10 idm00 named[4166701]: client @0x7f11986d48e8 10.73.240.42#58429: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 09:39:30 idmp0 named[1598691]: client @0x7f2d2c03b838 10.73.240.43#64396: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 27 09:18:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 4 total) == Sep 27 09:43:58 munin sudo[200468]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 27 09:43:58 munin sudo[200468]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 27 09:13:03 newhonors2 dhcpcd[3223924]: dhcpcd is not running [x24] == ntop00 (81 distinct, 118730 total) == Sep 27 09:07: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 ] [x7840] Sep 27 09:07: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 ] [x56622] Sep 27 09:07: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 ] [x53694] Sep 27 09:07:10 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 ] [x239] Sep 27 09:07:10 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 ] [x239] Sep 27 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) *** Sep 27 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 52/52, ET: 0) *** Sep 27 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) *** Sep 27 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 5288/5288, ET: 0) *** Sep 27 09:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 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 27 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) *** Sep 27 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 0/5806, ET: 0) *** Sep 27 09:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 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 27 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) *** Sep 27 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 0/60, ET: 0) *** Sep 27 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) *** Sep 27 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 6002/6002, ET: 0) *** Sep 27 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) *** Sep 27 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 67/67, ET: 0) *** Sep 27 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) *** Sep 27 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 4293/4293, ET: 0) *** Sep 27 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) *** Sep 27 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 42/42, ET: 0) *** Sep 27 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) *** Sep 27 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 0/4087, ET: 0) *** Sep 27 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) *** Sep 27 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 0/44, ET: 0) *** Sep 27 09:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1193) *** ... 51 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 09:09:09 outbound00.cs.umd.edu python3[201945]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 27 09:13:06 outbound01.cs.umd.edu python3[2464591]: ldapdb [x6] Sep 27 09:25:17 outbound01.cs.umd.edu krb5_child[2468008]: Preauthentication failed == quiss (5 distinct, 7 total) == Sep 27 09:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show Sep 27 09:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding Sep 27 09:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding Sep 27 09:08:42 quiss packagekitd[3265207]: Failed to get cache filename for perl [x2] Sep 27 09:08:42 quiss packagekitd[3265207]: Failed to get cache filename for kernel [x2] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 27 09:05:26 sentry-docker00.cs.umd.edu systemd-udevd[601611]: link_config: could not get ethtool features for vethbb781f0 Sep 27 09:05:26 sentry-docker00.cs.umd.edu systemd-udevd[601611]: Could not set offload features of vethbb781f0: No such device Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601648]: Could not generate persistent MAC address for veth601fe69: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601649]: Could not generate persistent MAC address for veth603e3e0: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601652]: Could not generate persistent MAC address for veth7107c62: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601653]: Could not generate persistent MAC address for vethc088c49: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601676]: Could not generate persistent MAC address for veth8016fbe: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601677]: Could not generate persistent MAC address for vethcd5ceae: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601690]: Could not generate persistent MAC address for vethc6117c8: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601695]: Could not generate persistent MAC address for veth60d9987: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601691]: Could not generate persistent MAC address for veth9bc5fb5: No such file or directory Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601690]: Could not generate persistent MAC address for vethaf55200: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611403]: link_config: could not get ethtool features for veth7107c62 Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611403]: Could not set offload features of veth7107c62: No such device Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611456]: link_config: could not get ethtool features for veth9bc5fb5 Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611456]: Could not set offload features of veth9bc5fb5: No such device Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611496]: Could not generate persistent MAC address for vethbdde582: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611497]: Could not generate persistent MAC address for veth1bc7ba4: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611500]: Could not generate persistent MAC address for veth65b7708: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611501]: Could not generate persistent MAC address for veth7242ed0: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611500]: Could not generate persistent MAC address for veth569069a: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611513]: Could not generate persistent MAC address for veth102a333: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611511]: Could not generate persistent MAC address for vetha7c935d: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611517]: Could not generate persistent MAC address for veth2c8bb88: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611513]: Could not generate persistent MAC address for veth159f3d6: No such file or directory Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611511]: Could not generate persistent MAC address for veth6ec8721: No such file or directory Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620918]: Could not generate persistent MAC address for vethb54fcd4: No such file or directory Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620919]: Could not generate persistent MAC address for vethb879ea0: No such file or directory Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620919]: Could not generate persistent MAC address for veth604cd3e: No such file or directory Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620941]: Could not generate persistent MAC address for veth3217ff3: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 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 27 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 27 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 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 27 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 27 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Sep 27 09:08:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 2 total) == Sep 27 09:12:09 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (10 distinct, 16 total) == Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.M9veDD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.M9veDD. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: 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 27 09:10:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (10 distinct, 16 total) == Sep 27 09:08:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 [x2] Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PIMVJA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 [x2] Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.PIMVJA. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: 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 27 09:24:51 submit26-b9-f4 setroubleshoot[2694081]: 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