Command: /usr/local/sbin/syslog-digest.py Time : 7.4814s Status : exited 0 Output : Syslog digest — 2026-09-26 21:05 EDT Processed 119,536 lines, filtered 1,708 (1%). 117,828 unknown (141 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 21:02:01 b0b02.cs.umd.edu rustdesk[1461804]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 3 total) == Sep 26 21:02:58 cheezit.cs.umd.edu sshd-session[3469736]: error: PAM: Authentication failure for adamnguy from 10.174.62.191 [x3] == galax (1 distinct, 1 total) == Sep 26 20:59:49 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 8195 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Sep 26 20:54:08 idm00 named[4166701]: client @0x7f119807baf8 10.73.240.42#50435: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 20:39:28 idmp0 named[1598691]: client @0x7f2d280332b8 10.73.240.43#51139: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 26 20:08:21 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 4 total) == Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 26 20:23:19 munin sudo[4102400]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 26 20:13:03 newhonors2 dhcpcd[3199432]: dhcpcd is not running [x24] == ntop00 (81 distinct, 117697 total) == Sep 26 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 20: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 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 874) *** Sep 26 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 874, QN: 0/61, ET: 0) *** Sep 26 20: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 ] [x56110] Sep 26 20: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 ] [x53328] Sep 26 20: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 ] [x237] Sep 26 20: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 ] [x237] Sep 26 20:05:09 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 ] [x7689] Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 875) *** Sep 26 20:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 7964/7964, ET: 0) *** Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 875) *** Sep 26 20:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 875, QN: 61/61, ET: 0) *** Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 877) *** Sep 26 20:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 65/65, ET: 0) *** Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 877) *** Sep 26 20:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 877, QN: 8920/8920, ET: 0) *** Sep 26 20:15:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 26 20:15: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 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) *** Sep 26 20:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/9655, ET: 0) *** Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 878) *** Sep 26 20:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 878, QN: 0/59, ET: 0) *** Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 879) *** Sep 26 20:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 9156/9156, ET: 0) *** Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 879) *** Sep 26 20:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 879, QN: 57/57, ET: 0) *** Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 881) *** Sep 26 20:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 881, QN: 9975/9975, ET: 0) *** Sep 26 20:23:02 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 881) *** ... 51 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 20:09:09 outbound00.cs.umd.edu python3[17585]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 20:13:06 outbound01.cs.umd.edu python3[2279605]: ldapdb [x6] == sentry-docker00.cs.umd.edu (32 distinct, 32 total) == Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240674]: Could not generate persistent MAC address for veth0cb3890: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240675]: Could not generate persistent MAC address for veth3c2d252: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240678]: Could not generate persistent MAC address for veth3c2a590: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240690]: Could not generate persistent MAC address for vethcd3686e: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240698]: Could not generate persistent MAC address for vethdbd59d4: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240687]: Could not generate persistent MAC address for veth13de5de: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240706]: Could not generate persistent MAC address for veth8ade4f6: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240707]: Could not generate persistent MAC address for veth9bd96c7: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240718]: Could not generate persistent MAC address for veth38522ca: No such file or directory Sep 26 20:20:10 sentry-docker00.cs.umd.edu systemd-udevd[240722]: Could not generate persistent MAC address for veth5ef6cbb: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: link_config: could not get ethtool features for veth0cb3890 Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[249991]: Could not set offload features of veth0cb3890: No such device Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250071]: Could not generate persistent MAC address for veth4b44127: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250072]: Could not generate persistent MAC address for veth93ed0c0: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250075]: Could not generate persistent MAC address for veth96a6062: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250089]: Could not generate persistent MAC address for vethe1f95bc: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250099]: Could not generate persistent MAC address for veth82dd944: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250100]: Could not generate persistent MAC address for veth48266a2: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250118]: Could not generate persistent MAC address for vethe005dc8: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250116]: Could not generate persistent MAC address for veth6039b8b: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250171]: Could not generate persistent MAC address for veth7bf394a: No such file or directory Sep 26 20:40:19 sentry-docker00.cs.umd.edu systemd-udevd[250173]: Could not generate persistent MAC address for veth019b195: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259751]: Could not generate persistent MAC address for veth55cccb1: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259752]: Could not generate persistent MAC address for veth650c18d: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259755]: Could not generate persistent MAC address for vethd85018c: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259756]: Could not generate persistent MAC address for vethd726dcb: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259762]: Could not generate persistent MAC address for vethf0e3b71: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth4f93a12: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259776]: Could not generate persistent MAC address for veth3eaba64: No such file or directory Sep 26 21:00:27 sentry-docker00.cs.umd.edu systemd-udevd[259760]: Could not generate persistent MAC address for vethfa12872: No such file or directory ... 2 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 20: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 20: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 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 20: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 20: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 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f4 (1 distinct, 1 total) == Sep 26 20:48:59 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-fclone (9 distinct, 10 total) == Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 [x2] Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3PkJow/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3PkJow. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 26 20:22:01 submit26-b9-fclone setroubleshoot[548203]: 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 20:22:02 submit26-b9-fclone setroubleshoot[548203]: 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 20:22:02 submit26-b9-fclone setroubleshoot[548203]: 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