Command: /usr/local/sbin/syslog-digest.py Time : 7.5373s Status : exited 0 Output : Syslog digest — 2026-09-26 09:05 EDT Processed 120,405 lines, filtered 1,502 (1%). 118,903 unknown (152 distinct) from 19 host(s). == atif01.cs.umd.edu (1 distinct, 1 total) == Sep 26 08:12:12 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 09:01:19 b0b02.cs.umd.edu rustdesk[1278845]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Sep 26 08:13:20 cheezit.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. == emaar (2 distinct, 2 total) == Sep 26 08:33:39 emaar systemd[1]: insights-client.service: Start request repeated too quickly. Sep 26 08:43:21 emaar puppet-agent[2349309]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found == galax (1 distinct, 1 total) == Sep 26 08:41:12 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND == hackerman (1 distinct, 1 total) == Sep 26 08:53:14 hackerman systemd[1]: insights-client.service: Start request repeated too quickly. == idm00 (1 distinct, 1 total) == Sep 26 08:54:09 idm00 named[4166701]: client @0x7f11a0064678 10.73.240.42#50815: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 08:39:29 idmp0 named[1598691]: client @0x7f2d20000cc8 10.73.240.43#49219: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 26 08:13:35 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == mirrors.cs.umd.edu (1 distinct, 1 total) == Sep 26 08:37:00 mirrors.cs.umd.edu puppet-agent[28683]: (Facter) Error while resolving custom fact fact='ipa', resolution='<anonymous>': Failed while executing '/usr/bin/kinit -k 2>&1': Timeout encounter after 10s, killing process with pid: 28889 == munin (2 distinct, 6 total) == Sep 26 09:03:18 munin sudo[3856750]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3] Sep 26 09:03:18 munin sudo[3856750]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3] == newhonors2 (1 distinct, 24 total) == Sep 26 08:13:03 newhonors2 dhcpcd[3177144]: dhcpcd is not running [x24] == ntop00 (81 distinct, 118757 total) == Sep 26 08:06:56 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 ] [x56616] Sep 26 08:06:56 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 ] [x53824] Sep 26 08:06:56 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 ] [x225] Sep 26 08:06:56 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 ] [x225] Sep 26 08:06:56 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 ] [x7771] Sep 26 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 587) *** Sep 26 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 587, QN: 51/51, ET: 0) *** Sep 26 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 587) *** Sep 26 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 587, QN: 4991/4991, ET: 0) *** Sep 26 08:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 08: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 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 588) *** Sep 26 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 588, QN: 0/4826, ET: 0) *** Sep 26 08:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 08: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 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 588) *** Sep 26 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 588, QN: 0/58, ET: 0) *** Sep 26 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 589) *** Sep 26 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 589, QN: 5791/5791, ET: 0) *** Sep 26 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 589) *** Sep 26 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 589, QN: 79/79, ET: 0) *** Sep 26 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 591) *** Sep 26 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 591, QN: 6617/6617, ET: 0) *** Sep 26 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 591) *** Sep 26 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 591, QN: 64/64, ET: 0) *** Sep 26 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 592) *** Sep 26 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 592, QN: 0/5718, ET: 0) *** Sep 26 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 592) *** Sep 26 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 592, QN: 0/72, ET: 0) *** Sep 26 08:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 593) *** ... 51 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 08:09:09 outbound00.cs.umd.edu python3[4043264]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 08:13:06 outbound01.cs.umd.edu python3[2109905]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091290]: link_config: could not get ethtool features for vethab4601f Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091290]: Could not set offload features of vethab4601f: No such device Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091371]: Could not generate persistent MAC address for vethadd9d06: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091372]: Could not generate persistent MAC address for veth6ba18e8: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091375]: Could not generate persistent MAC address for vethc4af472: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091376]: Could not generate persistent MAC address for veth81ffb0f: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091397]: Could not generate persistent MAC address for veth8130069: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091382]: Could not generate persistent MAC address for vethd29d497: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091384]: Could not generate persistent MAC address for veth627dd69: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091382]: Could not generate persistent MAC address for veth5d22473: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091371]: Could not generate persistent MAC address for vethf352ffa: No such file or directory Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091372]: Could not generate persistent MAC address for veth77fbdc1: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100573]: link_config: could not get ethtool features for veth627dd69 Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100573]: Could not set offload features of veth627dd69: No such device Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100602]: Could not generate persistent MAC address for vethbd37076: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth69d9ab3: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100606]: Could not generate persistent MAC address for veth4ae9683: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100607]: Could not generate persistent MAC address for veth0f46268: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100624]: Could not generate persistent MAC address for veth73fb4f4: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100617]: Could not generate persistent MAC address for vethc8b15db: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100612]: Could not generate persistent MAC address for veth97e2d71: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth3fe9cd4: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100621]: Could not generate persistent MAC address for vetha7af021: No such file or directory Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth791d9cf: No such file or directory Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111682]: link_config: could not get ethtool features for veth791d9cf Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111682]: Could not set offload features of veth791d9cf: No such device Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111708]: link_config: could not get ethtool features for vethbd37076 Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111708]: Could not set offload features of vethbd37076: No such device Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111798]: Could not generate persistent MAC address for vetha12c4b5: No such file or directory Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111799]: Could not generate persistent MAC address for veth15d6a72: No such file or directory ... 8 more distinct messages not shown == smokeping-slave (1 distinct, 1 total) == Sep 26 08:58:16 smokeping-slave nologin[2674829]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN == strawberry (7 distinct, 38 total) == Sep 26 08: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 08: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 08:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 08: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 08: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 08:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 08:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-fclone (9 distinct, 12 total) == Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 [x2] Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aPW1vd/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc [x2] Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 [x2] Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aPW1vd. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4