Command: /usr/local/sbin/syslog-digest.py Time : 7.5015s Status : exited 0 Output : Syslog digest — 2026-09-26 06:05 EDT Processed 120,092 lines, filtered 1,728 (1%). 118,364 unknown (154 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 06:01:06 b0b02.cs.umd.edu rustdesk[1232075]: cannot open display: == grades01.cs.umd.edu (1 distinct, 1 total) == Sep 26 05:48:19 grades01.cs.umd.edu puppet-agent[10880]: 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 26 05:54:08 idm00 named[4166701]: client @0x7f11a00218e8 10.73.240.42#49530: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 05:39:29 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#49306: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 26 05:18:45 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == matrix (12 distinct, 14 total) == Sep 26 05:27:46 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3742988, but reception only permitted for main PID 720 Sep 26 05:27:46 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3742992, but reception only permitted for main PID 720 Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743101, but reception only permitted for main PID 720 Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743105, but reception only permitted for main PID 720 Sep 26 05:27:54 matrix networkctl[3743118]: Interface "veth78752a8" not found. Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743118, but reception only permitted for main PID 720 [x2] Sep 26 05:27:55 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743197, but reception only permitted for main PID 720 Sep 26 05:27:55 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743210, but reception only permitted for main PID 720 Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745974, but reception only permitted for main PID 720 Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745980, but reception only permitted for main PID 720 Sep 26 05:31:24 matrix networkctl[3745993]: Interface "vethdc4eeee" not found. Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745993, but reception only permitted for main PID 720 [x2] == munin (2 distinct, 8 total) == Sep 26 05:18:49 munin sudo[3775227]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 26 05:18:49 munin sudo[3775227]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 26 05:13:03 newhonors2 dhcpcd[3171022]: dhcpcd is not running [x24] == ntop00 (70 distinct, 118204 total) == Sep 26 05:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10] Sep 26 05:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x10] Sep 26 05:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 514) *** Sep 26 05:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 0/81, ET: 0) *** Sep 26 05:05:02 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 ] [x7858] Sep 26 05:05:02 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 ] [x56329] Sep 26 05:05:02 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 ] [x53486] Sep 26 05:05:15 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 ] [x216] Sep 26 05:05:15 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 ] [x216] Sep 26 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 26 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5088/5088, ET: 0) *** Sep 26 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 515) *** Sep 26 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 60/60, ET: 0) *** Sep 26 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x8] Sep 26 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) [x8] Sep 26 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 26 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 0/5285, ET: 0) *** Sep 26 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) *** Sep 26 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 0/58, ET: 0) *** Sep 26 05:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 26 05:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 0/4905, ET: 0) *** Sep 26 05:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) *** Sep 26 05:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 0/60, ET: 0) *** Sep 26 05:15: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 ] [x3] Sep 26 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 26 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 5882/5882, ET: 0) *** Sep 26 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 519) *** Sep 26 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 70/70, ET: 0) *** Sep 26 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) *** Sep 26 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 0/51, ET: 0) *** ... 40 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 05:09:09 outbound00.cs.umd.edu python3[4000563]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 8 total) == Sep 26 05:08:33 outbound01.cs.umd.edu python3[2065100]: ldapdb [x7] Sep 26 05:09:42 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 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006076]: link_config: could not get ethtool features for veth8572ff8 Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006076]: Could not set offload features of veth8572ff8: No such device Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006100]: Could not generate persistent MAC address for veth85b7b06: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006101]: Could not generate persistent MAC address for vethf96ac07: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethe6b076a: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006139]: Could not generate persistent MAC address for vethfb74621: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006164]: Could not generate persistent MAC address for vethc6750ce: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethfe87997: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethf36c608: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006164]: Could not generate persistent MAC address for veth0bac43c: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006161]: Could not generate persistent MAC address for vethfd91ef0: No such file or directory Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006155]: Could not generate persistent MAC address for veth02f732f: No such file or directory Sep 26 05:34:04 sentry-docker00.cs.umd.edu systemd-udevd[4015734]: link_config: could not get ethtool features for vethc6750ce Sep 26 05:34:04 sentry-docker00.cs.umd.edu systemd-udevd[4015734]: Could not set offload features of vethc6750ce: No such device Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015770]: Could not generate persistent MAC address for vethb6d68df: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015771]: Could not generate persistent MAC address for veth77a0ba2: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015774]: Could not generate persistent MAC address for vethbded419: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015775]: Could not generate persistent MAC address for veth7de582a: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015798]: Could not generate persistent MAC address for vethcf63320: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015799]: Could not generate persistent MAC address for veth8c3e104: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015817]: Could not generate persistent MAC address for veth9716d80: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015824]: Could not generate persistent MAC address for veth6e173b1: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015842]: Could not generate persistent MAC address for vethd88ef8d: No such file or directory Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015845]: Could not generate persistent MAC address for veth5768623: No such file or directory Sep 26 05:54:12 sentry-docker00.cs.umd.edu systemd-udevd[4025194]: link_config: could not get ethtool features for vethb6d68df Sep 26 05:54:12 sentry-docker00.cs.umd.edu systemd-udevd[4025194]: Could not set offload features of vethb6d68df: No such device Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025228]: Could not generate persistent MAC address for vethb268998: No such file or directory Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025229]: Could not generate persistent MAC address for veth95b4a7a: No such file or directory Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025232]: Could not generate persistent MAC address for veth6d2ebc4: No such file or directory Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025233]: Could not generate persistent MAC address for veth3a2568d: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 05: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 05: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 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 05: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 05: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 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Yj2SEV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Yj2SEV. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 (9 distinct, 9 total) == Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.x38Vqy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x38Vqy. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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