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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.8511s
Status : exited 0
Output :
Syslog digest — 2026-09-27 10:05 EDT
Processed 120,654 lines, filtered 1,760 (1%). 118,894 unknown (162 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 10:02:50 b0b02.cs.umd.edu rustdesk[1661932]: cannot open display:
== emaar (1 distinct, 1 total) ==
Sep 27 09:52:59 emaar systemd[1]: insights-client.service: Start request repeated too quickly.
== idm00 (1 distinct, 1 total) ==
Sep 27 09:54:10 idm00 named[4166701]: client @0x7f11986d48e8 10.73.240.42#58429: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 09:39:30 idmp0 named[1598691]: client @0x7f2d2c03b838 10.73.240.43#64396: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 27 09:18:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== munin (2 distinct, 4 total) ==
Sep 27 09:43:58 munin sudo[200468]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 27 09:43:58 munin sudo[200468]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 09:13:03 newhonors2 dhcpcd[3223924]: dhcpcd is not running [x24]
== ntop00 (81 distinct, 118730 total) ==
Sep 27 09:07:10 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 ] [x7840]
Sep 27 09:07:10 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 ] [x56622]
Sep 27 09:07:10 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 ] [x53694]
Sep 27 09:07:10 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 09:07:10 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 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) ***
Sep 27 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 52/52, ET: 0) ***
Sep 27 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1187) ***
Sep 27 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1187, QN: 5288/5288, ET: 0) ***
Sep 27 09:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 09: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 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) ***
Sep 27 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 0/5806, ET: 0) ***
Sep 27 09:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 09: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 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1188) ***
Sep 27 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1188, QN: 0/60, ET: 0) ***
Sep 27 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) ***
Sep 27 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 6002/6002, ET: 0) ***
Sep 27 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1189) ***
Sep 27 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1189, QN: 67/67, ET: 0) ***
Sep 27 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) ***
Sep 27 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 4293/4293, ET: 0) ***
Sep 27 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1191) ***
Sep 27 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1191, QN: 42/42, ET: 0) ***
Sep 27 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) ***
Sep 27 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 0/4087, ET: 0) ***
Sep 27 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1192) ***
Sep 27 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1192, QN: 0/44, ET: 0) ***
Sep 27 09:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1193) ***
... 51 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 09:09:09 outbound00.cs.umd.edu python3[201945]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 27 09:13:06 outbound01.cs.umd.edu python3[2464591]: ldapdb [x6]
Sep 27 09:25:17 outbound01.cs.umd.edu krb5_child[2468008]: Preauthentication failed
== quiss (5 distinct, 7 total) ==
Sep 27 09:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show
Sep 27 09:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding
Sep 27 09:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding
Sep 27 09:08:42 quiss packagekitd[3265207]: Failed to get cache filename for perl [x2]
Sep 27 09:08:42 quiss packagekitd[3265207]: Failed to get cache filename for kernel [x2]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 09:05:26 sentry-docker00.cs.umd.edu systemd-udevd[601611]: link_config: could not get ethtool features for vethbb781f0
Sep 27 09:05:26 sentry-docker00.cs.umd.edu systemd-udevd[601611]: Could not set offload features of vethbb781f0: No such device
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601648]: Could not generate persistent MAC address for veth601fe69: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601649]: Could not generate persistent MAC address for veth603e3e0: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601652]: Could not generate persistent MAC address for veth7107c62: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601653]: Could not generate persistent MAC address for vethc088c49: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601676]: Could not generate persistent MAC address for veth8016fbe: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601677]: Could not generate persistent MAC address for vethcd5ceae: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601690]: Could not generate persistent MAC address for vethc6117c8: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601695]: Could not generate persistent MAC address for veth60d9987: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601691]: Could not generate persistent MAC address for veth9bc5fb5: No such file or directory
Sep 27 09:05:27 sentry-docker00.cs.umd.edu systemd-udevd[601690]: Could not generate persistent MAC address for vethaf55200: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611403]: link_config: could not get ethtool features for veth7107c62
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611403]: Could not set offload features of veth7107c62: No such device
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611456]: link_config: could not get ethtool features for veth9bc5fb5
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611456]: Could not set offload features of veth9bc5fb5: No such device
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611496]: Could not generate persistent MAC address for vethbdde582: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611497]: Could not generate persistent MAC address for veth1bc7ba4: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611500]: Could not generate persistent MAC address for veth65b7708: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611501]: Could not generate persistent MAC address for veth7242ed0: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611500]: Could not generate persistent MAC address for veth569069a: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611513]: Could not generate persistent MAC address for veth102a333: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611511]: Could not generate persistent MAC address for vetha7c935d: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611517]: Could not generate persistent MAC address for veth2c8bb88: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611513]: Could not generate persistent MAC address for veth159f3d6: No such file or directory
Sep 27 09:25:35 sentry-docker00.cs.umd.edu systemd-udevd[611511]: Could not generate persistent MAC address for veth6ec8721: No such file or directory
Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620918]: Could not generate persistent MAC address for vethb54fcd4: No such file or directory
Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620919]: Could not generate persistent MAC address for vethb879ea0: No such file or directory
Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620919]: Could not generate persistent MAC address for veth604cd3e: No such file or directory
Sep 27 09:45:43 sentry-docker00.cs.umd.edu systemd-udevd[620941]: Could not generate persistent MAC address for veth3217ff3: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 09: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 09: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 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 09: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 09: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 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (1 distinct, 2 total) ==
Sep 27 09:08:08 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 27 09:12:09 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (10 distinct, 16 total) ==
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b [x2]
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 [x2]
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.M9veDD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.M9veDD. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 27 09:06:45 submit26-b9-f3 setroubleshoot[3680963]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
Sep 27 09:10:05 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
== submit26-b9-f4 (10 distinct, 16 total) ==
Sep 27 09:08:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x4]
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2]
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.PIMVJA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2]
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2]
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.PIMVJA. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 27 09:24:50 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74
Sep 27 09:24:51 submit26-b9-f4 setroubleshoot[2694081]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5316s
Status : exited 0
Output :
Syslog digest — 2026-09-27 09:05 EDT
Processed 120,971 lines, filtered 2,064 (1%). 118,907 unknown (156 distinct) from 22 host(s).
== atif01.cs.umd.edu (4 distinct, 4 total) ==
Sep 27 08:07:02 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed
Sep 27 08:07:21 atif01.cs.umd.edu kernel: net_ratelimit: 10 callbacks suppressed
Sep 27 08:48:54 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed
Sep 27 08:48:55 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)!
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 09:02:46 b0b02.cs.umd.edu rustdesk[1646690]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 08:08:22 cheezit.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly.
== emaar (1 distinct, 1 total) ==
Sep 27 08:43:22 emaar puppet-agent[2775603]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== hackerman (1 distinct, 1 total) ==
Sep 27 08:19:39 hackerman systemd[1]: insights-client.service: Start request repeated too quickly.
== idm00 (1 distinct, 1 total) ==
Sep 27 08:54:10 idm00 named[4166701]: client @0x7f11a93f2098 10.73.240.42#63036: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 08:39:28 idmp0 named[1598691]: client @0x7f2d2801dea8 10.73.240.43#57462: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 27 08:18:37 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== mirrors.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 08:37:00 mirrors.cs.umd.edu puppet-agent[16899]: (Facter) Error while resolving custom fact fact='ipa', resolution='<anonymous>': Failed while executing '/usr/bin/kinit -k 2>&1': Timeout encounter after 10s, killing process with pid: 17116
== netman.cs.umd.edu (2 distinct, 36 total) ==
Sep 27 08:25:21 netman.cs.umd.edu krb5_child[1330021]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x18]
Sep 27 08:44:13 netman.cs.umd.edu krb5_child[1336458]: Preauthentication failed [x18]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 08:13:03 newhonors2 dhcpcd[3222080]: dhcpcd is not running [x24]
== ntop00 (81 distinct, 118724 total) ==
Sep 27 08:06:44 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 ] [x56653]
Sep 27 08:06:44 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 ] [x53913]
Sep 27 08:06:44 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 ] [x238]
Sep 27 08:06:44 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 ] [x238]
Sep 27 08:06:45 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 ] [x7586]
Sep 27 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1163) ***
Sep 27 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1163, QN: 4850/4850, ET: 0) ***
Sep 27 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1163) ***
Sep 27 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1163, QN: 72/72, ET: 0) ***
Sep 27 08:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 08: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 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1164) ***
Sep 27 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1164, QN: 0/4986, ET: 0) ***
Sep 27 08:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 08: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 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1164) ***
Sep 27 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1164, QN: 0/66, ET: 0) ***
Sep 27 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1165) ***
Sep 27 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1165, QN: 5100/5100, ET: 0) ***
Sep 27 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1165) ***
Sep 27 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1165, QN: 54/54, ET: 0) ***
Sep 27 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1167) ***
Sep 27 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1167, QN: 4744/4744, ET: 0) ***
Sep 27 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1167) ***
Sep 27 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1167, QN: 88/88, ET: 0) ***
Sep 27 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1168) ***
Sep 27 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1168, QN: 0/4747, ET: 0) ***
Sep 27 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1168) ***
Sep 27 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1168, QN: 0/83, ET: 0) ***
Sep 27 08:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1169) ***
... 51 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 08:09:09 outbound00.cs.umd.edu python3[187462]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 08:13:06 outbound01.cs.umd.edu python3[2449932]: ldapdb [x6]
== quiss (2 distinct, 4 total) ==
Sep 27 08:56:53 quiss packagekitd[3262930]: Failed to get cache filename for perl [x2]
Sep 27 08:56:53 quiss packagekitd[3262930]: Failed to get cache filename for kernel [x2]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571929]: Could not generate persistent MAC address for veth7b33bde: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571930]: Could not generate persistent MAC address for veth07f5921: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571953]: Could not generate persistent MAC address for veth02dfe2f: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571934]: Could not generate persistent MAC address for veth8691e66: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571953]: Could not generate persistent MAC address for veth4da40f3: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571934]: Could not generate persistent MAC address for veth365a475: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571934]: Could not generate persistent MAC address for vethe4f1db8: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571935]: Could not generate persistent MAC address for veth08d9c7b: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571953]: Could not generate persistent MAC address for veth17cf5e1: No such file or directory
Sep 27 08:05:02 sentry-docker00.cs.umd.edu systemd-udevd[571943]: Could not generate persistent MAC address for veth3753788: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581242]: link_config: could not get ethtool features for veth3753788
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581242]: Could not set offload features of veth3753788: No such device
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581337]: link_config: could not get ethtool features for veth08d9c7b
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581337]: Could not set offload features of veth08d9c7b: No such device
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581361]: Could not generate persistent MAC address for vethf444dbf: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581362]: Could not generate persistent MAC address for veth0e0f642: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581380]: Could not generate persistent MAC address for vethe3db6b3: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581375]: Could not generate persistent MAC address for veth6b6e341: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581382]: Could not generate persistent MAC address for veth0c1567b: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581386]: Could not generate persistent MAC address for veth9cea9b1: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581376]: Could not generate persistent MAC address for veth6b8f23f: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581377]: Could not generate persistent MAC address for veth9cabfc7: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581423]: Could not generate persistent MAC address for veth167a499: No such file or directory
Sep 27 08:25:10 sentry-docker00.cs.umd.edu systemd-udevd[581427]: Could not generate persistent MAC address for vethf0cd49e: No such file or directory
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590653]: link_config: could not get ethtool features for veth9cea9b1
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590653]: Could not set offload features of veth9cea9b1: No such device
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590722]: Could not generate persistent MAC address for vethbb781f0: No such file or directory
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590723]: Could not generate persistent MAC address for veth290769f: No such file or directory
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590726]: Could not generate persistent MAC address for vethb0435b0: No such file or directory
Sep 27 08:45:18 sentry-docker00.cs.umd.edu systemd-udevd[590727]: Could not generate persistent MAC address for veth1d71058: No such file or directory
... 6 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 27 08:58:08 smokeping-slave nologin[2789898]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (7 distinct, 38 total) ==
Sep 27 08: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 08: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 08:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 08: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 08: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 08:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 08:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f2 (1 distinct, 2 total) ==
Sep 27 08:45:38 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-f3 (1 distinct, 2 total) ==
Sep 27 08:37:12 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 27 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TKsqzA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 27 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TKsqzA. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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 08:22:02 submit26-b9-fclone setroubleshoot[577469]: 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
== teaching-awards (1 distinct, 3 total) ==
Sep 27 08:45:28 teaching-awards krb5_child[1790918]: Preauthentication failed [x3]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5331s
Status : exited 0
Output :
Syslog digest — 2026-09-27 08:05 EDT
Processed 120,213 lines, filtered 1,355 (1%). 118,858 unknown (108 distinct) from 16 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 08:02:42 b0b02.cs.umd.edu rustdesk[1631316]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 27 07:54:10 idm00 named[4166701]: client @0x7f11a9460ca8 10.73.240.42#51417: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 07:39:28 idmp0 named[1598691]: client @0x7f2d3c0060b8 10.73.240.43#52804: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 3 total) ==
Sep 27 07:14:30 inbound00.cs.umd.edu cockpit-ws[326266]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
== inbound01.cs.umd.edu (1 distinct, 2 total) ==
Sep 27 07:14:34 inbound01.cs.umd.edu cockpit-ws[2538995]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== irb2156 (1 distinct, 1 total) ==
Sep 27 07:19:06 irb2156 systemd[1]: insights-client.service: Start request repeated too quickly.
== itmon02 (1 distinct, 4 total) ==
Sep 27 07:32:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 8 total) ==
Sep 27 07:14:11 munin sudo[145970]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 27 07:14:11 munin sudo[145970]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 07:13:02 newhonors2 dhcpcd[3220237]: dhcpcd is not running [x24]
== ntop00 (61 distinct, 118732 total) ==
Sep 27 07:06:19 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 ] [x56612]
Sep 27 07:06:19 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 ] [x53828]
Sep 27 07:06:19 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 ] [x237]
Sep 27 07:06:19 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 ] [x237]
Sep 27 07:06:19 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 ] [x7742]
Sep 27 07:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1139) ***
Sep 27 07:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1139, QN: 4734/4734, ET: 0) ***
Sep 27 07:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1139) ***
Sep 27 07:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1139, QN: 54/54, ET: 0) ***
Sep 27 07:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 07: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 07:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1140) ***
Sep 27 07:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1140, QN: 0/4089, ET: 0) ***
Sep 27 07:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 07: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 07:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1140) ***
Sep 27 07:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1140, QN: 0/53, ET: 0) ***
Sep 27 07:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1143) ***
Sep 27 07:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1143, QN: 3985/3985, ET: 0) ***
Sep 27 07:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1143) ***
Sep 27 07:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1143, QN: 55/55, ET: 0) ***
Sep 27 07:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1144) ***
Sep 27 07:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1144, QN: 0/4066, ET: 0) ***
Sep 27 07:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1144) ***
Sep 27 07:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1144, QN: 0/60, ET: 0) ***
Sep 27 07:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1147) ***
Sep 27 07:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1147, QN: 4403/4403, ET: 0) ***
Sep 27 07:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1147) ***
Sep 27 07:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1147, QN: 66/66, ET: 0) ***
Sep 27 07:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1148) ***
... 31 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 07:09:09 outbound00.cs.umd.edu python3[173261]: ldapdb [x6]
Sep 27 07:11:05 outbound00.cs.umd.edu cockpit-ws[173829]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x2]
== outbound01.cs.umd.edu (2 distinct, 9 total) ==
Sep 27 07:11:12 outbound01.cs.umd.edu cockpit-ws[2435208]: /usr/share/cockpit/static/login.js/favicon.ico: Failed to open file “/usr/share/cockpit/static/login.js/favicon.ico”: open() failed: Not a directory [x3]
Sep 27 07:13:06 outbound01.cs.umd.edu python3[2435726]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (24 distinct, 24 total) ==
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553032]: link_config: could not get ethtool features for veth847db45
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553032]: Could not set offload features of veth847db45: No such device
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553133]: Could not generate persistent MAC address for vetha9bf44b: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553134]: Could not generate persistent MAC address for veth001574c: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553137]: Could not generate persistent MAC address for veth5f9f70e: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553133]: Could not generate persistent MAC address for veth15107e8: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553143]: Could not generate persistent MAC address for veth4a982ea: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553139]: Could not generate persistent MAC address for veth42f3356: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553163]: Could not generate persistent MAC address for veth96fa900: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553164]: Could not generate persistent MAC address for vetha8ae265: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553182]: Could not generate persistent MAC address for vetha47c880: No such file or directory
Sep 27 07:24:45 sentry-docker00.cs.umd.edu systemd-udevd[553163]: Could not generate persistent MAC address for vetha80312c: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562510]: link_config: could not get ethtool features for vetha47c880
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562510]: Could not set offload features of vetha47c880: No such device
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562537]: Could not generate persistent MAC address for veth22d751b: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562538]: Could not generate persistent MAC address for veth833c01b: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562537]: Could not generate persistent MAC address for veth1f77950: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562554]: Could not generate persistent MAC address for vethe1236ab: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562565]: Could not generate persistent MAC address for veth64e8a87: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562566]: Could not generate persistent MAC address for vetha662482: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562575]: Could not generate persistent MAC address for veth565e0ac: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562582]: Could not generate persistent MAC address for veth7591ab3: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562603]: Could not generate persistent MAC address for vetha4d99b4: No such file or directory
Sep 27 07:44:53 sentry-docker00.cs.umd.edu systemd-udevd[562600]: Could not generate persistent MAC address for veth1944c5a: No such file or directory
== strawberry (7 distinct, 38 total) ==
Sep 27 07: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 07: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 07:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 07: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 07: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 07:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 07:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit10-cln25 (1 distinct, 1 total) ==
Sep 27 07:37:01 submit10-cln25 systemd: Failed at step EXEC spawning /usr/local/bin/cronjob: No such file or directory
== uffish.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 07:34:44 uffish.cs.umd.edu systemd-timedated[4150436]: /dev/rtc is busy. Is somebody keeping it open continuously? That's not a good idea... Returning a bogus RTC timestamp.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5370s
Status : exited 0
Output :
Syslog digest — 2026-09-27 07:05 EDT
Processed 120,706 lines, filtered 1,631 (1%). 119,075 unknown (320 distinct) from 24 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 27 06:15:00 abadi-computer nologin[1144727]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 06:15:00 abadi-computer pipewire[1144726]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
== b0b02.cs.umd.edu (2 distinct, 2 total) ==
Sep 27 06:57:08 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly.
Sep 27 07:02:38 b0b02.cs.umd.edu rustdesk[1615155]: cannot open display:
== galahad.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:19:12 galahad.cs.umd.edu gnome-software[2904800]: Only 0 apps for recent list, hiding
== grosh (166 distinct, 174 total) ==
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for cosmic-epoch [x3]
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for xz
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for xz-libs
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for vim-data
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for vim-minimal
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for openssl
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for openssl-libs
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for libldb
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for libsmbclient
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for libwbclient
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for samba-client-libs
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for samba-common
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for samba-common-libs
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for sudo
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for kernel-modules-extra-matched [x3]
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for wget
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for ipp-usb
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for grafana
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for grafana-selinux
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for grafana-pcp
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for rhc
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for buildah
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for xz-devel
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for qt6-qt5compat
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for vim-common
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for vim-enhanced
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for xxd
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for freerdp-libs
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for libwinpr
Sep 27 06:37:27 grosh packagekitd[259260]: Failed to get cache filename for scap-security-guide
... 136 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 27 06:54:09 idm00 named[4166701]: client @0x7f11a4033978 10.73.240.42#56800: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 06:39:28 idmp0 named[1598691]: client @0x7f2d2401f488 10.73.240.43#50501: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:06:59 inbound00.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:17:55 inbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== irb2156 (2 distinct, 2 total) ==
Sep 27 07:04:08 irb2156 packagekitd[1607608]: Failed to get cache filename for cosmic-epoch
Sep 27 07:04:08 irb2156 packagekitd[1607608]: Failed to get cache filename for kernel
== itmon02 (1 distinct, 3 total) ==
Sep 27 06:08:44 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:14:30 kadath.cs.umd.edu gnome-software[589638]: Only 0 apps for recent list, hiding
== librenms (1 distinct, 1 total) ==
Sep 27 06:48:24 librenms puppet-agent[3347679]: The directory '/opt/librenms/rrd' contains 16519 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees
== neoavion (1 distinct, 1 total) ==
Sep 27 06:32:35 neoavion krb5_child[827924]: No credentials cache found
== neodontcare.cs.umd.edu (6 distinct, 7 total) ==
Sep 27 06:14:49 neodontcare.cs.umd.edu gnome-software[10171]: Only 0 apps for recent list, hiding
Sep 27 06:14:58 neodontcare.cs.umd.edu packagekitd[3075751]: Failed to get cache filename for gnu-free-mono-fonts
Sep 27 06:14:58 neodontcare.cs.umd.edu packagekitd[3075751]: Failed to get cache filename for gnu-free-serif-fonts
Sep 27 06:14:58 neodontcare.cs.umd.edu packagekitd[3075751]: Failed to get cache filename for ImageMagick
Sep 27 06:14:58 neodontcare.cs.umd.edu packagekitd[3075751]: Failed to get cache filename for ImageMagick-libs
Sep 27 06:15:02 neodontcare.cs.umd.edu packagekitd[3075751]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 06:13:03 newhonors2 dhcpcd[3218278]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 118726 total) ==
Sep 27 06:05:59 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 ] [x56637]
Sep 27 06:05:59 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 ] [x53805]
Sep 27 06:05:59 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 ] [x236]
Sep 27 06:05:59 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 ] [x236]
Sep 27 06:06:00 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 ] [x7740]
Sep 27 06:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1115) ***
Sep 27 06:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1115, QN: 3969/3969, ET: 0) ***
Sep 27 06:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1115) ***
Sep 27 06:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1115, QN: 65/65, ET: 0) ***
Sep 27 06:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 06: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 06:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1116) ***
Sep 27 06:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1116, QN: 0/4175, ET: 0) ***
Sep 27 06:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 06: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 06:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1116) ***
Sep 27 06:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1116, QN: 0/66, ET: 0) ***
Sep 27 06:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1119) ***
Sep 27 06:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1119, QN: 4795/4795, ET: 0) ***
Sep 27 06:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1119) ***
Sep 27 06:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1119, QN: 75/75, ET: 0) ***
Sep 27 06:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1120) ***
Sep 27 06:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1120, QN: 0/4389, ET: 0) ***
Sep 27 06:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1120) ***
Sep 27 06:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1120, QN: 0/59, ET: 0) ***
Sep 27 06:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1123) ***
Sep 27 06:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1123, QN: 4015/4015, ET: 0) ***
Sep 27 06:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1123) ***
Sep 27 06:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1123, QN: 62/62, ET: 0) ***
Sep 27 06:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1124) ***
... 27 more distinct messages not shown
== orchids (8 distinct, 9 total) ==
Sep 27 06:11:31 orchids gnome-software[1516991]: Only 0 apps for recent list, hiding
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for ImageMagick
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for ImageMagick-libs
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for claude-code
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for libreoffice
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for cups-filesystem
Sep 27 06:11:38 orchids packagekitd[1539565]: Failed to get cache filename for kernel
Sep 27 06:11:45 orchids packagekitd[1539565]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2]
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 06:09:09 outbound00.cs.umd.edu python3[159158]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 06:13:06 outbound01.cs.umd.edu python3[2421644]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524771]: link_config: could not get ethtool features for vethbbbdfcc
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524771]: Could not set offload features of vethbbbdfcc: No such device
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524844]: Could not generate persistent MAC address for veth7f217a9: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524845]: Could not generate persistent MAC address for veth6c6d8ea: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524848]: Could not generate persistent MAC address for vethd84d4ba: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524849]: Could not generate persistent MAC address for veth23ce4c3: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524865]: Could not generate persistent MAC address for veth23faa92: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524861]: Could not generate persistent MAC address for veth104440c: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524863]: Could not generate persistent MAC address for vethc69f746: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524852]: Could not generate persistent MAC address for vethb363f7a: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524878]: Could not generate persistent MAC address for veth53895cf: No such file or directory
Sep 27 06:24:20 sentry-docker00.cs.umd.edu systemd-udevd[524879]: Could not generate persistent MAC address for vethd2d92d1: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534217]: link_config: could not get ethtool features for veth23faa92
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534217]: Could not set offload features of veth23faa92: No such device
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534252]: Could not generate persistent MAC address for vethe03b59e: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534253]: Could not generate persistent MAC address for veth485c2d0: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534256]: Could not generate persistent MAC address for veth7ff7159: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534257]: Could not generate persistent MAC address for vethb0e0a81: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534272]: Could not generate persistent MAC address for vetha586faf: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534252]: Could not generate persistent MAC address for vethbcbaadc: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534263]: Could not generate persistent MAC address for veth0e69f25: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534269]: Could not generate persistent MAC address for vethb028267: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534362]: Could not generate persistent MAC address for veth36e5f21: No such file or directory
Sep 27 06:44:28 sentry-docker00.cs.umd.edu systemd-udevd[534369]: Could not generate persistent MAC address for vethd34216a: No such file or directory
Sep 27 07:04:36 sentry-docker00.cs.umd.edu systemd-udevd[543646]: link_config: could not set ethtool features for vethe03b59e
Sep 27 07:04:36 sentry-docker00.cs.umd.edu systemd-udevd[543646]: Could not set offload features of vethe03b59e: Operation not permitted
Sep 27 07:04:37 sentry-docker00.cs.umd.edu systemd-udevd[543680]: Could not generate persistent MAC address for vethb7bd91f: No such file or directory
Sep 27 07:04:37 sentry-docker00.cs.umd.edu systemd-udevd[543681]: Could not generate persistent MAC address for veth9d46fae: No such file or directory
Sep 27 07:04:37 sentry-docker00.cs.umd.edu systemd-udevd[543684]: Could not generate persistent MAC address for veth334a91c: No such file or directory
Sep 27 07:04:37 sentry-docker00.cs.umd.edu systemd-udevd[543685]: Could not generate persistent MAC address for veth0241bb4: No such file or directory
... 6 more distinct messages not shown
== strawberry (9 distinct, 46 total) ==
Sep 27 06:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 27 06:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 27 06:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x7]
Sep 27 06:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 27 06:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 27 06:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x7]
Sep 27 06:31:04 strawberry nologin[3755035]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 06:31:04 strawberry pipewire[3755034]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
Sep 27 06:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (10 distinct, 14 total) ==
Sep 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gfZ2UB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gfZ2UB. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: 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 27 06:25:57 submit26-b9-f1 setroubleshoot[3893477]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.flgf14. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
== submit26-b9-f2 (9 distinct, 9 total) ==
Sep 27 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vC8x6V/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 27 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vC8x6V. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 27 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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 06:06:51 submit26-b9-f2 setroubleshoot[2962056]: 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
== tlsrpt (1 distinct, 1 total) ==
Sep 27 06:38:03 tlsrpt (httpd)[3268854]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5247s
Status : exited 0
Output :
Syslog digest — 2026-09-27 06:05 EDT
Processed 120,326 lines, filtered 1,444 (1%). 118,882 unknown (134 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 06:02:36 b0b02.cs.umd.edu rustdesk[1599973]: cannot open display:
== grades01.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 05:49:02 grades01.cs.umd.edu puppet-agent[8578]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees
== idm00 (1 distinct, 1 total) ==
Sep 27 05:54:09 idm00 named[4166701]: client @0x7f11a4042778 10.73.240.42#65343: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 05:39:28 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#59923: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 27 05:13:32 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== matrix (4 distinct, 5 total) ==
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369032, but reception only permitted for main PID 720
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369037, but reception only permitted for main PID 720
Sep 27 05:06:38 matrix networkctl[369050]: Interface "vethd12c30e" not found.
Sep 27 05:06:38 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 369050, but reception only permitted for main PID 720 [x2]
== munin (2 distinct, 8 total) ==
Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 27 05:28:03 munin sudo[106952]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 05:13:03 newhonors2 dhcpcd[3216409]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 118726 total) ==
Sep 27 05:05:34 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 ] [x56628]
Sep 27 05:05:34 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 ] [x53947]
Sep 27 05:05:34 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 05:05:34 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 05:05:34 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 ] [x7609]
Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) ***
Sep 27 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 4961/4961, ET: 0) ***
Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1091) ***
Sep 27 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1091, QN: 52/52, ET: 0) ***
Sep 27 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 05: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 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) ***
Sep 27 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/5226, ET: 0) ***
Sep 27 05:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 05: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 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1092) ***
Sep 27 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1092, QN: 0/51, ET: 0) ***
Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) ***
Sep 27 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 4140/4140, ET: 0) ***
Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1095) ***
Sep 27 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1095, QN: 45/45, ET: 0) ***
Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) ***
Sep 27 05:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/4311, ET: 0) ***
Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1096) ***
Sep 27 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1096, QN: 0/53, ET: 0) ***
Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) ***
Sep 27 05:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 4750/4750, ET: 0) ***
Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1099) ***
Sep 27 05:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1099, QN: 47/47, ET: 0) ***
Sep 27 05:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1100) ***
... 27 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 05:09:09 outbound00.cs.umd.edu python3[145212]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 05:08:33 outbound01.cs.umd.edu python3[2405867]: ldapdb [x7]
Sep 27 05:09:40 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: link_config: could not get ethtool features for veth0f0fdb4
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496555]: Could not set offload features of veth0f0fdb4: No such device
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: link_config: could not get ethtool features for vethfa51150
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496556]: Could not set offload features of vethfa51150: No such device
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496590]: Could not generate persistent MAC address for vethf636bdb: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496591]: Could not generate persistent MAC address for vetheb21707: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496594]: Could not generate persistent MAC address for veth1135a1b: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496595]: Could not generate persistent MAC address for vethc17d69e: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496619]: Could not generate persistent MAC address for veth1fe5842: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496624]: Could not generate persistent MAC address for veth17bac38: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496698]: Could not generate persistent MAC address for veth9c3f013: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496699]: Could not generate persistent MAC address for veth3b02923: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496702]: Could not generate persistent MAC address for veth725fedd: No such file or directory
Sep 27 05:23:55 sentry-docker00.cs.umd.edu systemd-udevd[496717]: Could not generate persistent MAC address for veth172a34d: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: link_config: could not get ethtool features for veth725fedd
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[505922]: Could not set offload features of veth725fedd: No such device
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506009]: Could not generate persistent MAC address for veth2662a63: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506010]: Could not generate persistent MAC address for vethc9477ab: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506013]: Could not generate persistent MAC address for veth04310dc: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506015]: Could not generate persistent MAC address for veth139f8b7: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506016]: Could not generate persistent MAC address for veth66f235d: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506014]: Could not generate persistent MAC address for veth8ea4b0e: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506061]: Could not generate persistent MAC address for vethb46c07b: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506069]: Could not generate persistent MAC address for vethab533a1: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506115]: Could not generate persistent MAC address for veth63233ea: No such file or directory
Sep 27 05:44:03 sentry-docker00.cs.umd.edu systemd-udevd[506120]: Could not generate persistent MAC address for veth0b4d3bb: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515437]: Could not generate persistent MAC address for vethe13f1ff: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515438]: Could not generate persistent MAC address for veth24f9360: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515441]: Could not generate persistent MAC address for veth7df4a74: No such file or directory
Sep 27 06:04:12 sentry-docker00.cs.umd.edu systemd-udevd[515442]: Could not generate persistent MAC address for veth08ee2de: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 27 05:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 05:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 27 05: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 05:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.w2ViRp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.w2ViRp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 27 05:06:45 submit26-b9-f3 setroubleshoot[3670144]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (10 distinct, 13 total) ==
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2]
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Wp4Z7D/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2]
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Wp4Z7D. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 [x2]
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 27 05:24:48 submit26-b9-f4 setroubleshoot[2683916]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.zII8EE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5369s
Status : exited 0
Output :
Syslog digest — 2026-09-27 05:05 EDT
Processed 120,369 lines, filtered 1,385 (1%). 118,984 unknown (187 distinct) from 17 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 27 04:15:00 abadi-computer nologin[1137423]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 04:15:00 abadi-computer pipewire[1137422]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 05:02:32 b0b02.cs.umd.edu rustdesk[1584674]: cannot open display:
== forge00 (1 distinct, 1 total) ==
Sep 27 04:09:03 forge00 (httpd)[1369740]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== galax (56 distinct, 57 total) ==
Sep 27 04:21:24 galax puppet-agent[406377]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 27 04:21:24 galax puppet-agent[406377]: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [x2]
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Install/Package[choria]/ensure) change from 'absent' to '0.29.4+resolute' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install choria=0.29.4+resolute' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Install/Package[choria]/ensure) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. (corrective)
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/policies]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/policies/rego]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/plugin.d]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/overrides.json]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/machine]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/usr/bin/choria_mcollective_agent_compat.rb]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/File[/etc/choria/server.conf]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/server.cfg]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/client.cfg]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/choria_util.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rpcutil.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/scout.policy]) Skipping because of failed dependencies
Sep 27 04:21:24 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/File[/etc/choria/policies/rego/default.rego]) Skipping because of failed dependencies
Sep 27 04:21:25 galax puppet-agent[406377]: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 27 04:21:25 galax puppet-agent[406377]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) change from '8.29.0-1+ubuntu26.04' to '8.27.0-1+ubuntu26.04' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install openvox-agent=8.27.0-1+ubuntu26.04' returned 100: W: --force-yes is deprecated, use one of the options starting with --allow instead.
Sep 27 04:21:25 galax puppet-agent[406377]: (/Stage[main]/Puppet::Agent::Install/Package[openvox-agent]/ensure) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. (corrective)
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/Concat_file[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Choria::Config/Concat[/etc/choria/policies/groups]/File[/etc/choria/policies/groups]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/client.conf]/File[/etc/choria/client.conf]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Config/Mcollective::Config_file[/etc/choria/choria-shim.cfg]/File[/etc/choria/choria-shim.cfg]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective::Facts/Exec[mcollective_facts_yaml_refresh]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_puppet/Mcollective::Module_plugin[mcollective_agent_puppet]/File[/etc/choria/policies/puppet.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_service/Mcollective::Module_plugin[mcollective_agent_service]/File[/etc/choria/policies/service.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_package/Mcollective::Module_plugin[mcollective_agent_package]/File[/etc/choria/policies/package.policy]) Skipping because of failed dependencies
Sep 27 04:21:26 galax puppet-agent[406377]: (/Stage[main]/Mcollective_agent_filemgr/Mcollective::Module_plugin[mcollective_agent_filemgr]/File[/etc/choria/policies/filemgr.policy]) Skipping because of failed dependencies
... 26 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 27 04:54:09 idm00 named[4166701]: client @0x7f11a93e2ef8 10.73.240.42#58516: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 04:39:28 idmp0 named[1598691]: client @0x7f2d200357a8 10.73.240.43#55697: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 8 total) ==
Sep 27 04:08:41 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x8]
== matrix (9 distinct, 10 total) ==
Sep 27 05:02:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366704, but reception only permitted for main PID 720
Sep 27 05:02:59 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366715, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366804, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366809, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd-resolved[3892763]: veth847efe6: Failed to determine whether the interface is managed, ignoring: No such file or directory
Sep 27 05:03:08 matrix networkctl[366820]: Interface "veth847efe6" not found.
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366820, but reception only permitted for main PID 720 [x2]
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366880, but reception only permitted for main PID 720
Sep 27 05:03:08 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 366888, but reception only permitted for main PID 720
== munin (2 distinct, 48 total) ==
Sep 27 04:18:53 munin sudo[81320]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x24]
Sep 27 04:18:53 munin sudo[81320]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x24]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 04:13:02 newhonors2 dhcpcd[3214542]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 118732 total) ==
Sep 27 04:05:04 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 ] [x56665]
Sep 27 04:05:04 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 ] [x53891]
Sep 27 04:05:04 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 04:05:04 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 04:05:05 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 ] [x7626]
Sep 27 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1067) ***
Sep 27 04:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1067, QN: 4698/4698, ET: 0) ***
Sep 27 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1067) ***
Sep 27 04:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1067, QN: 60/60, ET: 0) ***
Sep 27 04:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 04: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 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1068) ***
Sep 27 04:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1068, QN: 0/4561, ET: 0) ***
Sep 27 04:10:02 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 04:10:02 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 04:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1068) ***
Sep 27 04:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1068, QN: 0/61, ET: 0) ***
Sep 27 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1071) ***
Sep 27 04:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1071, QN: 5899/5899, ET: 0) ***
Sep 27 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1071) ***
Sep 27 04:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1071, QN: 55/55, ET: 0) ***
Sep 27 04:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1072) ***
Sep 27 04:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1072, QN: 0/6384, ET: 0) ***
Sep 27 04:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1072) ***
Sep 27 04:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1072, QN: 0/59, ET: 0) ***
Sep 27 04:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1075) ***
Sep 27 04:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1075, QN: 4942/4942, ET: 0) ***
Sep 27 04:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1075) ***
Sep 27 04:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1075, QN: 56/56, ET: 0) ***
Sep 27 04:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1076) ***
... 27 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 04:09:09 outbound00.cs.umd.edu python3[131215]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 04:13:07 outbound01.cs.umd.edu python3[2392654]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468139]: link_config: could not get ethtool features for veth928efaf
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468139]: Could not set offload features of veth928efaf: No such device
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468168]: Could not generate persistent MAC address for vethe2a8c74: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468169]: Could not generate persistent MAC address for veth55c5d76: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468172]: Could not generate persistent MAC address for veth75405e3: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468173]: Could not generate persistent MAC address for veth7eb7a28: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468196]: Could not generate persistent MAC address for veth1247093: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468197]: Could not generate persistent MAC address for veth9bafd34: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468219]: Could not generate persistent MAC address for vetha071794: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468196]: Could not generate persistent MAC address for veth008cce3: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468214]: Could not generate persistent MAC address for vetha2230a0: No such file or directory
Sep 27 04:23:30 sentry-docker00.cs.umd.edu systemd-udevd[468210]: Could not generate persistent MAC address for veth6741e3d: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477580]: link_config: could not get ethtool features for veth1247093
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477580]: Could not set offload features of veth1247093: No such device
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477614]: Could not generate persistent MAC address for veth14b7808: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477615]: Could not generate persistent MAC address for vetha3bccbd: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477618]: Could not generate persistent MAC address for veth44c2711: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477619]: Could not generate persistent MAC address for veth920674b: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477635]: Could not generate persistent MAC address for veth249dd8e: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477622]: Could not generate persistent MAC address for veth4a450e8: No such file or directory
Sep 27 04:43:38 sentry-docker00.cs.umd.edu systemd-udevd[477618]: Could not generate persistent MAC address for veth7fdb301: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477621]: Could not generate persistent MAC address for veth6988020: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477639]: Could not generate persistent MAC address for vethf839b04: No such file or directory
Sep 27 04:43:39 sentry-docker00.cs.umd.edu systemd-udevd[477622]: Could not generate persistent MAC address for veth7095131: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487015]: Could not generate persistent MAC address for veth5cf8eb8: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487016]: Could not generate persistent MAC address for veth777fcc2: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487019]: Could not generate persistent MAC address for vethfa51150: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487020]: Could not generate persistent MAC address for veth5feff11: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487043]: Could not generate persistent MAC address for veth0f0fdb4: No such file or directory
Sep 27 05:03:47 sentry-docker00.cs.umd.edu systemd-udevd[487044]: Could not generate persistent MAC address for vetha868110: No such file or directory
... 4 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 27 04:15:31 smokeping-slave nologin[2767094]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (9 distinct, 40 total) ==
Sep 27 04: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 04: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 04:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 04: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 04: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 04:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 04:15:04 strawberry nologin[3745996]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 27 04:15:04 strawberry pipewire[3745995]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
Sep 27 04:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 12 total) ==
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 [x2]
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.kQ75o6/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc [x2]
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 [x2]
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.kQ75o6. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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 04:22:01 submit26-b9-fclone setroubleshoot[567752]: 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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4168s
Status : exited 0
Output :
Syslog digest — 2026-09-27 04:05 EDT
Processed 118,654 lines, filtered 1,281 (1%). 117,373 unknown (139 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 04:02:28 b0b02.cs.umd.edu rustdesk[1569184]: cannot open display:
== grosh (3 distinct, 6 total) ==
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for cosmic-epoch [x2]
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for kernel-modules-extra-matched [x2]
Sep 27 03:43:12 grosh packagekitd[237952]: Failed to get cache filename for kernel [x2]
== idm00 (1 distinct, 1 total) ==
Sep 27 03:54:09 idm00 named[4166701]: client @0x7f11a412e378 10.73.240.42#50147: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 03:39:28 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#49773: update '73.10.in-addr.arpa/IN' denied
== itmon02 (2 distinct, 3 total) ==
Sep 27 03:15:04 itmon02 (httpd)[757611]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Sep 27 03:28:12 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 03:47:32 kadath.cs.umd.edu puppet-agent[2783267]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== librenms (1 distinct, 1 total) ==
Sep 27 03:47:03 librenms (httpd)[3190810]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== munin (2 distinct, 16 total) ==
Sep 27 03:12:57 munin sudo[57610]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8]
Sep 27 03:12:57 munin sudo[57610]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8]
== netbox (1 distinct, 1 total) ==
Sep 27 03:08:03 netbox (httpd)[837653]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== newhonors2 (1 distinct, 24 total) ==
Sep 27 03:13:03 newhonors2 dhcpcd[3212699]: dhcpcd is not running [x24]
== ntop00 (79 distinct, 117230 total) ==
Sep 27 03:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 03:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 03:05: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 27 03:05: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 03:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1042) ***
Sep 27 03:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1042) ***
Sep 27 03:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1042, QN: 0/5065, ET: 0) ***
Sep 27 03:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1042, QN: 0/51, ET: 0) ***
Sep 27 03: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 ] [x55888]
Sep 27 03: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 ] [x52986]
Sep 27 03: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 03: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 03: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 ] [x7770]
Sep 27 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1043) ***
Sep 27 03:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1043, QN: 5730/5730, ET: 0) ***
Sep 27 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1043) ***
Sep 27 03:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1043, QN: 52/52, ET: 0) ***
Sep 27 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1044) ***
Sep 27 03:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1044, QN: 0/5230, ET: 0) ***
Sep 27 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1044) ***
Sep 27 03:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1044, QN: 0/65, ET: 0) ***
Sep 27 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1046) ***
Sep 27 03:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1046, QN: 0/4574, ET: 0) ***
Sep 27 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1046) ***
Sep 27 03:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1046, QN: 0/55, ET: 0) ***
Sep 27 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1047) ***
Sep 27 03:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1047, QN: 4343/4343, ET: 0) ***
Sep 27 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1047) ***
Sep 27 03:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1047, QN: 54/54, ET: 0) ***
Sep 27 03:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1048) ***
... 49 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 03:09:09 outbound00.cs.umd.edu python3[116497]: ldapdb [x7]
Sep 27 03:24:15 outbound00.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 03:13:06 outbound01.cs.umd.edu python3[2378669]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: link_config: could not get ethtool features for vethc3ea7bd
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: Could not set offload features of vethc3ea7bd: No such device
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: link_config: could not get ethtool features for veth3ebd151
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439658]: Could not set offload features of veth3ebd151: No such device
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439778]: Could not generate persistent MAC address for veth7d020f0: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439779]: Could not generate persistent MAC address for veth02ae893: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439797]: Could not generate persistent MAC address for vethb070907: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439802]: Could not generate persistent MAC address for vetha1a619c: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439806]: Could not generate persistent MAC address for veth8cebfac: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439807]: Could not generate persistent MAC address for veth4a84b8a: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439843]: Could not generate persistent MAC address for vetha6c1994: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439827]: Could not generate persistent MAC address for vethe8de0b6: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439923]: Could not generate persistent MAC address for vethcb1bb1d: No such file or directory
Sep 27 03:23:05 sentry-docker00.cs.umd.edu systemd-udevd[439924]: Could not generate persistent MAC address for veth72a0ae9: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449156]: link_config: could not get ethtool features for vethb070907
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449156]: Could not set offload features of vethb070907: No such device
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449191]: Could not generate persistent MAC address for veth5f39b42: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449192]: Could not generate persistent MAC address for vethe864263: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449195]: Could not generate persistent MAC address for vethf5a5bed: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449196]: Could not generate persistent MAC address for veth192dbee: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449192]: Could not generate persistent MAC address for vethd83fb6b: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449207]: Could not generate persistent MAC address for veth00041a4: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449222]: Could not generate persistent MAC address for vethcb20dd7: No such file or directory
Sep 27 03:43:13 sentry-docker00.cs.umd.edu systemd-udevd[449221]: Could not generate persistent MAC address for veth4695587: No such file or directory
Sep 27 03:43:14 sentry-docker00.cs.umd.edu systemd-udevd[449295]: Could not generate persistent MAC address for vethe72a64d: No such file or directory
Sep 27 03:43:14 sentry-docker00.cs.umd.edu systemd-udevd[449296]: Could not generate persistent MAC address for veth7aa5577: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458632]: Could not generate persistent MAC address for vethd8840d5: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458633]: Could not generate persistent MAC address for vethb4b444a: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458651]: Could not generate persistent MAC address for vethe228cf9: No such file or directory
Sep 27 04:03:22 sentry-docker00.cs.umd.edu systemd-udevd[458636]: Could not generate persistent MAC address for veth7119da7: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 03: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 03: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 03:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 03: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 03: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 03:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 03:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
1
0
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
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4737s
Status : exited 0
Output :
Syslog digest — 2026-09-27 02:05 EDT
Processed 119,333 lines, filtered 1,398 (1%). 117,935 unknown (171 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 02:02:22 b0b02.cs.umd.edu rustdesk[1538741]: cannot open display:
== biggulp.cs.umd.edu (4 distinct, 5 total) ==
Sep 27 01:39:27 biggulp.cs.umd.edu sshd-session[353897]: error: send_error: write: Connection reset by peer
Sep 27 01:52:20 biggulp.cs.umd.edu sshd-session[355808]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355808]: Error in Duo login for 'larry' from 71.191.93.172
Sep 27 01:52:21 biggulp.cs.umd.edu sshd-session[355806]: error: PAM: Authentication failure for larry from 71.191.93.172
== hazfs.cs.umd.edu (11 distinct, 66 total) ==
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6]
Sep 27 01:33:47 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6]
== idm00 (1 distinct, 1 total) ==
Sep 27 01:54:09 idm00 named[4166701]: client @0x7f119804e448 10.73.240.42#49232: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 01:39:28 idmp0 named[1598691]: client @0x7f2d2801dea8 10.73.240.43#60684: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 27 01:37:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 01:13:03 newhonors2 dhcpcd[3209007]: dhcpcd is not running [x24]
== ntop00 (84 distinct, 117721 total) ==
Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x13]
Sep 27 01:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x13]
Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 994) ***
Sep 27 01:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 994, QN: 0/59, ET: 0) ***
Sep 27 01: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 ] [x7660]
Sep 27 01: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 ] [x56138]
Sep 27 01: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 ] [x53326]
Sep 27 01: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 01: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 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 995) ***
Sep 27 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 4982/4982, ET: 0) ***
Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 995) ***
Sep 27 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 995, QN: 62/62, ET: 0) ***
Sep 27 01:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 01: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 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) ***
Sep 27 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/5332, ET: 0) ***
Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 996) ***
Sep 27 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 996, QN: 0/57, ET: 0) ***
Sep 27 01:14:01 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 ] [x3]
Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) ***
Sep 27 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/4550, ET: 0) ***
Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 998) ***
Sep 27 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 998, QN: 0/44, ET: 0) ***
Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 999) ***
Sep 27 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 4181/4181, ET: 0) ***
Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 999) ***
Sep 27 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 999, QN: 59/59, ET: 0) ***
Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1000) ***
Sep 27 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1000, QN: 0/4835, ET: 0) ***
... 54 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 01:09:09 outbound00.cs.umd.edu python3[88452]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 01:13:06 outbound01.cs.umd.edu python3[2350588]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: link_config: could not get ethtool features for vethcc2a3ca
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382295]: Could not set offload features of vethcc2a3ca: No such device
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382335]: Could not generate persistent MAC address for veth2565a2d: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382336]: Could not generate persistent MAC address for veth7f3d35c: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382339]: Could not generate persistent MAC address for vethaef78cf: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382340]: Could not generate persistent MAC address for veth56ad423: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382355]: Could not generate persistent MAC address for vethbcef809: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382360]: Could not generate persistent MAC address for vethfe6192a: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382365]: Could not generate persistent MAC address for veth1b3d073: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382366]: Could not generate persistent MAC address for vethb7c6c03: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382416]: Could not generate persistent MAC address for vethe01ccb9: No such file or directory
Sep 27 01:22:15 sentry-docker00.cs.umd.edu systemd-udevd[382419]: Could not generate persistent MAC address for veth4da65f1: No such file or directory
Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: link_config: could not get ethtool features for veth1b3d073
Sep 27 01:42:23 sentry-docker00.cs.umd.edu systemd-udevd[391963]: Could not set offload features of veth1b3d073: No such device
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392035]: Could not generate persistent MAC address for vethe66ae91: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392036]: Could not generate persistent MAC address for vethe7d5825: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392039]: Could not generate persistent MAC address for vethb1d1906: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392040]: Could not generate persistent MAC address for veth58502ce: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392063]: Could not generate persistent MAC address for veth0ab8b6c: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392064]: Could not generate persistent MAC address for veth88bc1af: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392082]: Could not generate persistent MAC address for veth0a8d887: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392073]: Could not generate persistent MAC address for vethfb794bb: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392079]: Could not generate persistent MAC address for veth1e4876d: No such file or directory
Sep 27 01:42:24 sentry-docker00.cs.umd.edu systemd-udevd[392069]: Could not generate persistent MAC address for vethcaa04a4: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: link_config: could not set ethtool features for veth0a8d887
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401421]: Could not set offload features of veth0a8d887: Operation not permitted
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401446]: Could not generate persistent MAC address for veth262900a: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401447]: Could not generate persistent MAC address for vethee7109a: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401465]: Could not generate persistent MAC address for vethc206693: No such file or directory
Sep 27 02:02:32 sentry-docker00.cs.umd.edu systemd-udevd[401450]: Could not generate persistent MAC address for veth874fa89: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f2 (1 distinct, 1 total) ==
Sep 27 01:30:07 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f3 (10 distinct, 10 total) ==
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.oqoEim/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.oqoEim. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65
Sep 27 01:06:45 submit26-b9-f3 setroubleshoot[3649673]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
Sep 27 01:08:20 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
== submit26-b9-f4 (11 distinct, 14 total) ==
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d [x2]
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4WQs5e/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e [x2]
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.4WQs5e. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 [x2]
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915
Sep 27 01:24:49 submit26-b9-f4 setroubleshoot[2669749]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.EPY0OG/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 01:50:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
1
0