Command: /usr/local/sbin/syslog-digest.py Time : 7.4429s Status : exited 0 Output : Syslog digest — 2026-09-26 22:05 EDT Processed 118,790 lines, filtered 1,429 (1%). 117,361 unknown (154 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 22:02:05 b0b02.cs.umd.edu rustdesk[1476984]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 26 21:54:08 idm00 named[4166701]: client @0x7f11a9464788 10.73.240.42#51606: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 21:39:28 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#65192: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 26 21:18:25 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 12 total) == Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 26 21:13:18 munin sudo[4121178]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 26 21:13:02 newhonors2 dhcpcd[3201272]: dhcpcd is not running [x24] == ntop00 (79 distinct, 117210 total) == Sep 26 21:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 21:05: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 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 898) *** Sep 26 21:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 898, QN: 0/73, ET: 0) *** Sep 26 21: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 ] [x55882] Sep 26 21: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 ] [x52984] Sep 26 21: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 ] [x234] Sep 26 21: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 ] [x234] Sep 26 21: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 ] [x7784] Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 899) *** Sep 26 21:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 5328/5328, ET: 0) *** Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 899) *** Sep 26 21:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 899, QN: 68/68, ET: 0) *** Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 901) *** Sep 26 21:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 4647/4647, ET: 0) *** Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 901) *** Sep 26 21:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 901, QN: 45/45, ET: 0) *** Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x5] Sep 26 21:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x5] Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) *** Sep 26 21:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/5272, ET: 0) *** Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 902) *** Sep 26 21:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 902, QN: 0/44, ET: 0) *** Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 903) *** Sep 26 21:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 5500/5500, ET: 0) *** Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 903) *** Sep 26 21:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 903, QN: 58/58, ET: 0) *** Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 905) *** Sep 26 21:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 905, QN: 5631/5631, ET: 0) *** Sep 26 21:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 905) *** ... 49 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 21:09:08 outbound00.cs.umd.edu python3[31513]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 21:13:06 outbound01.cs.umd.edu python3[2293657]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 26 21:09:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: link_config: could not get ethtool features for vetha3ad32c Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268804]: Could not set offload features of vetha3ad32c: No such device Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268875]: Could not generate persistent MAC address for veth10b8e87: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268876]: Could not generate persistent MAC address for vethb3a8ff2: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268894]: Could not generate persistent MAC address for veth2ee57b4: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268888]: Could not generate persistent MAC address for veth6daa879: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268903]: Could not generate persistent MAC address for vethe5e086b: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268904]: Could not generate persistent MAC address for vethedb7e54: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268929]: Could not generate persistent MAC address for veth4b684fc: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268930]: Could not generate persistent MAC address for veth2056814: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268955]: Could not generate persistent MAC address for veth3167755: No such file or directory Sep 26 21:20:35 sentry-docker00.cs.umd.edu systemd-udevd[268956]: Could not generate persistent MAC address for veth12bad31: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: link_config: could not get ethtool features for veth2ee57b4 Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278574]: Could not set offload features of veth2ee57b4: No such device Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278608]: Could not generate persistent MAC address for veth3433dfc: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for vethc6b2c20: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278612]: Could not generate persistent MAC address for veth79afbe4: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278613]: Could not generate persistent MAC address for veth85a9632: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278624]: Could not generate persistent MAC address for veth82497ff: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278609]: Could not generate persistent MAC address for veth9dfd391: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278638]: Could not generate persistent MAC address for vethfdb77e7: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278639]: Could not generate persistent MAC address for veth57a07e2: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278657]: Could not generate persistent MAC address for veth7935464: No such file or directory Sep 26 21:40:44 sentry-docker00.cs.umd.edu systemd-udevd[278651]: Could not generate persistent MAC address for veth0174e24: No such file or directory Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: link_config: could not get ethtool features for veth3433dfc Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288198]: Could not set offload features of veth3433dfc: No such device Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288252]: Could not generate persistent MAC address for veth2e641b5: No such file or directory Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288253]: Could not generate persistent MAC address for veth054e8bc: No such file or directory Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288256]: Could not generate persistent MAC address for veth2e1202a: No such file or directory Sep 26 22:00:52 sentry-docker00.cs.umd.edu systemd-udevd[288257]: Could not generate persistent MAC address for veth67b719d: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 21: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 21: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 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 21: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 21: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 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 10 total) == Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.bCbZti/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.bCbZti. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 26 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 21:06:45 submit26-b9-f3 setroubleshoot[3597515]: 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 26 21:10:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (10 distinct, 10 total) == Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ORXJ1O/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 26 21:24:48 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ORXJ1O. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 26 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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 21:24:49 submit26-b9-f4 setroubleshoot[2633888]: 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 26 21:30:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == wraith (2 distinct, 2 total) == Sep 26 21:48:47 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND Sep 26 21:50:22 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND