Command: /usr/local/sbin/syslog-digest.py Time : 0.6568s Status : exited 0 Output : Syslog digest — 2026-09-27 21:05 EDT Processed 11,433 lines, filtered 1,425 (12%). 10,008 unknown (168 distinct) from 14 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 21:03:32 b0b02.cs.umd.edu rustdesk[1829556]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 27 20:54:09 idm00 named[4166701]: client @0x7f119854a418 10.73.240.42#52124: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 20:39:28 idmp0 named[1598691]: client @0x7f2d3c082968 10.73.240.43#62378: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 27 20:18:52 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 50 total) == Sep 27 20:08:32 munin sudo[427067]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x25] Sep 27 20:08:32 munin sudo[427067]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x25] == newhonors2 (1 distinct, 24 total) == Sep 27 20:13:03 newhonors2 dhcpcd[3244895]: dhcpcd is not running [x24] == ntop00 (97 distinct, 9816 total) == Sep 27 20:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. Sep 27 20:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) Sep 27 20:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1450) *** Sep 27 20:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1450, QN: 0/7168, ET: 0) *** Sep 27 20:05:01 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 ] [x4610] Sep 27 20:05:01 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 ] [x4393] Sep 27 20:05:01 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 ] [x649] Sep 27 20:05:01 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 ] [x18] Sep 27 20:05:01 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 ] [x18] Sep 27 20:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. Sep 27 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) Sep 27 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1450) *** Sep 27 20:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1450, QN: 0/62, ET: 0) *** Sep 27 20:07:05 ntop00 rsyslogd[1208]: file '/var/log/secure'[17] 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 ] [x19] Sep 27 20:07:05 ntop00 rsyslogd[1208]: action 'action-4-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 ] [x19] Sep 27 20:14:46 ntop00 pmacct-mariadb[775683]: 2026-09-28 0:14:46 4 [Warning] Aborted connection 4 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Sep 27 20:14:46 ntop00 pmacct-mariadb[775683]: 2026-09-28 0:14:46 3 [Warning] Aborted connection 3 to db: 'pmacct' user: 'grafana_reader' host: '10.73.246.25' (Got an error reading communication packets) Sep 27 20:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 4) *** Sep 27 20:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 4, QN: 3/3, ET: 0) *** Sep 27 20:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 4) *** Sep 27 20:15:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 5) *** Sep 27 20:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 4, QN: 3585/3585, ET: 0) *** Sep 27 20:15:09 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 5, QN: 3585/3585, ET: 8) *** Sep 27 20:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 5) *** Sep 27 20:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 5, QN: 10/10, ET: 0) *** Sep 27 20:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 6) *** Sep 27 20:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 6, QN: 30/30, ET: 0) *** Sep 27 20:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 6) *** Sep 27 20:20:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 7) *** Sep 27 20:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 6, QN: 4168/4168, ET: 0) *** ... 67 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 20:09:09 outbound00.cs.umd.edu python3[356756]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 27 20:13:06 outbound01.cs.umd.edu python3[2622771]: ldapdb [x6] == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914360]: link_config: could not get ethtool features for veth0342bc4 Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914360]: Could not set offload features of veth0342bc4: No such device Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914456]: Could not generate persistent MAC address for vethd7cffbf: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914457]: Could not generate persistent MAC address for veth18e940f: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914460]: Could not generate persistent MAC address for veth883b790: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914461]: Could not generate persistent MAC address for veth4e86b36: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914485]: Could not generate persistent MAC address for veth0a6feb7: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914484]: Could not generate persistent MAC address for vethd0597fc: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914490]: Could not generate persistent MAC address for veth5d5fc60: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914488]: Could not generate persistent MAC address for veth843fce9: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914606]: Could not generate persistent MAC address for vethd609738: No such file or directory Sep 27 20:10:01 sentry-docker00.cs.umd.edu systemd-udevd[914605]: Could not generate persistent MAC address for veth493d3d4: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923757]: link_config: could not get ethtool features for veth493d3d4 Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923757]: Could not set offload features of veth493d3d4: No such device Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923852]: link_config: could not get ethtool features for veth883b790 Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923852]: Could not set offload features of veth883b790: No such device Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923881]: Could not generate persistent MAC address for vethb5b89ba: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923882]: Could not generate persistent MAC address for vethfc1fbad: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923889]: Could not generate persistent MAC address for veth928ab7b: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923896]: Could not generate persistent MAC address for vethe104ec6: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923889]: Could not generate persistent MAC address for vetha08dd13: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923896]: Could not generate persistent MAC address for vethddacb75: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923915]: Could not generate persistent MAC address for veth006b297: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923916]: Could not generate persistent MAC address for veth090dc9a: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923962]: Could not generate persistent MAC address for veth1b551cf: No such file or directory Sep 27 20:30:09 sentry-docker00.cs.umd.edu systemd-udevd[923966]: Could not generate persistent MAC address for veth2e03182: No such file or directory Sep 27 20:50:18 sentry-docker00.cs.umd.edu systemd-udevd[933484]: link_config: could not get ethtool features for vethb5b89ba Sep 27 20:50:18 sentry-docker00.cs.umd.edu systemd-udevd[933484]: Could not set offload features of vethb5b89ba: No such device Sep 27 20:50:18 sentry-docker00.cs.umd.edu systemd-udevd[933488]: link_config: could not get ethtool features for veth006b297 Sep 27 20:50:18 sentry-docker00.cs.umd.edu systemd-udevd[933488]: Could not set offload features of veth006b297: No such device ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 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 27 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 27 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 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 27 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 27 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-fclone (9 distinct, 9 total) == Sep 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.3ALxw1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.3ALxw1. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 27 20:22:01 submit26-b9-fclone setroubleshoot[606580]: 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 == test-ipv6 (5 distinct, 13 total) == Sep 27 20:47:57 test-ipv6 sshd-session[4118161]: error: Certificate does not contain an authorized principal [x8] Sep 27 20:48:30 test-ipv6 krb5_child[4118455]: Preauthentication failed Sep 27 20:48:40 test-ipv6 oddjob-mkhomedir[4118459]: error creating /fs/junkfood/seriv: Permission denied [x2] Sep 27 20:49:20 test-ipv6 sshd-session[4118485]: error: maximum authentication attempts exceeded for seriv from 10.73.255.10 port 54838 ssh2 [preauth] Sep 27 20:54:25 test-ipv6 sshd-session[4119073]: error: maximum authentication attempts exceeded for seriv from 10.73.255.10 port 52080 ssh2 [preauth] == tma-0 (1 distinct, 1 total) == Sep 27 20:13:12 tma-0 sshd[8709]: fatal: ssh_packet_get_string: incomplete message [preauth]