Command: /usr/local/sbin/syslog-digest.py Time : 2.9098s Status : exited 0 Output : Syslog digest — 2026-09-26 03:05 EDT Processed 47,405 lines, filtered 1,692 (3%). 45,713 unknown (176 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 03:00:57 b0b02.cs.umd.edu rustdesk[1186180]: cannot open display: == galax (1 distinct, 1 total) == Sep 26 02:31:54 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Sep 26 02:54:08 idm00 named[4166701]: client @0x7f11980727c8 10.73.240.42#59670: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 02:39:29 idmp0 named[1598691]: client @0x7f2d1401bb98 10.73.240.43#64599: update '73.10.in-addr.arpa/IN' denied == irb2156 (1 distinct, 1 total) == Sep 26 02:34:13 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 128.8.74.3. == itmon02 (1 distinct, 5 total) == Sep 26 02:07:57 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5] == munin (2 distinct, 38 total) == Sep 26 02:08:12 munin sudo[3706132]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x19] Sep 26 02:08:12 munin sudo[3706132]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x19] == newhonors2 (1 distinct, 24 total) == Sep 26 02:13:03 newhonors2 dhcpcd[3164870]: dhcpcd is not running [x24] == ntop00 (104 distinct, 45535 total) == Sep 26 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 ] [x21651] Sep 26 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 ] [x20424] Sep 26 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 ] [x3298] Sep 26 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 26 02:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 4554/4554, ET: 0) *** Sep 26 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 26 02:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 59/59, ET: 0) *** Sep 26 02:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12] Sep 26 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) [x12] Sep 26 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 26 02:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 0/5189, ET: 0) *** Sep 26 02:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12] Sep 26 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) [x12] Sep 26 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 26 02:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 0/52, ET: 0) *** Sep 26 02:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 26 02:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 5354/5354, ET: 0) *** Sep 26 02:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 26 02:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 58/58, ET: 0) *** Sep 26 02:14:03 ntop00 rsyslogd[1208]: action 'action-1-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 26 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 26 02:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 0/5086, ET: 0) *** Sep 26 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 26 02:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 0/73, ET: 0) *** Sep 26 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 26 02:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4873/4873, ET: 0) *** Sep 26 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 26 02:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 67/67, ET: 0) *** Sep 26 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 26 02:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 0/54, ET: 0) *** ... 74 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 02:09:09 outbound00.cs.umd.edu python3[3957606]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 02:13:06 outbound01.cs.umd.edu python3[2023905]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920662]: link_config: could not get ethtool features for veth6c50115 Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920662]: Could not set offload features of veth6c50115: No such device Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920697]: Could not generate persistent MAC address for veth9e9f52d: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920698]: Could not generate persistent MAC address for veth61c0f81: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920701]: Could not generate persistent MAC address for veth52a02d3: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920702]: Could not generate persistent MAC address for vethcad0d9b: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920725]: Could not generate persistent MAC address for vethb67f011: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920726]: Could not generate persistent MAC address for vethe91ce33: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920744]: Could not generate persistent MAC address for veth142a5d8: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920751]: Could not generate persistent MAC address for vethb511de4: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920765]: Could not generate persistent MAC address for veth06f110b: No such file or directory Sep 26 02:12:41 sentry-docker00.cs.umd.edu systemd-udevd[3920766]: Could not generate persistent MAC address for vethfae43f4: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930139]: link_config: could not set ethtool features for vethb67f011 Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930139]: Could not set offload features of vethb67f011: Operation not permitted Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930163]: Could not generate persistent MAC address for veth00fe2b0: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930164]: Could not generate persistent MAC address for veth435a2bb: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930182]: Could not generate persistent MAC address for veth1caa67a: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930167]: Could not generate persistent MAC address for vethdbb67e1: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930178]: Could not generate persistent MAC address for veth39aaf74: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930177]: Could not generate persistent MAC address for veth3c143de: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930178]: Could not generate persistent MAC address for veth5fdfdf4: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930173]: Could not generate persistent MAC address for vethfe63d84: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930225]: Could not generate persistent MAC address for vethd1b5418: No such file or directory Sep 26 02:32:49 sentry-docker00.cs.umd.edu systemd-udevd[3930235]: Could not generate persistent MAC address for veth90adfcb: No such file or directory Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939957]: link_config: could not get ethtool features for veth1caa67a Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939957]: Could not set offload features of veth1caa67a: No such device Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939993]: Could not generate persistent MAC address for veth6d96a7a: No such file or directory Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939994]: Could not generate persistent MAC address for vethd4dd658: No such file or directory Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939997]: Could not generate persistent MAC address for veth1aecd51: No such file or directory Sep 26 02:52:58 sentry-docker00.cs.umd.edu systemd-udevd[3939998]: Could not generate persistent MAC address for veth67b1fae: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 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 26 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 26 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 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 26 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 26 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 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 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vHW4zr/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:56 submit26-b9-f1 setroubleshoot[3741822]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vHW4zr. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 26 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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 26 02:25:57 submit26-b9-f1 setroubleshoot[3741822]: 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, 11 total) == Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 [x2] Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 [x2] Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GVkKZa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GVkKZa. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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 26 02:06:51 submit26-b9-f2 setroubleshoot[2820289]: 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