Command: /usr/local/sbin/syslog-digest.py Time : 7.5247s Status : exited 0 Output : Syslog digest — 2026-09-27 06:05 EDT Processed 120,326 lines, filtered 1,444 (1%). 118,882 unknown (134 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 06:02:36 b0b02.cs.umd.edu rustdesk[1599973]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 27 05:49:02 grades01.cs.umd.edu puppet-agent[8578]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees == idm00 (1 distinct, 1 total) == Sep 27 05:54:09 idm00 named[4166701]: client @0x7f11a4042778 10.73.240.42#65343: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 05:39:28 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#59923: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 27 05:13:32 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == matrix (4 distinct, 5 total) == Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369032, but reception only permitted for main PID 720 Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369037, but reception only permitted for main PID 720 Sep 27 05:06:38 matrix networkctl[369050]: Interface "vethd12c30e" not found. Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369050, but reception only permitted for main PID 720 [x2] == munin (2 distinct, 8 total) == Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 27 05:13:03 newhonors2 dhcpcd[3216409]: dhcpcd is not running [x24] == ntop00 (57 distinct, 118726 total) == Sep 27 05:05:34 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 ] [x56628] Sep 27 05:05:34 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 ] [x53947] Sep 27 05:05:34 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 ] [x235] Sep 27 05:05:34 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 ] [x235] Sep 27 05:05:34 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 ] [x7609] Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) *** Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 4961/4961, ET: 0) *** Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) *** Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 52/52, ET: 0) *** Sep 27 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 05: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 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) *** Sep 27 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/5226, ET: 0) *** Sep 27 05:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 05: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 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) *** Sep 27 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/51, ET: 0) *** Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) *** Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 4140/4140, ET: 0) *** Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) *** Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 45/45, ET: 0) *** Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) *** Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/4311, ET: 0) *** Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) *** Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/53, ET: 0) *** Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) *** Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 4750/4750, ET: 0) *** Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) *** Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 47/47, ET: 0) *** Sep 27 05:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1100) *** ... 27 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 05:09:09 outbound00.cs.umd.edu python3[145212]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 27 05:08:33 outbound01.cs.umd.edu python3[2405867]: ldapdb [x7] Sep 27 05:09:40 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway. == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: link_config: could not get ethtool features for veth0f0fdb4 Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: Could not set offload features of veth0f0fdb4: No such device Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: link_config: could not get ethtool features for vethfa51150 Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: Could not set offload features of vethfa51150: No such device Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496590]: Could not generate persistent MAC address for vethf636bdb: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496591]: Could not generate persistent MAC address for vetheb21707: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496594]: Could not generate persistent MAC address for veth1135a1b: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496595]: Could not generate persistent MAC address for vethc17d69e: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496619]: Could not generate persistent MAC address for veth1fe5842: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496624]: Could not generate persistent MAC address for veth17bac38: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496698]: Could not generate persistent MAC address for veth9c3f013: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496699]: Could not generate persistent MAC address for veth3b02923: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496702]: Could not generate persistent MAC address for veth725fedd: No such file or directory Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496717]: Could not generate persistent MAC address for veth172a34d: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: link_config: could not get ethtool features for veth725fedd Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: Could not set offload features of veth725fedd: No such device Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506009]: Could not generate persistent MAC address for veth2662a63: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506010]: Could not generate persistent MAC address for vethc9477ab: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506013]: Could not generate persistent MAC address for veth04310dc: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506015]: Could not generate persistent MAC address for veth139f8b7: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506016]: Could not generate persistent MAC address for veth66f235d: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506014]: Could not generate persistent MAC address for veth8ea4b0e: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506061]: Could not generate persistent MAC address for vethb46c07b: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506069]: Could not generate persistent MAC address for vethab533a1: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506115]: Could not generate persistent MAC address for veth63233ea: No such file or directory Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506120]: Could not generate persistent MAC address for veth0b4d3bb: No such file or directory Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515437]: Could not generate persistent MAC address for vethe13f1ff: No such file or directory Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515438]: Could not generate persistent MAC address for veth24f9360: No such file or directory Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515441]: Could not generate persistent MAC address for veth7df4a74: No such file or directory Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515442]: Could not generate persistent MAC address for veth08ee2de: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 05:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 05:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.w2ViRp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.w2ViRp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: 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 == submit26-b9-f4 (10 distinct, 13 total) == Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Wp4Z7D/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Wp4Z7D. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 [x2] Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: 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 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zII8EE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0