Command: /usr/local/sbin/syslog-digest.py
Time : 7.4723s
Status : exited 0
Output :
Syslog digest — 2026-09-27 16:05 EDT
Processed 119,645 lines, filtered 1,851 (1%). 117,794 unknown (121 distinct) from 13 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 16:03:14 b0b02.cs.umd.edu rustdesk[1753263]: cannot open display:
== idm00 (2 distinct, 2 total) ==
Sep 27 15:53:06 idm00 named[4166701]: client @0x7f11a001f8d8 10.73.245.12#54473: update '73.10.in-addr.arpa/IN' denied
Sep 27 15:54:10 idm00 named[4166701]: client @0x7f11a006da58 10.73.240.42#59673: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 15:39:28 idmp0 named[1598691]: client @0x7f2d3c082968 10.73.240.43#51233: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 2 total) ==
Sep 27 15:37:49 inbound00.cs.umd.edu cockpit-ws[445827]: /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]
== inbound01.cs.umd.edu (1 distinct, 2 total) ==
Sep 27 15:37:45 inbound01.cs.umd.edu cockpit-ws[2658440]: /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]
== itmon02 (1 distinct, 4 total) ==
Sep 27 15:22:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== munin (2 distinct, 2 total) ==
Sep 27 16:04:06 munin sudo[337511]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 27 16:04:06 munin sudo[337511]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== newhonors2 (1 distinct, 24 total) ==
Sep 27 15:13:02 newhonors2 dhcpcd[3235041]: dhcpcd is not running [x24]
== ntop00 (66 distinct, 117667 total) ==
Sep 27 15:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x8]
Sep 27 15:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x8]
Sep 27 15:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1330) ***
Sep 27 15:05:01 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 ] [x56141]
Sep 27 15:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1330, QN: 0/10141, ET: 0) ***
Sep 27 15:05:01 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 ] [x53431]
Sep 27 15:05:01 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 27 15:05:01 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 27 15:05:01 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 ] [x7523]
Sep 27 15:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x8]
Sep 27 15:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x8]
Sep 27 15:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1330) ***
Sep 27 15:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1330, QN: 0/86, ET: 0) ***
Sep 27 15:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1332) ***
Sep 27 15:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1332, QN: 0/9858, ET: 0) ***
Sep 27 15:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1332) ***
Sep 27 15:10:02 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1332, QN: 0/66, ET: 0) ***
Sep 27 15:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1333) ***
Sep 27 15:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1333, QN: 76/76, ET: 0) ***
Sep 27 15:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1333) ***
Sep 27 15:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1333, QN: 9343/9343, ET: 0) ***
Sep 27 15: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 ] [x18]
Sep 27 15:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1334) ***
Sep 27 15:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1334, QN: 0/9606, ET: 0) ***
Sep 27 15:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1334) ***
Sep 27 15:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1334, QN: 0/77, ET: 0) ***
Sep 27 15:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1336) ***
Sep 27 15:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1336, QN: 0/11038, ET: 0) ***
Sep 27 15:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1336) ***
Sep 27 15:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1336, QN: 0/57, ET: 0) ***
... 36 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 8 total) ==
Sep 27 15:09:09 outbound00.cs.umd.edu python3[285998]: ldapdb [x6]
Sep 27 15:34:25 outbound00.cs.umd.edu cockpit-ws[291977]: /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 15:13:06 outbound01.cs.umd.edu python3[2548822]: ldapdb [x6]
Sep 27 15:59:10 outbound01.cs.umd.edu cockpit-ws[2559851]: /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]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771971]: Could not generate persistent MAC address for veth542f089: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771972]: Could not generate persistent MAC address for veth700cc21: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771990]: Could not generate persistent MAC address for veth2fc54c2: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771972]: Could not generate persistent MAC address for veth5146d72: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771991]: Could not generate persistent MAC address for vethd4cf5ee: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771997]: Could not generate persistent MAC address for veth52d5978: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771993]: Could not generate persistent MAC address for veth761272f: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771972]: Could not generate persistent MAC address for veth11eb2a9: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771979]: Could not generate persistent MAC address for vetha711755: No such file or directory
Sep 27 15:07:56 sentry-docker00.cs.umd.edu systemd-udevd[771995]: Could not generate persistent MAC address for vethe5fcb36: No such file or directory
Sep 27 15:28:04 sentry-docker00.cs.umd.edu systemd-udevd[781333]: link_config: could not get ethtool features for veth2fc54c2
Sep 27 15:28:04 sentry-docker00.cs.umd.edu systemd-udevd[781333]: Could not set offload features of veth2fc54c2: No such device
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781377]: Could not generate persistent MAC address for veth2de5ef9: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781378]: Could not generate persistent MAC address for vethedf0439: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781381]: Could not generate persistent MAC address for veth791d6a5: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781382]: Could not generate persistent MAC address for vethe5a27b8: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781399]: Could not generate persistent MAC address for veth151df37: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781396]: Could not generate persistent MAC address for vethd2a79c4: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781408]: Could not generate persistent MAC address for veth3c4ee5a: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781412]: Could not generate persistent MAC address for veth52af330: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781426]: Could not generate persistent MAC address for vethd084787: No such file or directory
Sep 27 15:28:05 sentry-docker00.cs.umd.edu systemd-udevd[781449]: Could not generate persistent MAC address for veth3d94628: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791722]: link_config: could not get ethtool features for veth3c4ee5a
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791722]: Could not set offload features of veth3c4ee5a: No such device
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791749]: Could not generate persistent MAC address for veth05a231a: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791750]: Could not generate persistent MAC address for veth134f6ed: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791753]: Could not generate persistent MAC address for veth0e7717c: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791754]: Could not generate persistent MAC address for vetha0aa95f: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791760]: Could not generate persistent MAC address for veth3c68785: No such file or directory
Sep 27 15:48:13 sentry-docker00.cs.umd.edu systemd-udevd[791766]: Could not generate persistent MAC address for veth5b1216e: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 15: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 15: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 15:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 15: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 15: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 15:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 15: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.4120s
Status : exited 0
Output :
Syslog digest — 2026-09-27 15:05 EDT
Processed 118,547 lines, filtered 1,679 (1%). 116,868 unknown (181 distinct) from 17 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 15:03:09 b0b02.cs.umd.edu rustdesk[1738078]: cannot open display:
== cheezit.cs.umd.edu (2 distinct, 2 total) ==
Sep 27 14:09:16 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 27 14:09:16 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== idm00 (1 distinct, 1 total) ==
Sep 27 14:54:10 idm00 named[4166701]: client @0x7f11980104c8 10.73.240.42#53663: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 14:39:28 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#54412: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 27 14:43:01 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== lifepix (1 distinct, 1 total) ==
Sep 27 14:38:04 lifepix setroubleshoot[431855]: SELinux is preventing /usr/bin/podman from using the nnp_transition access on a process. For complete SELinux messages run: sealert -l db6b3d2c-fa5b-4b9b-8ef7-675cd3f54e86
== munin (2 distinct, 4 total) ==
Sep 27 14:43:03 munin sudo[308412]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 27 14:43:03 munin sudo[308412]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 14:13:03 newhonors2 dhcpcd[3233181]: dhcpcd is not running [x24]
== ntop00 (82 distinct, 116695 total) ==
Sep 27 14:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 14:05: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 14:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1306) ***
Sep 27 14:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1306, QN: 0/8265, ET: 0) ***
Sep 27 14:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 14: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 14:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1306) ***
Sep 27 14:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1306, QN: 0/50, ET: 0) ***
Sep 27 14:05: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 ] [x55625]
Sep 27 14:05: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 ] [x7686]
Sep 27 14:05: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 ] [x52788]
Sep 27 14:05: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 ] [x230]
Sep 27 14:05: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 ] [x230]
Sep 27 14:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1308) ***
Sep 27 14:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1308, QN: 0/9096, ET: 0) ***
Sep 27 14:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1308) ***
Sep 27 14:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1308, QN: 0/66, ET: 0) ***
Sep 27 14:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1309) ***
Sep 27 14:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1309, QN: 63/63, ET: 0) ***
Sep 27 14:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1309) ***
Sep 27 14:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1309, QN: 9699/9699, ET: 0) ***
Sep 27 14: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 ] [x16]
Sep 27 14:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1310) ***
Sep 27 14:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1310, QN: 0/9599, ET: 0) ***
Sep 27 14:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1310) ***
Sep 27 14:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1310, QN: 0/75, ET: 0) ***
Sep 27 14:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1312) ***
Sep 27 14:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1312, QN: 0/60, ET: 0) ***
Sep 27 14:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1312) ***
Sep 27 14:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1312, QN: 0/8690, ET: 0) ***
... 52 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 14:09:09 outbound00.cs.umd.edu python3[271864]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 14:13:07 outbound01.cs.umd.edu python3[2534847]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743552]: link_config: could not get ethtool features for veth628ac28
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743552]: Could not set offload features of veth628ac28: No such device
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743652]: link_config: could not get ethtool features for veth31e0a82
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743652]: Could not set offload features of veth31e0a82: No such device
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743655]: link_config: could not get ethtool features for veth15d7ba0
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743655]: Could not set offload features of veth15d7ba0: No such device
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743681]: Could not generate persistent MAC address for veth2e43676: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743682]: Could not generate persistent MAC address for vethe96e25a: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743700]: Could not generate persistent MAC address for vethaf77a2b: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743703]: Could not generate persistent MAC address for vethdcf59fa: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743700]: Could not generate persistent MAC address for vetheffcb59: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743687]: Could not generate persistent MAC address for veth6d7892f: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743728]: Could not generate persistent MAC address for vethec636ba: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743730]: Could not generate persistent MAC address for vethe2f7f52: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743741]: Could not generate persistent MAC address for vethde19020: No such file or directory
Sep 27 14:07:31 sentry-docker00.cs.umd.edu systemd-udevd[743750]: Could not generate persistent MAC address for veth9d62913: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753121]: Could not generate persistent MAC address for vethddd51f4: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753122]: Could not generate persistent MAC address for veth275325b: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753125]: Could not generate persistent MAC address for veth57e0e7c: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753126]: Could not generate persistent MAC address for veth673ef01: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753149]: Could not generate persistent MAC address for vethd7e0e32: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753150]: Could not generate persistent MAC address for vethfaa1946: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753166]: Could not generate persistent MAC address for veth124a230: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753153]: Could not generate persistent MAC address for veth7411464: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753195]: Could not generate persistent MAC address for veth39a9c3a: No such file or directory
Sep 27 14:27:40 sentry-docker00.cs.umd.edu systemd-udevd[753196]: Could not generate persistent MAC address for veth730df33: No such file or directory
Sep 27 14:47:48 sentry-docker00.cs.umd.edu systemd-udevd[762545]: Could not generate persistent MAC address for veth4edc6ad: No such file or directory
Sep 27 14:47:48 sentry-docker00.cs.umd.edu systemd-udevd[762546]: Could not generate persistent MAC address for veth7e3d4d2: No such file or directory
Sep 27 14:47:48 sentry-docker00.cs.umd.edu systemd-udevd[762549]: Could not generate persistent MAC address for vetha8e19c4: No such file or directory
Sep 27 14:47:48 sentry-docker00.cs.umd.edu systemd-udevd[762550]: Could not generate persistent MAC address for vethb47d221: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 14: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 14: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 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 14: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 14: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 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (12 distinct, 12 total) ==
Sep 27 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.sYlerc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 27 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.sYlerc. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 27 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:25:57 submit26-b9-f1 setroubleshoot[3922273]: 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 14:53:35 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 27 14:53:36 submit26-b9-f1 systemd-coredump[3929994]: Process 3929991 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3929991:#012#0 0x00007f3336e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f3336e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f3336e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f3336e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f3336f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f3336f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:53:37 submit26-b9-f1 systemd-coredump[3930004]: Process 3930001 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3930001:#012#0 0x00007f026308d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f026303fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f0263029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f026302a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f026311d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f026311e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (16 distinct, 20 total) ==
Sep 27 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 [x2]
Sep 27 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a [x2]
Sep 27 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: 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 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.KO0zNa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 27 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: 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 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.KO0zNa. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 27 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: 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 14:06:51 submit26-b9-f2 setroubleshoot[2999039]: 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 14:06:52 submit26-b9-f2 setroubleshoot[2999039]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7
Sep 27 14:20:01 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x3]
Sep 27 14:20:03 submit26-b9-f2 systemd-coredump[3001802]: Process 3001799 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3001799:#012#0 0x00007f5eb8c8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f5eb8c3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f5eb8c29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f5eb8c2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f5eb8d1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f5eb8d1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:20:03 submit26-b9-f2 systemd-coredump[3001813]: Process 3001809 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3001809:#012#0 0x00007f5a4808d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f5a4803fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f5a48029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f5a4802a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f5a4811d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f5a4811e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:32:51 submit26-b9-f2 systemd-coredump[3004901]: Process 3004898 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3004898:#012#0 0x00007fbeec88d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fbeec83fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fbeec829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fbeec82a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fbeec91d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fbeec91e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:32:52 submit26-b9-f2 systemd-coredump[3004912]: Process 3004909 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3004909:#012#0 0x00007f649108d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f649103fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6491029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f649102a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f649111d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f649111e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:53:46 submit26-b9-f2 systemd-coredump[3010493]: Process 3010490 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3010490:#012#0 0x00007fa68f08d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fa68f03fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fa68f029873 abort (libc.so.6 + 0x29873)#012#3 0x00007fa68f02a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fa68f11d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fa68f11e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:53:47 submit26-b9-f2 systemd-coredump[3010503]: Process 3010500 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3010500:#012#0 0x00007f740788d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f740783fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f7407829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f740782a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f740791d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f740791e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (13 distinct, 17 total) ==
Sep 27 14:11:13 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x5]
Sep 27 14:11:14 submit26-b9-f3 systemd-coredump[3714910]: Process 3714907 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3714907:#012#0 0x00007ff31fa8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007ff31fa3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007ff31fa29873 abort (libc.so.6 + 0x29873)#012#3 0x00007ff31fa2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007ff31fb1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007ff31fb1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:11:14 submit26-b9-f3 systemd-coredump[3714921]: Process 3714917 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3714917:#012#0 0x00007f664fc8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f664fc3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f664fc29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f664fc2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f664fd1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f664fd1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:13:35 submit26-b9-f3 systemd-coredump[3715160]: Process 3715157 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3715157:#012#0 0x00007f736528d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f736523fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f7365229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f736522a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f736531d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f736531e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:13:35 submit26-b9-f3 systemd-coredump[3715171]: Process 3715167 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3715167:#012#0 0x00007fd93288d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fd93283fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fd932829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fd93282a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fd93291d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fd93291e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:24:20 submit26-b9-f3 systemd-coredump[3718314]: Process 3718311 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3718311:#012#0 0x00007fbf41e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fbf41e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fbf41e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fbf41e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fbf41f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fbf41f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
Sep 27 14:24:20 submit26-b9-f3 systemd-coredump[3718324]: Process 3718321 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3718321:#012#0 0x00007fa19de8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fa19de3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fa19de29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fa19de2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fa19df1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fa19df1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
Sep 27 14:33:37 submit26-b9-f3 systemd-coredump[3719424]: Process 3719421 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3719421:#012#0 0x00007f7b0ee8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f7b0ee3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f7b0ee29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f7b0ee2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f7b0ef1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f7b0ef1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:33:37 submit26-b9-f3 systemd-coredump[3719435]: Process 3719432 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3719432:#012#0 0x00007f2f3ac8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f2f3ac3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2f3ac29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f2f3ac2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f2f3ad1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f2f3ad1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f0 main (grades + 0x18f0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:40:08 submit26-b9-f3 systemd-coredump[3722422]: Process 3722419 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3722419:#012#0 0x00007f71d1c8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f71d1c3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f71d1c29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f71d1c2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f71d1d1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f71d1d1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:40:08 submit26-b9-f3 systemd-coredump[3722432]: Process 3722429 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3722429:#012#0 0x00007fbf71c8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fbf71c3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fbf71c29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fbf71c2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fbf71d1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fbf71d1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
Sep 27 14:45:08 submit26-b9-f3 systemd-coredump[3722972]: Process 3722969 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3722969:#012#0 0x00007f2db328d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f2db323fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2db3229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f2db322a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f2db331d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f2db331e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
Sep 27 14:45:08 submit26-b9-f3 systemd-coredump[3722982]: Process 3722979 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3722979:#012#0 0x00007f46bb88d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f46bb83fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f46bb829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f46bb82a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f46bb91d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f46bb91e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (3 distinct, 3 total) ==
Sep 27 15:00:10 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 27 15:00:12 submit26-b9-f4 systemd-coredump[2718408]: Process 2718405 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2718405:#012#0 0x00007fc2af88d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fc2af83fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fc2af829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fc2af82a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fc2af91d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fc2af91e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
Sep 27 15:00:13 submit26-b9-f4 systemd-coredump[2718418]: Process 2718415 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2718415:#012#0 0x00007f0ecd08d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f0ecd03fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f0ecd029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f0ecd02a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f0ecd11d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f0ecd11e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x0000000000401ac0 main (grades + 0x1ac0)#012ELF object binary architecture: AMD x86-64
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.3938s
Status : exited 0
Output :
Syslog digest — 2026-09-27 14:05 EDT
Processed 118,698 lines, filtered 1,841 (1%). 116,857 unknown (166 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 14:03:05 b0b02.cs.umd.edu rustdesk[1722844]: cannot open display:
== bachata (10 distinct, 10 total) ==
Sep 27 13:57:11 bachata smbd[1280196]: [2026/09/27 13:57:11.928052, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service)
Sep 27 13:57:11 bachata smbd[1280196]: chdir_current_service: vfs_ChDir(/fs/junkfood/mount) failed: Permission denied. Current token: uid=11255, gid=11255, 12 groups: 11255 319000009 25038 15294 15229 755 25030 25025 30880 25029 770 15026
Sep 27 13:57:11 bachata smbd[1280196]: [2026/09/27 13:57:11.929989, 0] ../../source3/smbd/smbXsrv_tcon.c:914(smbXsrv_tcon_disconnect)
Sep 27 13:57:11 bachata smbd[1280196]: smbXsrv_tcon_disconnect: disconnect(0xe8eb0413, 'mount'): chdir_current_service() failed: NT_STATUS_INTERNAL_ERROR
Sep 27 13:57:11 bachata smbd[1280196]: [2026/09/27 13:57:11.930237, 0] ../../source3/smbd/smbXsrv_tcon.c:1028(smbXsrv_tcon_disconnect_all)
Sep 27 13:57:11 bachata smbd[1280196]: smbXsrv_tcon_disconnect_all: count[2] errors[1] first[NT_STATUS_INTERNAL_ERROR]
Sep 27 13:57:11 bachata smbd[1280196]: [2026/09/27 13:57:11.930335, 0] ../../source3/smbd/smbXsrv_session.c:1900(smbXsrv_session_logoff)
Sep 27 13:57:11 bachata smbd[1280196]: smbXsrv_session_logoff: smbXsrv_session_logoff(0x27f07adc): smb2srv_tcon_disconnect_all() failed: NT_STATUS_INTERNAL_ERROR
Sep 27 13:57:11 bachata smbd[1280196]: [2026/09/27 13:57:11.930413, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done)
Sep 27 13:57:11 bachata smbd[1280196]: smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(670071516) failed: NT_STATUS_INTERNAL_ERROR
== biggulp.cs.umd.edu (3 distinct, 8 total) ==
Sep 27 13:05:44 biggulp.cs.umd.edu sshd-session[471182]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 27 13:05:45 biggulp.cs.umd.edu sshd-session[471182]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 27 13:05:45 biggulp.cs.umd.edu sshd-session[471180]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== cheezit.cs.umd.edu (2 distinct, 2 total) ==
Sep 27 13:59:39 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 27 13:59:39 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
== idm00 (1 distinct, 1 total) ==
Sep 27 13:54:10 idm00 named[4166701]: client @0x7f11a4046478 10.73.240.42#56327: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 13:39:27 idmp0 named[1598691]: client @0x7f2d1c051bb8 10.73.240.43#62557: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 2 total) ==
Sep 27 13:13:08 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 13:13:03 newhonors2 dhcpcd[3231336]: dhcpcd is not running [x24]
== ntop00 (80 distinct, 116701 total) ==
Sep 27 13:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 27 13: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 13:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1282) ***
Sep 27 13:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1282, QN: 0/63, ET: 0) ***
Sep 27 13:05: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 ] [x55641]
Sep 27 13:05: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 ] [x52811]
Sep 27 13:05: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 ] [x7664]
Sep 27 13:05: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 ] [x233]
Sep 27 13:05: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 ] [x233]
Sep 27 13:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 27 13: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 13:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1284) ***
Sep 27 13:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1284, QN: 0/10286, ET: 0) ***
Sep 27 13:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1284) ***
Sep 27 13:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1284, QN: 0/69, ET: 0) ***
Sep 27 13:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1285) ***
Sep 27 13:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1285) ***
Sep 27 13:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1285, QN: 71/71, ET: 0) ***
Sep 27 13:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1285, QN: 10063/10063, ET: 0) ***
Sep 27 13:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1286) ***
Sep 27 13:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1286, QN: 0/69, ET: 0) ***
Sep 27 13:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1286) ***
Sep 27 13:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1286, QN: 0/9919, ET: 0) ***
Sep 27 13:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1288) ***
Sep 27 13:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1288, QN: 0/58, ET: 0) ***
Sep 27 13:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1288) ***
Sep 27 13:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1288, QN: 0/9092, ET: 0) ***
Sep 27 13:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1289) ***
Sep 27 13:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1289, QN: 8489/8489, ET: 0) ***
Sep 27 13:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1289) ***
... 50 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 13:09:09 outbound00.cs.umd.edu python3[257906]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 13:13:06 outbound01.cs.umd.edu python3[2520714]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[714998]: link_config: could not get ethtool features for vethb90006d
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[714998]: Could not set offload features of vethb90006d: No such device
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715076]: Could not generate persistent MAC address for veth8d1ceac: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715077]: Could not generate persistent MAC address for veth1749b4b: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715080]: Could not generate persistent MAC address for veth8e86e42: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715081]: Could not generate persistent MAC address for vethc09e3a6: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715104]: Could not generate persistent MAC address for veth5572137: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715105]: Could not generate persistent MAC address for veth7dd3678: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715123]: Could not generate persistent MAC address for vetha759b7f: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715115]: Could not generate persistent MAC address for vethc4340e8: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715110]: Could not generate persistent MAC address for vethb0bfccf: No such file or directory
Sep 27 13:07:06 sentry-docker00.cs.umd.edu systemd-udevd[715104]: Could not generate persistent MAC address for vethffb84ef: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724685]: Could not generate persistent MAC address for veth4b918f2: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724686]: Could not generate persistent MAC address for veth401069c: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724689]: Could not generate persistent MAC address for veth010ed13: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724706]: Could not generate persistent MAC address for veth7ead45a: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724769]: Could not generate persistent MAC address for veth3e1165c: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724770]: Could not generate persistent MAC address for veth5654264: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724788]: Could not generate persistent MAC address for veth11ceaf2: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724809]: Could not generate persistent MAC address for veth55ae3a4: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724805]: Could not generate persistent MAC address for vethafd8b0b: No such file or directory
Sep 27 13:27:15 sentry-docker00.cs.umd.edu systemd-udevd[724811]: Could not generate persistent MAC address for vethbd4c041: No such file or directory
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734088]: link_config: could not get ethtool features for veth010ed13
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734088]: Could not set offload features of veth010ed13: No such device
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734183]: link_config: could not get ethtool features for vethafd8b0b
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734183]: Could not set offload features of vethafd8b0b: No such device
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734211]: Could not generate persistent MAC address for veth3ce0650: No such file or directory
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734212]: Could not generate persistent MAC address for veth10f78a8: No such file or directory
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734215]: Could not generate persistent MAC address for veth15d7ba0: No such file or directory
Sep 27 13:47:23 sentry-docker00.cs.umd.edu systemd-udevd[734216]: Could not generate persistent MAC address for vethbfc154c: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 13: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 13: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 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 13: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 13: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 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (12 distinct, 12 total) ==
Sep 27 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TDruh3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 27 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TDruh3. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 27 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 13:06:45 submit26-b9-f3 setroubleshoot[3700875]: 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 14:03:53 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 27 14:03:55 submit26-b9-f3 systemd-coredump[3712544]: Process 3712541 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3712541:#012#0 0x00007f436388d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f436383fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f4363829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f436382a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f436391d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f436391e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
Sep 27 14:03:55 submit26-b9-f3 systemd-coredump[3712554]: Process 3712551 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3712551:#012#0 0x00007f9ae1e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f9ae1e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f9ae1e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f9ae1e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f9ae1f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f9ae1f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018f6 main (grades + 0x18f6)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 27 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: 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 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: 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 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: 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
Sep 27 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.vg2uYB/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 27 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: 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
Sep 27 13:24:48 submit26-b9-f4 setroubleshoot[2708268]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.vg2uYB. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 27 13:24:49 submit26-b9-f4 setroubleshoot[2708268]: 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 13:24:49 submit26-b9-f4 setroubleshoot[2708268]: 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 13:24:49 submit26-b9-f4 setroubleshoot[2708268]: 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.5087s
Status : exited 0
Output :
Syslog digest — 2026-09-27 13:05 EDT
Processed 120,255 lines, filtered 1,789 (1%). 118,466 unknown (140 distinct) from 14 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 13:03:00 b0b02.cs.umd.edu rustdesk[1707664]: cannot open display:
== biggulp.cs.umd.edu (3 distinct, 8 total) ==
Sep 27 12:05:27 biggulp.cs.umd.edu sshd-session[461214]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 27 12:05:28 biggulp.cs.umd.edu sshd-session[461214]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 27 12:05:28 biggulp.cs.umd.edu sshd-session[461212]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== idm00 (1 distinct, 1 total) ==
Sep 27 12:54:10 idm00 named[4166701]: client @0x7f11a00383f8 10.73.240.42#50093: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 12:39:27 idmp0 named[1598691]: client @0x7f2d50005288 10.73.240.43#62788: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 27 12:18:10 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 12:13:03 newhonors2 dhcpcd[3229492]: dhcpcd is not running [x24]
== ntop00 (74 distinct, 118327 total) ==
Sep 27 12:08:30 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 ] [x56447]
Sep 27 12:08:30 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 ] [x53635]
Sep 27 12:08:30 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 12:08:30 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 12:08:30 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 ] [x7659]
Sep 27 12:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 27 12:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x10]
Sep 27 12:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1260) ***
Sep 27 12:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1260, QN: 0/3701, ET: 0) ***
Sep 27 12:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 27 12:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x10]
Sep 27 12:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1260) ***
Sep 27 12:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1260, QN: 0/45, ET: 0) ***
Sep 27 12:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1261) ***
Sep 27 12:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1261, QN: 51/51, ET: 0) ***
Sep 27 12:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1261) ***
Sep 27 12:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1261, QN: 4806/4806, ET: 0) ***
Sep 27 12:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1262) ***
Sep 27 12:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1262, QN: 0/64, ET: 0) ***
Sep 27 12:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1264) ***
Sep 27 12:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1264, QN: 0/9120, ET: 0) ***
Sep 27 12:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1264) ***
Sep 27 12:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1264, QN: 0/64, ET: 0) ***
Sep 27 12:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1265) ***
Sep 27 12:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1265) ***
Sep 27 12:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1265, QN: 65/65, ET: 0) ***
Sep 27 12:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1265, QN: 9258/9258, ET: 0) ***
Sep 27 12:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1268) ***
Sep 27 12:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1268, QN: 0/10313, ET: 0) ***
Sep 27 12:30:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1268) ***
... 44 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 12:09:09 outbound00.cs.umd.edu python3[243977]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 12:13:06 outbound01.cs.umd.edu python3[2506708]: ldapdb [x6]
== portal (3 distinct, 3 total) ==
Sep 27 12:35:46 portal hello[81422]: [::ffff:10.89.1.2]:41210: response:200
Sep 27 12:35:46 portal hello[81422]: [::ffff:10.89.1.2]:41222: response:404
Sep 27 12:35:49 portal hello[81422]: [::ffff:10.89.1.2]:45352: response:304
== quiss (3 distinct, 4 total) ==
Sep 27 12:24:47 quiss falcon-sensor-bpf[1301]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 27 12:24:47 quiss falcon-sensor-bpf[1301]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 27 12:32:11 quiss nautilus[1581193]: Attempted to add a non-existent file to the view. [x2]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686838]: link_config: could not get ethtool features for vethfbaa0f8
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686838]: Could not set offload features of vethfbaa0f8: No such device
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686872]: Could not generate persistent MAC address for veth580a681: No such file or directory
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686873]: Could not generate persistent MAC address for veth139a9da: No such file or directory
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686876]: Could not generate persistent MAC address for vetha0fddfc: No such file or directory
Sep 27 12:06:41 sentry-docker00.cs.umd.edu systemd-udevd[686877]: Could not generate persistent MAC address for vethadcf4b6: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686899]: Could not generate persistent MAC address for vethb0e2f74: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686882]: Could not generate persistent MAC address for vethb8a3d4f: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686876]: Could not generate persistent MAC address for veth48b746c: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686893]: Could not generate persistent MAC address for vethcde64e1: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686899]: Could not generate persistent MAC address for vethbc04690: No such file or directory
Sep 27 12:06:42 sentry-docker00.cs.umd.edu systemd-udevd[686893]: Could not generate persistent MAC address for vethc98b8cc: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696324]: Could not generate persistent MAC address for vethb2ba6b3: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696325]: Could not generate persistent MAC address for veth18e68f7: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696328]: Could not generate persistent MAC address for veth05de4ed: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696329]: Could not generate persistent MAC address for vetha72822a: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696338]: Could not generate persistent MAC address for veth96ec9d8: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696339]: Could not generate persistent MAC address for veth3f56fea: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696343]: Could not generate persistent MAC address for vethc915e89: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696328]: Could not generate persistent MAC address for veth5aa049b: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696338]: Could not generate persistent MAC address for veth559bf7d: No such file or directory
Sep 27 12:26:50 sentry-docker00.cs.umd.edu systemd-udevd[696336]: Could not generate persistent MAC address for veth790f457: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705649]: link_config: could not get ethtool features for veth96ec9d8
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705649]: Could not set offload features of veth96ec9d8: No such device
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705678]: Could not generate persistent MAC address for vethd69acea: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705679]: Could not generate persistent MAC address for vethe344090: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705697]: Could not generate persistent MAC address for veth128d608: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705683]: Could not generate persistent MAC address for veth0344936: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705692]: Could not generate persistent MAC address for veth212809e: No such file or directory
Sep 27 12:46:58 sentry-docker00.cs.umd.edu systemd-udevd[705702]: Could not generate persistent MAC address for vethefebf2c: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 12: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 12: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 12:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 12: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 12: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 12:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 12:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 9 total) ==
Sep 27 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.9C3WFj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 27 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.9C3WFj. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 27 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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 12:22:00 submit26-b9-fclone setroubleshoot[587171]: 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.5296s
Status : exited 0
Output :
Syslog digest — 2026-09-27 12:05 EDT
Processed 120,090 lines, filtered 1,262 (1%). 118,828 unknown (122 distinct) from 14 host(s).
== abadi-computer (1 distinct, 1 total) ==
Sep 27 12:00:12 abadi-computer kernel: kauditd_printk_skb: 2 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 27 12:02:56 b0b02.cs.umd.edu rustdesk[1692308]: cannot open display:
== biggulp.cs.umd.edu (3 distinct, 8 total) ==
Sep 27 11:05:17 biggulp.cs.umd.edu sshd-session[450289]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 27 11:05:18 biggulp.cs.umd.edu sshd-session[450289]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 27 11:05:18 biggulp.cs.umd.edu sshd-session[450287]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== clone-submit9 (3 distinct, 3 total) ==
Sep 27 11:41:34 clone-submit9 sudo[1287286]: pugh : a password is required ; PWD=/home/pugh ; USER=root ; COMMAND=/bin/true
Sep 27 11:48:42 clone-submit9 sudo[1288303]: pugh : a password is required ; PWD=/home/pugh ; USER=sbuser ; COMMAND=/bin/whoami
Sep 27 11:48:42 clone-submit9 sudo[1288246]: pugh : a password is required ; PWD=/home/pugh ; USER=sbuser ; COMMAND=/bin/ls /export/home/sbuser/apache-tomcat/webapps
== idm00 (1 distinct, 1 total) ==
Sep 27 11:54:10 idm00 named[4166701]: client @0x7f11a406bb48 10.73.240.42#56896: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 27 11:39:27 idmp0 named[1598691]: client @0x7f2d5002e408 10.73.240.43#54880: update '73.10.in-addr.arpa/IN' denied
== irb2156 (1 distinct, 1 total) ==
Sep 27 11:56:11 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 128.8.74.3.
== itmon02 (1 distinct, 3 total) ==
Sep 27 11:08:38 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 27 11:13:02 newhonors2 dhcpcd[3227645]: dhcpcd is not running [x24]
== ntop00 (62 distinct, 118697 total) ==
Sep 27 11:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1235) ***
Sep 27 11:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1235, QN: 63/63, ET: 0) ***
Sep 27 11:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1235) ***
Sep 27 11:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1235, QN: 5336/5336, ET: 0) ***
Sep 27 11:08:01 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 ] [x7955]
Sep 27 11:08:01 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 ] [x56576]
Sep 27 11:08:01 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 ] [x53609]
Sep 27 11:08: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 11:08: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 11:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 11: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 11:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1236) ***
Sep 27 11:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1236, QN: 0/53, ET: 0) ***
Sep 27 11:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 27 11: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 11:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1236) ***
Sep 27 11:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1236, QN: 0/5293, ET: 0) ***
Sep 27 11:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1237) ***
Sep 27 11:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1237, QN: 52/52, ET: 0) ***
Sep 27 11:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1237) ***
Sep 27 11:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1237, QN: 5063/5063, ET: 0) ***
Sep 27 11:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1240) ***
Sep 27 11:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1240, QN: 0/5053, ET: 0) ***
Sep 27 11:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1240) ***
Sep 27 11:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1240, QN: 0/67, ET: 0) ***
Sep 27 11:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 1241) ***
Sep 27 11:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 1241, QN: 5118/5118, ET: 0) ***
Sep 27 11:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 1241) ***
Sep 27 11:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 1241, QN: 54/54, ET: 0) ***
Sep 27 11:24: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]
... 32 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 11:09:08 outbound00.cs.umd.edu python3[230019]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 27 11:13:07 outbound01.cs.umd.edu python3[2492741]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658627]: Could not generate persistent MAC address for vethcfc97a9: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658628]: Could not generate persistent MAC address for vethb66980c: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658631]: Could not generate persistent MAC address for veth9eb313d: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658653]: Could not generate persistent MAC address for veth2b69af3: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658648]: Could not generate persistent MAC address for veth34e0378: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658639]: Could not generate persistent MAC address for veth744b240: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658659]: Could not generate persistent MAC address for veth64991c8: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658660]: Could not generate persistent MAC address for veth5e64bc7: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658665]: Could not generate persistent MAC address for vethb0c3f1e: No such file or directory
Sep 27 11:06:17 sentry-docker00.cs.umd.edu systemd-udevd[658674]: Could not generate persistent MAC address for veth9d9d555: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668026]: link_config: could not get ethtool features for veth9d9d555
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668026]: Could not set offload features of veth9d9d555: No such device
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668061]: Could not generate persistent MAC address for veth36dcef8: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668062]: Could not generate persistent MAC address for veth5a7ad3f: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668065]: Could not generate persistent MAC address for vethbcb04d4: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668066]: Could not generate persistent MAC address for veth247ab9d: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668082]: Could not generate persistent MAC address for veth7595b2c: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668071]: Could not generate persistent MAC address for veth8850f6b: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668083]: Could not generate persistent MAC address for vetha6ef54d: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668067]: Could not generate persistent MAC address for veth3777adc: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668071]: Could not generate persistent MAC address for veth015cbd9: No such file or directory
Sep 27 11:26:25 sentry-docker00.cs.umd.edu systemd-udevd[668082]: Could not generate persistent MAC address for vethc7a236a: No such file or directory
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677314]: link_config: could not get ethtool features for vethbcb04d4
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677314]: Could not set offload features of vethbcb04d4: No such device
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677415]: link_config: could not set ethtool features for vethc7a236a
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677415]: Could not set offload features of vethc7a236a: Operation not permitted
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677416]: link_config: could not get ethtool features for vetha6ef54d
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677416]: Could not set offload features of vetha6ef54d: No such device
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677443]: Could not generate persistent MAC address for veth0a6e234: No such file or directory
Sep 27 11:46:33 sentry-docker00.cs.umd.edu systemd-udevd[677444]: Could not generate persistent MAC address for veth5d7dd29: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 27 11: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 11: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 11:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 27 11: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 11: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 11:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 27 11: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.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