Command: /usr/local/sbin/syslog-digest.py Time : 7.5328s Status : exited 0 Output : Syslog digest — 2026-09-27 03:05 EDT Processed 119,686 lines, filtered 1,760 (1%). 117,926 unknown (150 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 03:02:27 b0b02.cs.umd.edu rustdesk[1554010]: cannot open display: == biggulp.cs.umd.edu (1 distinct, 4 total) == Sep 27 02:15:31 biggulp.cs.umd.edu sshd-session[360004]: error: send_error: write: Connection reset by peer [x4] == galax (1 distinct, 1 total) == Sep 27 02:12:30 galax kernel: rtw89_8922ae 0000:06:00.0: failed to wait RF DACK == idm00 (1 distinct, 1 total) == Sep 27 02:54:09 idm00 named[4166701]: client @0x7f11a0045838 10.73.240.42#52169: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 02:39:28 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#60745: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 27 02:08:30 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 56 total) == Sep 27 02:23:26 munin sudo[40621]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x28] Sep 27 02:23:26 munin sudo[40621]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x28] == newhonors2 (1 distinct, 24 total) == Sep 27 02:13:03 newhonors2 dhcpcd[3210869]: dhcpcd is not running [x24] == ntop00 (77 distinct, 117729 total) == Sep 27 02:05:09 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 ] [x56135] Sep 27 02:05:09 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 ] [x53199] Sep 27 02:05:09 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 ] [x235] Sep 27 02:05:09 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 ] [x235] Sep 27 02: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 ] [x7813] Sep 27 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) *** Sep 27 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 4862/4862, ET: 0) *** Sep 27 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1019) *** Sep 27 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1019, QN: 41/41, ET: 0) *** Sep 27 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11] Sep 27 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11] Sep 27 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) *** Sep 27 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 0/5337, ET: 0) *** Sep 27 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11] Sep 27 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x11] Sep 27 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1020) *** Sep 27 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1020, QN: 0/39, ET: 0) *** Sep 27 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) *** Sep 27 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 0/5549, ET: 0) *** Sep 27 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1022) *** Sep 27 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1022, QN: 0/57, ET: 0) *** Sep 27 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) *** Sep 27 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 5175/5175, ET: 0) *** Sep 27 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1023) *** Sep 27 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1023, QN: 57/57, ET: 0) *** Sep 27 02:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) *** Sep 27 02:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 0/4681, ET: 0) *** Sep 27 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1024) *** Sep 27 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1024, QN: 0/50, ET: 0) *** Sep 27 02:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1026) *** ... 47 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 02:09:09 outbound00.cs.umd.edu python3[102401]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 27 02:13:06 outbound01.cs.umd.edu python3[2364735]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 27 03:00:43 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410862]: link_config: could not set ethtool features for veth6583660 Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410862]: Could not set offload features of veth6583660: Operation not permitted Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410894]: Could not generate persistent MAC address for vethf8cc8a8: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410895]: Could not generate persistent MAC address for veth3dc6def: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410898]: Could not generate persistent MAC address for veth5fabf55: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410904]: Could not generate persistent MAC address for vethcc6ff29: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410899]: Could not generate persistent MAC address for veth2835219: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410912]: Could not generate persistent MAC address for veth2191e18: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410918]: Could not generate persistent MAC address for veth8a7fe98: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410909]: Could not generate persistent MAC address for veth9b51b71: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410904]: Could not generate persistent MAC address for veth07df455: No such file or directory Sep 27 02:22:40 sentry-docker00.cs.umd.edu systemd-udevd[410912]: Could not generate persistent MAC address for veth9f817c0: No such file or directory Sep 27 02:42:48 sentry-docker00.cs.umd.edu systemd-udevd[420487]: link_config: could not get ethtool features for veth9b51b71 Sep 27 02:42:48 sentry-docker00.cs.umd.edu systemd-udevd[420487]: Could not set offload features of veth9b51b71: No such device Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420521]: Could not generate persistent MAC address for vethde4e2a5: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420522]: Could not generate persistent MAC address for vethfa8f274: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420525]: Could not generate persistent MAC address for veth8eb902b: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420526]: Could not generate persistent MAC address for veth7cc41f7: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420549]: Could not generate persistent MAC address for vethc2b118f: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420550]: Could not generate persistent MAC address for vethecec1ef: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420553]: Could not generate persistent MAC address for vethe873d9c: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420554]: Could not generate persistent MAC address for veth4d37c6e: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420577]: Could not generate persistent MAC address for veth49bb0f5: No such file or directory Sep 27 02:42:49 sentry-docker00.cs.umd.edu systemd-udevd[420578]: Could not generate persistent MAC address for veth376191f: No such file or directory Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430291]: link_config: could not get ethtool features for vethc2b118f Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430291]: Could not set offload features of vethc2b118f: No such device Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430321]: Could not generate persistent MAC address for vethd8a4158: No such file or directory Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430322]: Could not generate persistent MAC address for veth0d1a7c8: No such file or directory Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430347]: Could not generate persistent MAC address for veth9821412: No such file or directory Sep 27 03:02:57 sentry-docker00.cs.umd.edu systemd-udevd[430348]: Could not generate persistent MAC address for vethfa6ce8e: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.1CRSEU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.1CRSEU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 Sep 27 02:25:57 submit26-b9-f1 setroubleshoot[3881007]: 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 == submit26-b9-f2 (9 distinct, 9 total) == Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tLOEBD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tLOEBD. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 27 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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 02:06:51 submit26-b9-f2 setroubleshoot[2946807]: 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