Command: /usr/local/sbin/syslog-digest.py Time : 7.4279s Status : exited 0 Output : Syslog digest — 2026-09-26 23:05 EDT Processed 119,024 lines, filtered 1,658 (1%). 117,366 unknown (156 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 23:02:10 b0b02.cs.umd.edu rustdesk[1492210]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 26 22:54:08 idm00 named[4166701]: client @0x7f11a9468268 10.73.240.42#63308: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 22:39:28 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#53231: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 26 22:28:31 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 8 total) == Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 26 22:28:31 munin sudo[4147910]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 26 23:03:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. == newhonors2 (1 distinct, 24 total) == Sep 26 22:13:03 newhonors2 dhcpcd[3203115]: dhcpcd is not running [x24] == ntop00 (77 distinct, 117212 total) == Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7] Sep 26 22:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7] Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) *** Sep 26 22:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/5081, ET: 0) *** Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x7] Sep 26 22:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x7] Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 922) *** Sep 26 22:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 922, QN: 0/54, ET: 0) *** Sep 26 22: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 ] [x55919] Sep 26 22: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 ] [x53141] Sep 26 22: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 ] [x233] Sep 26 22: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 ] [x233] Sep 26 22:05:08 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 ] [x7590] Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 923) *** Sep 26 22:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 4760/4760, ET: 0) *** Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 923) *** Sep 26 22:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 923, QN: 49/49, ET: 0) *** Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 925) *** Sep 26 22:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 5849/5849, ET: 0) *** Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 925) *** Sep 26 22:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 925, QN: 54/54, ET: 0) *** Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) *** Sep 26 22:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/6362, ET: 0) *** Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 926) *** Sep 26 22:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 926, QN: 0/55, ET: 0) *** Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 927) *** Sep 26 22:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 6786/6786, ET: 0) *** Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 927) *** Sep 26 22:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 927, QN: 55/55, ET: 0) *** Sep 26 22:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 929) *** ... 47 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 22:09:09 outbound00.cs.umd.edu python3[45516]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 22:13:06 outbound01.cs.umd.edu python3[2307789]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: link_config: could not get ethtool features for veth2e1202a Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297664]: Could not set offload features of veth2e1202a: No such device Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297721]: Could not generate persistent MAC address for vethe21f61f: No such file or directory Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297722]: Could not generate persistent MAC address for veth58dd69f: No such file or directory Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297725]: Could not generate persistent MAC address for veth1db2bc8: No such file or directory Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297747]: Could not generate persistent MAC address for veth47d75cf: No such file or directory Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297736]: Could not generate persistent MAC address for veth3e16485: No such file or directory Sep 26 22:21:00 sentry-docker00.cs.umd.edu systemd-udevd[297732]: Could not generate persistent MAC address for veth86ad1aa: No such file or directory Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297758]: Could not generate persistent MAC address for veth5b84c0b: No such file or directory Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297760]: Could not generate persistent MAC address for vetha51c2d9: No such file or directory Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297817]: Could not generate persistent MAC address for veth28463b5: No such file or directory Sep 26 22:21:01 sentry-docker00.cs.umd.edu systemd-udevd[297815]: Could not generate persistent MAC address for vethb1df683: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: link_config: could not set ethtool features for vethe21f61f Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307103]: Could not set offload features of vethe21f61f: Operation not permitted Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307128]: Could not generate persistent MAC address for vethf6f7fd9: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307129]: Could not generate persistent MAC address for veth59eb317: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307177]: Could not generate persistent MAC address for vethd8f0375: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307178]: Could not generate persistent MAC address for veth49c13ea: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307184]: Could not generate persistent MAC address for vethf3e8ddc: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307203]: Could not generate persistent MAC address for veth6a8e398: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307204]: Could not generate persistent MAC address for vethf5a7b94: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307196]: Could not generate persistent MAC address for veth7d77425: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307224]: Could not generate persistent MAC address for veth6395a10: No such file or directory Sep 26 22:41:09 sentry-docker00.cs.umd.edu systemd-udevd[307221]: Could not generate persistent MAC address for vethfae786d: No such file or directory Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: link_config: could not get ethtool features for vethf5a7b94 Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316523]: Could not set offload features of vethf5a7b94: No such device Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316563]: Could not generate persistent MAC address for veth65e6ffe: No such file or directory Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316564]: Could not generate persistent MAC address for vethefb9db5: No such file or directory Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316567]: Could not generate persistent MAC address for vethe7ed892: No such file or directory Sep 26 23:01:17 sentry-docker00.cs.umd.edu systemd-udevd[316568]: Could not generate persistent MAC address for veth31c184e: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 22: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 22: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 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 22: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 22: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 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (11 distinct, 15 total) == Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 [x2] Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 [x2] Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EDBZpQ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.EDBZpQ. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 [x2] Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: 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 [x2] Sep 26 22:25:57 submit26-b9-f1 setroubleshoot[3843149]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lGUl89. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 26 22:30:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (10 distinct, 10 total) == Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WApS6Z/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WApS6Z. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 26 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 22:06:51 submit26-b9-f2 setroubleshoot[2912230]: 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 Sep 26 22:50:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f4 (1 distinct, 1 total) == Sep 26 22:09:57 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 26 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[21121]: Process 16701 (driver) of user 33 killed by SIGABRT - dumping core Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Package 'amanda-backup_server' isn't signed with proper key Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701' exited with 1 Sep 26 22:11:58 vacuum.cs.umd.edu abrt-server[21123]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-26-22:11:58-16701'