Command: /usr/local/sbin/syslog-digest.py Time : 7.5406s Status : exited 0 Output : Syslog digest — 2026-09-27 11:05 EDT Processed 120,386 lines, filtered 1,519 (1%). 118,867 unknown (165 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 11:02:54 b0b02.cs.umd.edu rustdesk[1677118]: cannot open display: == biggulp.cs.umd.edu (7 distinct, 21 total) == Sep 27 10:47:15 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 20 seq 2 [preauth] [x3] Sep 27 10:47:15 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 30 seq 3 [preauth] [x3] Sep 27 10:47:17 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 20 seq 4 [preauth] [x3] Sep 27 10:47:17 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 30 seq 5 [preauth] [x3] Sep 27 10:47:19 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 20 seq 6 [preauth] [x3] Sep 27 10:47:19 biggulp.cs.umd.edu sshd-session[447085]: error: kex_protocol_error: type 30 seq 7 [preauth] [x3] Sep 27 10:48:27 biggulp.cs.umd.edu sshd-session[447193]: error: send_error: write: Connection reset by peer [x3] == cheezit.cs.umd.edu (2 distinct, 4 total) == Sep 27 10:10:03 cheezit.cs.umd.edu sshd-session[3653852]: pam_access(sshd:auth): access denied for user `rztao' from `71.178.33.59' Sep 27 10:12:16 cheezit.cs.umd.edu sshd-session[3654672]: pam_access(sshd:auth): access denied for user `hanshao' from `73.86.176.20' [x3] == grosh (1 distinct, 1 total) == Sep 27 11:00:08 grosh (da-udp.*)[290312]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == idm00 (2 distinct, 3 total) == Sep 27 10:40:58 idm00 named[4166701]: client @0x7f119806c0a8 10.73.245.14#56667: update '73.10.in-addr.arpa/IN' denied [x2] Sep 27 10:54:10 idm00 named[4166701]: client @0x7f11a406bb48 10.73.240.42#64321: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 10:39:27 idmp0 named[1598691]: client @0x7f2d2c045638 10.73.240.43#62113: update '73.10.in-addr.arpa/IN' denied == irb2156 (1 distinct, 1 total) == Sep 27 11:00:31 irb2156 (da-udp.*)[1634877]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == itmon02 (1 distinct, 2 total) == Sep 27 10:13:00 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (1 distinct, 5 total) == Sep 27 10:43:31 krispykreme.cs.umd.edu sshd-session[3203610]: error: send_error: write: Connection reset by peer [x5] == lifepix (1 distinct, 1 total) == Sep 27 11:00:01 lifepix (da-udp.*)[411007]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == munin (2 distinct, 8 total) == Sep 27 10:13:05 munin sudo[211585]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 27 10:13:05 munin sudo[211585]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 27 10:13:03 newhonors2 dhcpcd[3225771]: dhcpcd is not running [x24] == ntop00 (81 distinct, 118688 total) == Sep 27 10:07:40 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 ] [x7690] Sep 27 10:07:40 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 ] [x56605] Sep 27 10:07:40 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 ] [x53819] Sep 27 10:07:40 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 ] [x239] Sep 27 10:07:40 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 ] [x239] Sep 27 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1211) *** Sep 27 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1211) *** Sep 27 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1211, QN: 43/43, ET: 0) *** Sep 27 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1211, QN: 4717/4717, ET: 0) *** Sep 27 10:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 10: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 27 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1212) *** Sep 27 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1212, QN: 0/4700, ET: 0) *** Sep 27 10:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6] Sep 27 10: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 27 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1212) *** Sep 27 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1212, QN: 0/55, ET: 0) *** Sep 27 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1213) *** Sep 27 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1213, QN: 4684/4684, ET: 0) *** Sep 27 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1213) *** Sep 27 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1213, QN: 79/79, ET: 0) *** Sep 27 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1215) *** Sep 27 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1215, QN: 5785/5785, ET: 0) *** Sep 27 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1215) *** Sep 27 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1215, QN: 50/50, ET: 0) *** Sep 27 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1216) *** Sep 27 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1216, QN: 0/5455, ET: 0) *** Sep 27 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1216) *** Sep 27 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1216, QN: 0/51, ET: 0) *** Sep 27 10:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1217) *** ... 51 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 10:09:09 outbound00.cs.umd.edu python3[215896]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 27 10:13:06 outbound01.cs.umd.edu python3[2478768]: ldapdb [x6] == quiss (1 distinct, 1 total) == Sep 27 11:00:12 quiss (da-udp.*)[3283626]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630320]: Could not generate persistent MAC address for vethc487d1c: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630321]: Could not generate persistent MAC address for veth7cc11bf: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630377]: Could not generate persistent MAC address for vethdca1f96: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630378]: Could not generate persistent MAC address for veth59ea910: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630406]: Could not generate persistent MAC address for veth4fc28a0: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630408]: Could not generate persistent MAC address for vethcb05ec0: No such file or directory Sep 27 10:05:51 sentry-docker00.cs.umd.edu systemd-udevd[630417]: Could not generate persistent MAC address for vethcf896c9: No such file or directory Sep 27 10:05:52 sentry-docker00.cs.umd.edu systemd-udevd[630418]: Could not generate persistent MAC address for vethda1651f: No such file or directory Sep 27 10:05:52 sentry-docker00.cs.umd.edu systemd-udevd[630448]: Could not generate persistent MAC address for veth1aaec0c: No such file or directory Sep 27 10:05:52 sentry-docker00.cs.umd.edu systemd-udevd[630449]: Could not generate persistent MAC address for veth3b1be38: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639705]: link_config: could not get ethtool features for vethcf896c9 Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639705]: Could not set offload features of vethcf896c9: No such device Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639740]: Could not generate persistent MAC address for veth642800d: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639741]: Could not generate persistent MAC address for vethc0bab36: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639744]: Could not generate persistent MAC address for veth0dae8d4: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639753]: Could not generate persistent MAC address for vethb31fa96: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639744]: Could not generate persistent MAC address for vethc944734: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639765]: Could not generate persistent MAC address for vethcc68841: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639765]: Could not generate persistent MAC address for vethb945f81: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639764]: Could not generate persistent MAC address for veth831c546: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639744]: Could not generate persistent MAC address for veth2043bd7: No such file or directory Sep 27 10:26:00 sentry-docker00.cs.umd.edu systemd-udevd[639765]: Could not generate persistent MAC address for vethc734381: No such file or directory Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649073]: link_config: could not set ethtool features for vethb945f81 Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649073]: Could not set offload features of vethb945f81: Operation not permitted Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649104]: Could not generate persistent MAC address for vethb2e841e: No such file or directory Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649105]: Could not generate persistent MAC address for veth70d6831: No such file or directory Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649108]: Could not generate persistent MAC address for vethd2f8a42: No such file or directory Sep 27 10:46:08 sentry-docker00.cs.umd.edu systemd-udevd[649109]: Could not generate persistent MAC address for veth924dba5: No such file or directory Sep 27 10:46:09 sentry-docker00.cs.umd.edu systemd-udevd[649132]: Could not generate persistent MAC address for veth68a6667: No such file or directory Sep 27 10:46:09 sentry-docker00.cs.umd.edu systemd-udevd[649133]: Could not generate persistent MAC address for vethd2bcc16: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 10: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 10: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 10:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 10: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 10:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 27 10:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 10:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 13 total) == Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 [x2] Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.6FiZQU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee [x2] Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.6FiZQU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 [x2] Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 Sep 27 10:25:57 submit26-b9-f1 setroubleshoot[3903697]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.twT3SF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d == submit26-b9-f2 (9 distinct, 9 total) == Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.SK9kUe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.SK9kUe. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Sep 27 10:06:51 submit26-b9-f2 setroubleshoot[2972843]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7