Command: /usr/local/sbin/syslog-digest.py
Time : 7.3507s
Status : exited 0
Output :
Syslog digest — 2026-09-26 15:05 EDT
Processed 118,324 lines, filtered 1,923 (1%). 116,401 unknown (169 distinct) from 21 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 15:01:39 b0b02.cs.umd.edu rustdesk[1370273]: cannot open display:
== biggulp.cs.umd.edu (5 distinct, 9 total) ==
Sep 26 14:24:46 biggulp.cs.umd.edu sshd-session[237506]: pam_access(sshd:auth): access denied for user `egolub' from `108.28.255.142' [x5]
Sep 26 14:28:26 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225
Sep 26 14:28:26 biggulp.cs.umd.edu falcon-sensor-bpf[834]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225
Sep 26 14:42:13 biggulp.cs.umd.edu sshd-session[241428]: Error in Duo login for 'egolub' from 108.28.255.142
Sep 26 14:42:13 biggulp.cs.umd.edu sshd-session[241426]: error: PAM: Authentication failure for egolub from 108.28.255.142
== galax (1 distinct, 1 total) ==
Sep 26 15:00:19 galax kernel: kauditd_printk_skb: 4 callbacks suppressed
== grosh (1 distinct, 1 total) ==
Sep 26 14:59:20 grosh kernel: snd_hda_codec_nvhdmi hdaudioC1D0: HDMI: pin NID 0x7 not registered
== idm00 (1 distinct, 1 total) ==
Sep 26 14:54:09 idm00 named[4166701]: client @0x7f11a40662f8 10.73.240.42#63072: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 14:39:27 idmp0 named[1598691]: client @0x7f2d34044a78 10.73.240.43#54378: update '73.10.in-addr.arpa/IN' denied
== inbound01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 14:05:37 inbound01.cs.umd.edu krb5_child[2296248]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 6 total) ==
Sep 26 14:13:23 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x6]
== lifepix (1 distinct, 1 total) ==
Sep 26 14:38:05 lifepix setroubleshoot[291129]: 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
== mcstic (1 distinct, 2 total) ==
Sep 26 14:44:08 mcstic krb5_child[1157870]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== munin (2 distinct, 2 total) ==
Sep 26 15:03:05 munin sudo[3987005]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 26 15:03:05 munin sudo[3987005]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== netman.cs.umd.edu (5 distinct, 18 total) ==
Sep 26 14:11:02 netman.cs.umd.edu krb5_child[1025053]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x10]
Sep 26 14:27:25 netman.cs.umd.edu krb5_child[1029755]: Preauthentication failed [x2]
Sep 26 14:30:38 netman.cs.umd.edu krb5_child[1030906]: Client 'test1(a)UMD.EDU' not found in Kerberos database [x2]
Sep 26 14:55:23 netman.cs.umd.edu krb5_child[1037495]: Client 'backup(a)UMD.EDU' not found in Kerberos database [x2]
Sep 26 14:58:57 netman.cs.umd.edu krb5_child[1038668]: Client 'elena(a)UMD.EDU' not found in Kerberos database [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 14:13:03 newhonors2 dhcpcd[3188336]: dhcpcd is not running [x24]
== ntop00 (83 distinct, 116228 total) ==
Sep 26 14:05:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x13]
Sep 26 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) [x13]
Sep 26 14:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 730) ***
Sep 26 14:05:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 730, QN: 0/8918, ET: 0) ***
Sep 26 14:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 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 26 14:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 730) ***
Sep 26 14:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 730, QN: 0/78, ET: 0) ***
Sep 26 14:05:07 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 ] [x7575]
Sep 26 14:05:07 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 ] [x55408]
Sep 26 14:05:07 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 ] [x52655]
Sep 26 14:05:07 ntop00 rsyslogd[1208]: file '/var/log/maillog'[15] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 14:05:07 ntop00 rsyslogd[1208]: action 'action-3-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x233]
Sep 26 14:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 732) ***
Sep 26 14:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 732, QN: 0/8829, ET: 0) ***
Sep 26 14:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 732) ***
Sep 26 14:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 732, QN: 0/47, ET: 0) ***
Sep 26 14:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 733) ***
Sep 26 14:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 733, QN: 52/52, ET: 0) ***
Sep 26 14:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 733) ***
Sep 26 14:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 733, QN: 8730/8730, ET: 0) ***
Sep 26 14:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 734) ***
Sep 26 14:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 734, QN: 0/8527, ET: 0) ***
Sep 26 14:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 734) ***
Sep 26 14:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 734, QN: 0/60, ET: 0) ***
Sep 26 14:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 736) ***
Sep 26 14:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 736, QN: 0/7944, ET: 0) ***
Sep 26 14:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 736) ***
Sep 26 14:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 736, QN: 0/73, ET: 0) ***
Sep 26 14:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 737) ***
... 53 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 14:09:09 outbound00.cs.umd.edu python3[4127285]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 14:13:07 outbound01.cs.umd.edu python3[2194110]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 14:17:40 sentry-docker00.cs.umd.edu systemd-udevd[69886]: link_config: could not get ethtool features for veth0866eb8
Sep 26 14:17:40 sentry-docker00.cs.umd.edu systemd-udevd[69886]: Could not set offload features of veth0866eb8: No such device
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69961]: Could not generate persistent MAC address for vethf4923ea: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69962]: Could not generate persistent MAC address for vethd9e0df0: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69965]: Could not generate persistent MAC address for vethc26df8d: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69966]: Could not generate persistent MAC address for vethf4cfeb8: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69990]: Could not generate persistent MAC address for veth56f4243: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69989]: Could not generate persistent MAC address for vetha83a895: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[70004]: Could not generate persistent MAC address for vetha7b0698: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[69995]: Could not generate persistent MAC address for veth1d96cc0: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[70001]: Could not generate persistent MAC address for vethebeced8: No such file or directory
Sep 26 14:17:41 sentry-docker00.cs.umd.edu systemd-udevd[70000]: Could not generate persistent MAC address for vethc0dce6a: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79231]: link_config: could not get ethtool features for vethf4923ea
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79231]: Could not set offload features of vethf4923ea: No such device
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79320]: Could not generate persistent MAC address for vethb9e1d7c: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79321]: Could not generate persistent MAC address for veth0ac0fc6: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79324]: Could not generate persistent MAC address for vethcad7364: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79325]: Could not generate persistent MAC address for vethdb80b39: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79332]: Could not generate persistent MAC address for vethac5aba7: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79341]: Could not generate persistent MAC address for vethdcedfa2: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79328]: Could not generate persistent MAC address for vethafe365a: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79338]: Could not generate persistent MAC address for vethbe202c3: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79438]: Could not generate persistent MAC address for vethbf4cbcd: No such file or directory
Sep 26 14:37:49 sentry-docker00.cs.umd.edu systemd-udevd[79434]: Could not generate persistent MAC address for veth79fc3a4: No such file or directory
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88723]: link_config: could not get ethtool features for vethafe365a
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88723]: Could not set offload features of vethafe365a: No such device
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88745]: Could not generate persistent MAC address for vethfe5e49a: No such file or directory
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88744]: Could not generate persistent MAC address for veth3bbc98c: No such file or directory
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88773]: Could not generate persistent MAC address for veth482b0d7: No such file or directory
Sep 26 14:57:57 sentry-docker00.cs.umd.edu systemd-udevd[88774]: Could not generate persistent MAC address for veth51a3407: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 26 14:56:31 soul krb5_child[979100]: Client 'admin(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 14:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 14:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 14:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iYKai3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iYKai3. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 14:25:57 submit26-b9-f1 setroubleshoot[3780720]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (9 distinct, 9 total) ==
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NlW90f/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NlW90f. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 14:06:51 submit26-b9-f2 setroubleshoot[2856522]: 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.6900s
Status : exited 0
Output :
Syslog digest — 2026-09-26 14:05 EDT
Processed 120,341 lines, filtered 1,421 (1%). 118,920 unknown (201 distinct) from 24 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 14:01:35 b0b02.cs.umd.edu rustdesk[1354998]: cannot open display:
== biggulp.cs.umd.edu (3 distinct, 8 total) ==
Sep 26 13:14:41 biggulp.cs.umd.edu sshd-session[226126]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 26 13:14:41 biggulp.cs.umd.edu sshd-session[226126]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 26 13:14:41 biggulp.cs.umd.edu sshd-session[226124]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 13:15:28 cheezit.cs.umd.edu sshd-session[3361302]: error: send_error: write: Connection reset by peer
== galax (4 distinct, 4 total) ==
Sep 26 13:51:55 galax systemd-sysv-generator[225203]: SysV service '/etc/init.d/openipmi' lacks a native systemd unit file, automatically generating a unit file for compatibility.
Sep 26 13:51:55 galax systemd-sysv-generator[225203]: Please update package to include a native systemd unit file.
Sep 26 13:51:55 galax systemd-sysv-generator[225203]: ! This compatibility logic is deprecated, expect removal soon. !
Sep 26 13:51:55 galax kernel: set_capacity_and_notify: 10 callbacks suppressed
== gle-dind00.cs.umd.edu (4 distinct, 4 total) ==
Sep 26 13:22:10 gle-dind00.cs.umd.edu systemd-udevd[3573701]: Could not generate persistent MAC address for veth01d2e3e: No such file or directory
Sep 26 13:22:10 gle-dind00.cs.umd.edu systemd-udevd[3573702]: Could not generate persistent MAC address for veth7f2a8e6: No such file or directory
Sep 26 13:22:11 gle-dind00.cs.umd.edu systemd-udevd[3573821]: Could not generate persistent MAC address for veth73f6f37: No such file or directory
Sep 26 13:22:11 gle-dind00.cs.umd.edu systemd-udevd[3573822]: Could not generate persistent MAC address for veth01a2fa8: No such file or directory
== gle-dind02.cs.umd.edu (22 distinct, 22 total) ==
Sep 26 13:22:14 gle-dind02.cs.umd.edu systemd-udevd[2941461]: Could not generate persistent MAC address for veth661e249: No such file or directory
Sep 26 13:22:14 gle-dind02.cs.umd.edu systemd-udevd[2941460]: Could not generate persistent MAC address for veth243365b: No such file or directory
Sep 26 13:22:15 gle-dind02.cs.umd.edu systemd-udevd[2941560]: Could not generate persistent MAC address for vethc99d6b0: No such file or directory
Sep 26 13:22:15 gle-dind02.cs.umd.edu systemd-udevd[2941561]: Could not generate persistent MAC address for veth84f3a15: No such file or directory
Sep 26 13:22:16 gle-dind02.cs.umd.edu systemd-udevd[2941654]: Could not generate persistent MAC address for vetha725b32: No such file or directory
Sep 26 13:22:16 gle-dind02.cs.umd.edu systemd-udevd[2941655]: Could not generate persistent MAC address for veth77e02b7: No such file or directory
Sep 26 13:22:17 gle-dind02.cs.umd.edu systemd-udevd[2941749]: Could not generate persistent MAC address for veth778c0de: No such file or directory
Sep 26 13:22:17 gle-dind02.cs.umd.edu systemd-udevd[2941750]: Could not generate persistent MAC address for veth339c35c: No such file or directory
Sep 26 13:22:17 gle-dind02.cs.umd.edu systemd-udevd[2941847]: Could not generate persistent MAC address for veth1e7d324: No such file or directory
Sep 26 13:22:17 gle-dind02.cs.umd.edu systemd-udevd[2941848]: Could not generate persistent MAC address for veth9e9b733: No such file or directory
Sep 26 13:22:19 gle-dind02.cs.umd.edu systemd-udevd[2942016]: Could not generate persistent MAC address for veth5a320cb: No such file or directory
Sep 26 13:22:19 gle-dind02.cs.umd.edu systemd-udevd[2942017]: Could not generate persistent MAC address for vethc4e8bd1: No such file or directory
Sep 26 13:22:20 gle-dind02.cs.umd.edu systemd-udevd[2942129]: Could not generate persistent MAC address for veth6ee4fb8: No such file or directory
Sep 26 13:22:20 gle-dind02.cs.umd.edu systemd-udevd[2942130]: Could not generate persistent MAC address for veth22a5469: No such file or directory
Sep 26 13:22:25 gle-dind02.cs.umd.edu systemd-udevd[2942307]: Could not generate persistent MAC address for veth7572660: No such file or directory
Sep 26 13:22:25 gle-dind02.cs.umd.edu systemd-udevd[2942308]: Could not generate persistent MAC address for veth2b87842: No such file or directory
Sep 26 13:22:25 gle-dind02.cs.umd.edu systemd-udevd[2942411]: Could not generate persistent MAC address for vetha9e00e4: No such file or directory
Sep 26 13:22:25 gle-dind02.cs.umd.edu systemd-udevd[2942412]: Could not generate persistent MAC address for vethe79ab5d: No such file or directory
Sep 26 13:22:26 gle-dind02.cs.umd.edu systemd-udevd[2942549]: Could not generate persistent MAC address for vethebb133e: No such file or directory
Sep 26 13:22:26 gle-dind02.cs.umd.edu systemd-udevd[2942550]: Could not generate persistent MAC address for vethb75f336: No such file or directory
Sep 26 13:22:27 gle-dind02.cs.umd.edu systemd-udevd[2942663]: Could not generate persistent MAC address for veth6ac6286: No such file or directory
Sep 26 13:22:27 gle-dind02.cs.umd.edu systemd-udevd[2942662]: Could not generate persistent MAC address for veth8bef590: No such file or directory
== helmsdeep (1 distinct, 1 total) ==
Sep 26 13:49:05 helmsdeep kernel: clocksource: timekeeping watchdog on CPU1: kvm-clock retried 1 times before success
== idm00 (1 distinct, 1 total) ==
Sep 26 13:54:09 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#50827: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 13:39:27 idmp0 named[1598691]: client @0x7f2d4001be78 10.73.240.43#56903: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (1 distinct, 4 total) ==
Sep 26 13:23:05 inbound00.cs.umd.edu krb5_child[73035]: Preauthentication failed [x4]
== inbound01.cs.umd.edu (1 distinct, 4 total) ==
Sep 26 13:24:19 inbound01.cs.umd.edu krb5_child[2285828]: Preauthentication failed [x4]
== itmon02 (1 distinct, 3 total) ==
Sep 26 13:13:07 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== munin (2 distinct, 2 total) ==
Sep 26 13:08:15 munin sudo[3946007]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 26 13:08:15 munin sudo[3946007]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== netman.cs.umd.edu (2 distinct, 12 total) ==
Sep 26 13:22:56 netman.cs.umd.edu krb5_child[1010715]: Preauthentication failed [x8]
Sep 26 13:57:39 netman.cs.umd.edu krb5_child[1020827]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 13:13:02 newhonors2 dhcpcd[3186493]: dhcpcd is not running [x24]
== ntop00 (80 distinct, 118704 total) ==
Sep 26 13:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x12]
Sep 26 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 26 13:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 706) ***
Sep 26 13:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 706, QN: 0/47, ET: 0) ***
Sep 26 13:05:07 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 ] [x7921]
Sep 26 13:05:07 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 ] [x56550]
Sep 26 13:05:07 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 ] [x53652]
Sep 26 13:05:07 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 ] [x231]
Sep 26 13:05:07 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 ] [x231]
Sep 26 13:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 708) ***
Sep 26 13:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 708, QN: 0/51, ET: 0) ***
Sep 26 13:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 26 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 26 13:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 708) ***
Sep 26 13:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 708, QN: 0/8680, ET: 0) ***
Sep 26 13:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 709) ***
Sep 26 13:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 709, QN: 63/63, ET: 0) ***
Sep 26 13:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 709) ***
Sep 26 13:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 709, QN: 9160/9160, ET: 0) ***
Sep 26 13:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 710) ***
Sep 26 13:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 710, QN: 0/9414, ET: 0) ***
Sep 26 13:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 710) ***
Sep 26 13:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 710, QN: 0/65, ET: 0) ***
Sep 26 13:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 712) ***
Sep 26 13:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 712, QN: 0/8378, ET: 0) ***
Sep 26 13:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 712) ***
Sep 26 13:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 712, QN: 0/77, ET: 0) ***
Sep 26 13:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 713) ***
Sep 26 13:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 713, QN: 8253/8253, ET: 0) ***
Sep 26 13:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 713) ***
... 50 more distinct messages not shown
== outbound00.cs.umd.edu (2 distinct, 10 total) ==
Sep 26 13:09:09 outbound00.cs.umd.edu python3[4113247]: ldapdb [x6]
Sep 26 13:22:35 outbound00.cs.umd.edu krb5_child[4116071]: Preauthentication failed [x4]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 13:13:07 outbound01.cs.umd.edu python3[2179994]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41384]: link_config: could not get ethtool features for veth68c38aa
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41384]: Could not set offload features of veth68c38aa: No such device
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41389]: link_config: could not get ethtool features for vetha8c21ee
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41389]: Could not set offload features of vetha8c21ee: No such device
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41415]: Could not generate persistent MAC address for veth14bc0d4: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41416]: Could not generate persistent MAC address for vetha268575: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41419]: Could not generate persistent MAC address for vethe592fd3: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41420]: Could not generate persistent MAC address for vethf6a0438: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41437]: Could not generate persistent MAC address for vethcd8342b: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41441]: Could not generate persistent MAC address for veth8ed1aa5: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41433]: Could not generate persistent MAC address for veth98b24c8: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41424]: Could not generate persistent MAC address for veth109520b: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41486]: Could not generate persistent MAC address for vetha9fab4c: No such file or directory
Sep 26 13:17:16 sentry-docker00.cs.umd.edu systemd-udevd[41488]: Could not generate persistent MAC address for veth20958c0: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51006]: link_config: could not set ethtool features for vetha9fab4c
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51006]: Could not set offload features of vetha9fab4c: Operation not permitted
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51033]: Could not generate persistent MAC address for veth0375f98: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51034]: Could not generate persistent MAC address for veth224f852: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51037]: Could not generate persistent MAC address for veth70b5c97: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51038]: Could not generate persistent MAC address for vethe629287: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51068]: Could not generate persistent MAC address for vethb2ecc66: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51070]: Could not generate persistent MAC address for veth52b0670: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51107]: Could not generate persistent MAC address for veth187917e: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51128]: Could not generate persistent MAC address for veth56c0946: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51150]: Could not generate persistent MAC address for vethed5f196: No such file or directory
Sep 26 13:37:24 sentry-docker00.cs.umd.edu systemd-udevd[51152]: Could not generate persistent MAC address for vethbbb2cb1: No such file or directory
Sep 26 13:57:32 sentry-docker00.cs.umd.edu systemd-udevd[60457]: link_config: could not get ethtool features for vethed5f196
Sep 26 13:57:32 sentry-docker00.cs.umd.edu systemd-udevd[60457]: Could not set offload features of vethed5f196: No such device
Sep 26 13:57:32 sentry-docker00.cs.umd.edu systemd-udevd[60487]: Could not generate persistent MAC address for vethc52d4e5: No such file or directory
Sep 26 13:57:32 sentry-docker00.cs.umd.edu systemd-udevd[60488]: Could not generate persistent MAC address for veth7add68f: No such file or directory
... 8 more distinct messages not shown
== soul (1 distinct, 3 total) ==
Sep 26 13:22:33 soul krb5_child[964364]: Preauthentication failed [x3]
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 13:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 13:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 13:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.W9YuKF/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.W9YuKF. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: 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 26 13:06:45 submit26-b9-f3 setroubleshoot[3539430]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (16 distinct, 17 total) ==
Sep 26 13:18:11 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 26 13:18:14 submit26-b9-f4 systemd-coredump[2592470]: Process 2592467 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2592467:#012#0 0x00007f5ef488d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f5ef483fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f5ef4829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f5ef482a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f5ef491d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f5ef491e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:18:14 submit26-b9-f4 systemd-coredump[2592480]: Process 2592477 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2592477:#012#0 0x00007f092c68d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f092c63fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f092c629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f092c62a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f092c71d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f092c71e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:18:20 submit26-b9-f4 systemd-coredump[2592697]: Process 2592694 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2592694:#012#0 0x00007ff30528d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007ff30523fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007ff305229873 abort (libc.so.6 + 0x29873)#012#3 0x00007ff30522a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007ff30531d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007ff30531e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:18:20 submit26-b9-f4 systemd-coredump[2592708]: Process 2592705 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2592705:#012#0 0x00007faa4288d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007faa4283fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007faa42829873 abort (libc.so.6 + 0x29873)#012#3 0x00007faa4282a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007faa4291d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007faa4291e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:23:14 submit26-b9-f4 systemd-coredump[2593017]: Process 2593014 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2593014:#012#0 0x00007f818e48d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f818e43fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f818e429873 abort (libc.so.6 + 0x29873)#012#3 0x00007f818e42a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f818e51d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f818e51e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:23:14 submit26-b9-f4 systemd-coredump[2593027]: Process 2593024 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2593024:#012#0 0x00007f2e9608d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f2e9603fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2e96029873 abort (libc.so.6 + 0x29873)#012#3 0x00007f2e9602a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f2e9611d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f2e9611e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lIbESD/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lIbESD. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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 26 13:24:48 submit26-b9-f4 setroubleshoot[2593453]: 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
== teaching-awards (1 distinct, 3 total) ==
Sep 26 13:23:36 teaching-awards krb5_child[1721327]: Preauthentication failed [x3]
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.4611s
Status : exited 0
Output :
Syslog digest — 2026-09-26 13:05 EDT
Processed 119,971 lines, filtered 2,281 (1%). 117,690 unknown (263 distinct) from 25 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 13:01:31 b0b02.cs.umd.edu rustdesk[1339809]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 2 total) ==
Sep 26 12:33:53 cheezit.cs.umd.edu sshd-session[3352056]: error: send_error: write: Connection reset by peer [x2]
== gle-dind00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 12:23:17 gle-dind00.cs.umd.edu systemd-udevd[3558649]: Could not generate persistent MAC address for veth0263bd0: No such file or directory
Sep 26 12:23:17 gle-dind00.cs.umd.edu systemd-udevd[3558651]: Could not generate persistent MAC address for veth1471c0c: No such file or directory
Sep 26 12:23:18 gle-dind00.cs.umd.edu systemd-udevd[3558752]: Could not generate persistent MAC address for veth2a432cf: No such file or directory
Sep 26 12:23:18 gle-dind00.cs.umd.edu systemd-udevd[3558753]: Could not generate persistent MAC address for veth75ab0ef: No such file or directory
Sep 26 12:23:19 gle-dind00.cs.umd.edu systemd-udevd[3558851]: Could not generate persistent MAC address for vethd05980d: No such file or directory
Sep 26 12:23:19 gle-dind00.cs.umd.edu systemd-udevd[3558852]: Could not generate persistent MAC address for veth00ffe3d: No such file or directory
Sep 26 12:23:20 gle-dind00.cs.umd.edu systemd-udevd[3558951]: Could not generate persistent MAC address for vethde2a5f9: No such file or directory
Sep 26 12:23:20 gle-dind00.cs.umd.edu systemd-udevd[3558952]: Could not generate persistent MAC address for veth05d09d7: No such file or directory
Sep 26 12:23:21 gle-dind00.cs.umd.edu systemd-udevd[3559050]: Could not generate persistent MAC address for veth3b0d9b1: No such file or directory
Sep 26 12:23:21 gle-dind00.cs.umd.edu systemd-udevd[3559051]: Could not generate persistent MAC address for veth7eb46e0: No such file or directory
Sep 26 12:23:22 gle-dind00.cs.umd.edu systemd-udevd[3559223]: Could not generate persistent MAC address for veth54f39ca: No such file or directory
Sep 26 12:23:22 gle-dind00.cs.umd.edu systemd-udevd[3559224]: Could not generate persistent MAC address for vethe86eee5: No such file or directory
Sep 26 12:23:23 gle-dind00.cs.umd.edu systemd-udevd[3559334]: Could not generate persistent MAC address for veth2bacb06: No such file or directory
Sep 26 12:23:23 gle-dind00.cs.umd.edu systemd-udevd[3559335]: Could not generate persistent MAC address for veth3520c35: No such file or directory
Sep 26 12:23:32 gle-dind00.cs.umd.edu systemd-udevd[3559506]: Could not generate persistent MAC address for veth0f8562a: No such file or directory
Sep 26 12:23:32 gle-dind00.cs.umd.edu systemd-udevd[3559507]: Could not generate persistent MAC address for vethb199ebd: No such file or directory
Sep 26 12:23:33 gle-dind00.cs.umd.edu systemd-udevd[3559611]: Could not generate persistent MAC address for vethca6c27b: No such file or directory
Sep 26 12:23:33 gle-dind00.cs.umd.edu systemd-udevd[3559612]: Could not generate persistent MAC address for vethd0a257b: No such file or directory
Sep 26 12:23:34 gle-dind00.cs.umd.edu systemd-udevd[3559727]: Could not generate persistent MAC address for veth8c7f125: No such file or directory
Sep 26 12:23:34 gle-dind00.cs.umd.edu systemd-udevd[3559728]: Could not generate persistent MAC address for veth6cd52b3: No such file or directory
Sep 26 12:23:35 gle-dind00.cs.umd.edu systemd-udevd[3559841]: Could not generate persistent MAC address for vethcfd500b: No such file or directory
Sep 26 12:23:35 gle-dind00.cs.umd.edu systemd-udevd[3559842]: Could not generate persistent MAC address for vetha818401: No such file or directory
Sep 26 12:25:18 gle-dind00.cs.umd.edu systemd-udevd[3560554]: Could not generate persistent MAC address for veth4598778: No such file or directory
Sep 26 12:25:18 gle-dind00.cs.umd.edu systemd-udevd[3560555]: Could not generate persistent MAC address for veth38c4dd1: No such file or directory
Sep 26 12:25:19 gle-dind00.cs.umd.edu systemd-udevd[3560654]: Could not generate persistent MAC address for veth4f328a8: No such file or directory
Sep 26 12:25:19 gle-dind00.cs.umd.edu systemd-udevd[3560655]: Could not generate persistent MAC address for veth58c161a: No such file or directory
Sep 26 12:25:20 gle-dind00.cs.umd.edu systemd-udevd[3560751]: Could not generate persistent MAC address for vethf289e4e: No such file or directory
Sep 26 12:25:20 gle-dind00.cs.umd.edu systemd-udevd[3560752]: Could not generate persistent MAC address for veth5c5b0a2: No such file or directory
Sep 26 12:25:21 gle-dind00.cs.umd.edu systemd-udevd[3560852]: Could not generate persistent MAC address for veth0f5f4c5: No such file or directory
Sep 26 12:25:21 gle-dind00.cs.umd.edu systemd-udevd[3560853]: Could not generate persistent MAC address for veth9b5f721: No such file or directory
... 4 more distinct messages not shown
== gle-dind02.cs.umd.edu (58 distinct, 58 total) ==
Sep 26 12:07:33 gle-dind02.cs.umd.edu systemd-udevd[2925828]: Could not generate persistent MAC address for veth1ee8d03: No such file or directory
Sep 26 12:07:33 gle-dind02.cs.umd.edu systemd-udevd[2925829]: Could not generate persistent MAC address for veth2393636: No such file or directory
Sep 26 12:07:34 gle-dind02.cs.umd.edu systemd-udevd[2925930]: Could not generate persistent MAC address for veth8824aca: No such file or directory
Sep 26 12:07:34 gle-dind02.cs.umd.edu systemd-udevd[2925928]: Could not generate persistent MAC address for vethfc77f0a: No such file or directory
Sep 26 12:07:35 gle-dind02.cs.umd.edu systemd-udevd[2926028]: Could not generate persistent MAC address for vethddbb91a: No such file or directory
Sep 26 12:07:35 gle-dind02.cs.umd.edu systemd-udevd[2926029]: Could not generate persistent MAC address for veth72d4aa4: No such file or directory
Sep 26 12:07:37 gle-dind02.cs.umd.edu systemd-udevd[2926160]: Could not generate persistent MAC address for vethef8fb86: No such file or directory
Sep 26 12:07:37 gle-dind02.cs.umd.edu systemd-udevd[2926161]: Could not generate persistent MAC address for vetha1ed8f8: No such file or directory
Sep 26 12:07:37 gle-dind02.cs.umd.edu systemd-udevd[2926258]: Could not generate persistent MAC address for veth8c1a511: No such file or directory
Sep 26 12:07:37 gle-dind02.cs.umd.edu systemd-udevd[2926259]: Could not generate persistent MAC address for veth1b1cca6: No such file or directory
Sep 26 12:07:39 gle-dind02.cs.umd.edu systemd-udevd[2926429]: Could not generate persistent MAC address for vethfe8b61b: No such file or directory
Sep 26 12:07:39 gle-dind02.cs.umd.edu systemd-udevd[2926428]: Could not generate persistent MAC address for veth6334895: No such file or directory
Sep 26 12:07:40 gle-dind02.cs.umd.edu systemd-udevd[2926539]: Could not generate persistent MAC address for veth390e34f: No such file or directory
Sep 26 12:07:40 gle-dind02.cs.umd.edu systemd-udevd[2926541]: Could not generate persistent MAC address for veth4a0fd81: No such file or directory
Sep 26 12:07:44 gle-dind02.cs.umd.edu systemd-udevd[2926662]: Could not generate persistent MAC address for vethe4e667a: No such file or directory
Sep 26 12:07:44 gle-dind02.cs.umd.edu systemd-udevd[2926663]: Could not generate persistent MAC address for veth0b97a51: No such file or directory
Sep 26 12:07:45 gle-dind02.cs.umd.edu systemd-udevd[2926775]: Could not generate persistent MAC address for veth01c04a3: No such file or directory
Sep 26 12:07:45 gle-dind02.cs.umd.edu systemd-udevd[2926776]: Could not generate persistent MAC address for veth96c9bf9: No such file or directory
Sep 26 12:23:05 gle-dind02.cs.umd.edu systemd-udevd[2929206]: Could not generate persistent MAC address for veth337f24d: No such file or directory
Sep 26 12:23:05 gle-dind02.cs.umd.edu systemd-udevd[2929207]: Could not generate persistent MAC address for veth5e03ebf: No such file or directory
Sep 26 12:23:06 gle-dind02.cs.umd.edu systemd-udevd[2929308]: Could not generate persistent MAC address for vethacbe9c8: No such file or directory
Sep 26 12:23:06 gle-dind02.cs.umd.edu systemd-udevd[2929309]: Could not generate persistent MAC address for vethf5d234e: No such file or directory
Sep 26 12:23:07 gle-dind02.cs.umd.edu systemd-udevd[2929408]: Could not generate persistent MAC address for veth388575b: No such file or directory
Sep 26 12:23:07 gle-dind02.cs.umd.edu systemd-udevd[2929409]: Could not generate persistent MAC address for veth51f977a: No such file or directory
Sep 26 12:23:08 gle-dind02.cs.umd.edu systemd-udevd[2929505]: Could not generate persistent MAC address for veth7a7394b: No such file or directory
Sep 26 12:23:08 gle-dind02.cs.umd.edu systemd-udevd[2929506]: Could not generate persistent MAC address for vethf06d615: No such file or directory
Sep 26 12:23:08 gle-dind02.cs.umd.edu systemd-udevd[2929603]: Could not generate persistent MAC address for veth4e27d99: No such file or directory
Sep 26 12:23:08 gle-dind02.cs.umd.edu systemd-udevd[2929604]: Could not generate persistent MAC address for vethcfede4c: No such file or directory
Sep 26 12:23:10 gle-dind02.cs.umd.edu systemd-udevd[2929776]: Could not generate persistent MAC address for veth3dd3063: No such file or directory
Sep 26 12:23:10 gle-dind02.cs.umd.edu systemd-udevd[2929777]: Could not generate persistent MAC address for veth5ab14b8: No such file or directory
... 28 more distinct messages not shown
== idm00 (1 distinct, 1 total) ==
Sep 26 12:54:09 idm00 named[4166701]: client @0x7f11a401d728 10.73.240.42#53054: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 12:39:27 idmp0 named[1598691]: client @0x7f2d40027998 10.73.240.43#56832: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (2 distinct, 2 total) ==
Sep 26 12:34:46 inbound00.cs.umd.edu krb5_child[62035]: Preauthentication failed
Sep 26 12:54:22 inbound00.cs.umd.edu krb5_child[66087]: Client 'george(a)UMD.EDU' not found in Kerberos database
== inbound01.cs.umd.edu (4 distinct, 10 total) ==
Sep 26 12:13:43 inbound01.cs.umd.edu krb5_child[2269392]: Preauthentication failed [x5]
Sep 26 12:24:25 inbound01.cs.umd.edu krb5_child[2271519]: Client 'gitlab(a)UMD.EDU' not found in Kerberos database
Sep 26 12:25:00 inbound01.cs.umd.edu krb5_child[2271684]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x3]
Sep 26 12:55:34 inbound01.cs.umd.edu krb5_child[2279551]: Client 'george(a)UMD.EDU' not found in Kerberos database
== itmon02 (1 distinct, 5 total) ==
Sep 26 12:13:41 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== krispykreme.cs.umd.edu (3 distinct, 8 total) ==
Sep 26 12:14:23 krispykreme.cs.umd.edu sshd-session[2830490]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4]
Sep 26 12:14:24 krispykreme.cs.umd.edu sshd-session[2830490]: Error in Duo login for 'larry' from 71.191.93.172 [x2]
Sep 26 12:14:24 krispykreme.cs.umd.edu sshd-session[2830462]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2]
== munin (2 distinct, 6 total) ==
Sep 26 12:23:39 munin sudo[3928646]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 26 12:23:39 munin sudo[3928646]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== netman.cs.umd.edu (2 distinct, 4 total) ==
Sep 26 12:34:38 netman.cs.umd.edu krb5_child[997324]: Preauthentication failed [x2]
Sep 26 12:54:13 netman.cs.umd.edu krb5_child[1002273]: Client 'george(a)UMD.EDU' not found in Kerberos database [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 12:13:03 newhonors2 dhcpcd[3184652]: dhcpcd is not running [x24]
== ntop00 (76 distinct, 117412 total) ==
Sep 26 12:08:37 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 ] [x55965]
Sep 26 12:08:37 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 ] [x53115]
Sep 26 12:08:37 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 26 12:08:37 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 26 12:08:37 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 ] [x7761]
Sep 26 12:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x11]
Sep 26 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) [x11]
Sep 26 12:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 684) ***
Sep 26 12:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 684, QN: 0/6394, ET: 0) ***
Sep 26 12:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 26 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 26 12:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 684) ***
Sep 26 12:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 684, QN: 0/58, ET: 0) ***
Sep 26 12:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 685) ***
Sep 26 12:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 685, QN: 7051/7051, ET: 0) ***
Sep 26 12:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 685) ***
Sep 26 12:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 685, QN: 58/58, ET: 0) ***
Sep 26 12:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 686) ***
Sep 26 12:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 686, QN: 0/8748, ET: 0) ***
Sep 26 12:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 686) ***
Sep 26 12:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 686, QN: 0/65, ET: 0) ***
Sep 26 12:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 688) ***
Sep 26 12:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 688, QN: 0/10611, ET: 0) ***
Sep 26 12:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 688) ***
Sep 26 12:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 688, QN: 0/66, ET: 0) ***
Sep 26 12:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 689) ***
Sep 26 12:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 689, QN: 11959/11959, ET: 0) ***
Sep 26 12:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 689) ***
Sep 26 12:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 689, QN: 72/72, ET: 0) ***
Sep 26 12:24:03 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x3]
... 46 more distinct messages not shown
== outbound00.cs.umd.edu (3 distinct, 9 total) ==
Sep 26 12:09:09 outbound00.cs.umd.edu python3[4099222]: ldapdb [x6]
Sep 26 12:34:18 outbound00.cs.umd.edu krb5_child[4105216]: Preauthentication failed [x2]
Sep 26 12:53:53 outbound00.cs.umd.edu krb5_child[4109203]: Client 'george(a)UMD.EDU' not found in Kerberos database
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 26 12:13:06 outbound01.cs.umd.edu python3[2165949]: ldapdb [x6]
Sep 26 12:53:08 outbound01.cs.umd.edu krb5_child[2175090]: Preauthentication failed
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13118]: link_config: could not get ethtool features for veth1032968
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13118]: Could not set offload features of veth1032968: No such device
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13151]: Could not generate persistent MAC address for vethd189fae: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13152]: Could not generate persistent MAC address for vethc951281: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13155]: Could not generate persistent MAC address for veth3839ac7: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13156]: Could not generate persistent MAC address for veth0e84846: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13177]: Could not generate persistent MAC address for vethb68a178: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13159]: Could not generate persistent MAC address for vethe64e369: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13181]: Could not generate persistent MAC address for vetha48fa56: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13182]: Could not generate persistent MAC address for veth7578466: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13193]: Could not generate persistent MAC address for vethcef491a: No such file or directory
Sep 26 12:16:51 sentry-docker00.cs.umd.edu systemd-udevd[13221]: Could not generate persistent MAC address for vethfe5bf21: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22536]: link_config: could not get ethtool features for vethcef491a
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22536]: Could not set offload features of vethcef491a: No such device
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22587]: Could not generate persistent MAC address for veth33f3ceb: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22588]: Could not generate persistent MAC address for vethad388a5: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22591]: Could not generate persistent MAC address for vethb267b7b: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22613]: Could not generate persistent MAC address for vethda2e7c1: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22587]: Could not generate persistent MAC address for vethedafe69: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22602]: Could not generate persistent MAC address for veth6ee640a: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22617]: Could not generate persistent MAC address for vethd677941: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22618]: Could not generate persistent MAC address for vethe4ade9f: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22617]: Could not generate persistent MAC address for vethe5d6359: No such file or directory
Sep 26 12:36:59 sentry-docker00.cs.umd.edu systemd-udevd[22632]: Could not generate persistent MAC address for veth49c87de: No such file or directory
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[31976]: link_config: could not get ethtool features for vethb267b7b
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[31976]: Could not set offload features of vethb267b7b: No such device
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[32002]: Could not generate persistent MAC address for vethe24f835: No such file or directory
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[32001]: Could not generate persistent MAC address for vethe0d7ae3: No such file or directory
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[32005]: Could not generate persistent MAC address for vethd914895: No such file or directory
Sep 26 12:57:07 sentry-docker00.cs.umd.edu systemd-udevd[32010]: Could not generate persistent MAC address for vethb5d2a50: No such file or directory
... 6 more distinct messages not shown
== soul (1 distinct, 1 total) ==
Sep 26 12:53:52 soul krb5_child[959660]: Client 'george(a)UMD.EDU' not found in Kerberos database
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 12:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 12:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 12:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (5 distinct, 6 total) ==
Sep 26 12:58:09 submit26-b9-f1 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 26 12:58:11 submit26-b9-f1 systemd-coredump[3771546]: Process 3771543 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3771543:#012#0 0x00007fad66a8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fad66a3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fad66a29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fad66a2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fad66b1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fad66b1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:58:11 submit26-b9-f1 systemd-coredump[3771557]: Process 3771553 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3771553:#012#0 0x00007f55b368d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f55b363fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f55b3629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f55b362a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f55b371d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f55b371e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:03:10 submit26-b9-f1 systemd-coredump[3771878]: Process 3771875 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3771875:#012#0 0x00007fc1a188d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fc1a183fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fc1a1829873 abort (libc.so.6 + 0x29873)#012#3 0x00007fc1a182a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fc1a191d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fc1a191e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 13:03:10 submit26-b9-f1 systemd-coredump[3771889]: Process 3771886 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3771886:#012#0 0x00007fbf6dc8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fbf6dc3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fbf6dc29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fbf6dc2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fbf6dd1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fbf6dd1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f2 (3 distinct, 3 total) ==
Sep 26 12:42:34 submit26-b9-f2 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 26 12:42:36 submit26-b9-f2 systemd-coredump[2851451]: Process 2851448 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2851448:#012#0 0x00007f4cfd88d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f4cfd83fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f4cfd829873 abort (libc.so.6 + 0x29873)#012#3 0x00007f4cfd82a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f4cfd91d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f4cfd91e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:42:36 submit26-b9-f2 systemd-coredump[2851462]: Process 2851459 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2851459:#012#0 0x00007f727c28d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f727c23fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f727c229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f727c22a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f727c31d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f727c31e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f3 (5 distinct, 6 total) ==
Sep 26 12:37:49 submit26-b9-f3 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL [x2]
Sep 26 12:37:51 submit26-b9-f3 systemd-coredump[3536098]: Process 3536095 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3536095:#012#0 0x00007f1ce6e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f1ce6e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f1ce6e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f1ce6e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f1ce6f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f1ce6f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:37:51 submit26-b9-f3 systemd-coredump[3536108]: Process 3536105 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3536105:#012#0 0x00007f2d0628d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f2d0623fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f2d06229873 abort (libc.so.6 + 0x29873)#012#3 0x00007f2d0622a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f2d0631d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f2d0631e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:58:08 submit26-b9-f3 systemd-coredump[3538817]: Process 3538814 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3538814:#012#0 0x00007fd7efa8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007fd7efa3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007fd7efa29873 abort (libc.so.6 + 0x29873)#012#3 0x00007fd7efa2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007fd7efb1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007fd7efb1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:58:09 submit26-b9-f3 systemd-coredump[3538828]: Process 3538824 (grades) of user 1001 dumped core.#012#012Stack trace of thread 3538824:#012#0 0x00007f880aa8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f880aa3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f880aa29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f880aa2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f880ab1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f880ab1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-f4 (3 distinct, 3 total) ==
Sep 26 12:37:09 submit26-b9-f4 systemd[1]: user(a)1001.service: Main process exited, code=killed, status=9/KILL
Sep 26 12:37:11 submit26-b9-f4 systemd-coredump[2588940]: Process 2588937 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2588937:#012#0 0x00007f6724e8d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f6724e3fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f6724e29873 abort (libc.so.6 + 0x29873)#012#3 0x00007f6724e2a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f6724f1d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f6724f1e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
Sep 26 12:37:12 submit26-b9-f4 systemd-coredump[2588950]: Process 2588947 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2588947:#012#0 0x00007f63b968d02c __pthread_kill_implementation (libc.so.6 + 0x8d02c)#012#1 0x00007f63b963fb86 raise (libc.so.6 + 0x3fb86)#012#2 0x00007f63b9629873 abort (libc.so.6 + 0x29873)#012#3 0x00007f63b962a1b2 __libc_message.cold (libc.so.6 + 0x2a1b2)#012#4 0x00007f63b971d19b __fortify_fail (libc.so.6 + 0x11d19b)#012#5 0x00007f63b971e416 __stack_chk_fail (libc.so.6 + 0x11e416)#012#6 0x00000000004018fa main (grades + 0x18fa)#012#7 0x0000000000000002 n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64
== submit26-b9-fclone (10 distinct, 12 total) ==
Sep 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: 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 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: 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 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: 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 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.S4hvKq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
Sep 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 [x2]
Sep 26 12:21:59 submit26-b9-fclone setroubleshoot[528769]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.S4hvKq. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 12:22:00 submit26-b9-fclone setroubleshoot[528769]: 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 26 12:22:00 submit26-b9-fclone setroubleshoot[528769]: 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 [x2]
Sep 26 12:22:00 submit26-b9-fclone setroubleshoot[528769]: 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
Sep 26 12:22:00 submit26-b9-fclone setroubleshoot[528769]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.4NSXDU/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc
== teaching-awards (1 distinct, 1 total) ==
Sep 26 12:54:51 teaching-awards krb5_child[1719593]: Client 'george(a)UMD.EDU' not found in Kerberos database
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5258s
Status : exited 0
Output :
Syslog digest — 2026-09-26 12:05 EDT
Processed 120,314 lines, filtered 1,458 (1%). 118,856 unknown (129 distinct) from 13 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 12:01:26 b0b02.cs.umd.edu rustdesk[1324452]: cannot open display:
== gle-dind00.cs.umd.edu (18 distinct, 18 total) ==
Sep 26 11:39:31 gle-dind00.cs.umd.edu systemd-udevd[3549069]: Could not generate persistent MAC address for veth6d61156: No such file or directory
Sep 26 11:39:31 gle-dind00.cs.umd.edu systemd-udevd[3549070]: Could not generate persistent MAC address for veth3d14140: No such file or directory
Sep 26 11:39:32 gle-dind00.cs.umd.edu systemd-udevd[3549167]: Could not generate persistent MAC address for vetha78ace5: No such file or directory
Sep 26 11:39:32 gle-dind00.cs.umd.edu systemd-udevd[3549169]: Could not generate persistent MAC address for vethb970c1d: No such file or directory
Sep 26 11:39:33 gle-dind00.cs.umd.edu systemd-udevd[3549262]: Could not generate persistent MAC address for veth3e4aa5d: No such file or directory
Sep 26 11:39:33 gle-dind00.cs.umd.edu systemd-udevd[3549263]: Could not generate persistent MAC address for vethcb16061: No such file or directory
Sep 26 11:39:34 gle-dind00.cs.umd.edu systemd-udevd[3549364]: Could not generate persistent MAC address for veth7e6fc48: No such file or directory
Sep 26 11:39:34 gle-dind00.cs.umd.edu systemd-udevd[3549363]: Could not generate persistent MAC address for vethc569a74: No such file or directory
Sep 26 11:39:35 gle-dind00.cs.umd.edu systemd-udevd[3549464]: Could not generate persistent MAC address for vethfba9fd3: No such file or directory
Sep 26 11:39:35 gle-dind00.cs.umd.edu systemd-udevd[3549465]: Could not generate persistent MAC address for veth4599be2: No such file or directory
Sep 26 11:39:36 gle-dind00.cs.umd.edu systemd-udevd[3549636]: Could not generate persistent MAC address for veth86d4c8e: No such file or directory
Sep 26 11:39:36 gle-dind00.cs.umd.edu systemd-udevd[3549637]: Could not generate persistent MAC address for veth37058cd: No such file or directory
Sep 26 11:39:37 gle-dind00.cs.umd.edu systemd-udevd[3549743]: Could not generate persistent MAC address for vethbd8c2b3: No such file or directory
Sep 26 11:39:37 gle-dind00.cs.umd.edu systemd-udevd[3549744]: Could not generate persistent MAC address for veth32c70e0: No such file or directory
Sep 26 11:39:40 gle-dind00.cs.umd.edu systemd-udevd[3549869]: Could not generate persistent MAC address for veth3501f6c: No such file or directory
Sep 26 11:39:40 gle-dind00.cs.umd.edu systemd-udevd[3549870]: Could not generate persistent MAC address for veth422c01e: No such file or directory
Sep 26 11:39:41 gle-dind00.cs.umd.edu systemd-udevd[3549983]: Could not generate persistent MAC address for veth610cacc: No such file or directory
Sep 26 11:39:41 gle-dind00.cs.umd.edu systemd-udevd[3549984]: Could not generate persistent MAC address for veth7697445: No such file or directory
== grosh (1 distinct, 1 total) ==
Sep 26 11:58:50 grosh setroubleshoot[126429]: failed to retrieve rpm info for path '/etc/resolv.conf':
== idm00 (1 distinct, 1 total) ==
Sep 26 11:54:09 idm00 named[4166701]: client @0x7f11a9408e98 10.73.240.42#59422: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 11:39:27 idmp0 named[1598691]: client @0x7f2d4803e0e8 10.73.240.43#52265: update '73.10.in-addr.arpa/IN' denied
== krispykreme.cs.umd.edu (3 distinct, 4 total) ==
Sep 26 11:43:30 krispykreme.cs.umd.edu sshd-session[2822475]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2]
Sep 26 11:43:32 krispykreme.cs.umd.edu sshd-session[2822475]: Error in Duo login for 'larry' from 71.191.93.172
Sep 26 11:43:32 krispykreme.cs.umd.edu sshd-session[2822473]: error: PAM: Authentication failure for larry from 71.191.93.172
== munin (2 distinct, 8 total) ==
Sep 26 11:28:17 munin sudo[3909854]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 11:28:17 munin sudo[3909854]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 11:13:03 newhonors2 dhcpcd[3182672]: dhcpcd is not running [x24]
== ntop00 (58 distinct, 118714 total) ==
Sep 26 11:08:11 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 ] [x56621]
Sep 26 11:08:11 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 ] [x53831]
Sep 26 11:08:11 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 26 11:08:11 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 26 11:08:11 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 ] [x7715]
Sep 26 11:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 11:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 660) ***
Sep 26 11:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 660, QN: 0/58, ET: 0) ***
Sep 26 11:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 11:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 660) ***
Sep 26 11:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 660, QN: 0/5321, ET: 0) ***
Sep 26 11:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 661) ***
Sep 26 11:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 661, QN: 6181/6181, ET: 0) ***
Sep 26 11:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 661) ***
Sep 26 11:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 661, QN: 66/66, ET: 0) ***
Sep 26 11:14:03 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ]
Sep 26 11:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 664) ***
Sep 26 11:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 664, QN: 0/6165, ET: 0) ***
Sep 26 11:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 664) ***
Sep 26 11:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 664, QN: 0/67, ET: 0) ***
Sep 26 11:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 665) ***
Sep 26 11:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 665, QN: 5944/5944, ET: 0) ***
Sep 26 11:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 665) ***
Sep 26 11:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 665, QN: 60/60, ET: 0) ***
Sep 26 11:30:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 668) ***
Sep 26 11:30:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 668, QN: 0/56, ET: 0) ***
Sep 26 11:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 668) ***
Sep 26 11:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 668, QN: 0/6555, ET: 0) ***
... 28 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 11:09:09 outbound00.cs.umd.edu python3[4085220]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 11:13:06 outbound01.cs.umd.edu python3[2151970]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (34 distinct, 34 total) ==
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178016]: Could not generate persistent MAC address for veth5cf13c7: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178017]: Could not generate persistent MAC address for vetha3e1ee1: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178021]: Could not generate persistent MAC address for veth69d744b: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178020]: Could not generate persistent MAC address for veth207ea42: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178021]: Could not generate persistent MAC address for vethdd305fe: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178031]: Could not generate persistent MAC address for veth0445a0f: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178050]: Could not generate persistent MAC address for veth00e22be: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178055]: Could not generate persistent MAC address for vethc6fed17: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178091]: Could not generate persistent MAC address for vethfec4b3d: No such file or directory
Sep 26 11:16:26 sentry-docker00.cs.umd.edu systemd-udevd[4178072]: Could not generate persistent MAC address for vethbc5bf1a: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187410]: link_config: could not get ethtool features for veth207ea42
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187410]: Could not set offload features of veth207ea42: No such device
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187446]: Could not generate persistent MAC address for veth58b9188: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187447]: Could not generate persistent MAC address for vethf3e1ae4: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187450]: Could not generate persistent MAC address for veth7ae0097: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187451]: Could not generate persistent MAC address for veth50e658f: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187475]: Could not generate persistent MAC address for vetha36d435: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187474]: Could not generate persistent MAC address for vethb65893e: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187487]: Could not generate persistent MAC address for veth3e22aa7: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187492]: Could not generate persistent MAC address for veth62e0be0: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187502]: Could not generate persistent MAC address for vethcb1020f: No such file or directory
Sep 26 11:36:34 sentry-docker00.cs.umd.edu systemd-udevd[4187503]: Could not generate persistent MAC address for vethbc93824: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3181]: link_config: could not get ethtool features for veth7ae0097
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3181]: Could not set offload features of veth7ae0097: No such device
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3223]: Could not generate persistent MAC address for veth1032968: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3224]: Could not generate persistent MAC address for veth880e90f: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3227]: Could not generate persistent MAC address for vethab07fd5: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3228]: Could not generate persistent MAC address for vethd8cd276: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3251]: Could not generate persistent MAC address for veth3b2e04b: No such file or directory
Sep 26 11:56:42 sentry-docker00.cs.umd.edu systemd-udevd[3252]: Could not generate persistent MAC address for veth796b8ad: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 11:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 11:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 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.5073s
Status : exited 0
Output :
Syslog digest — 2026-09-26 11:05 EDT
Processed 120,387 lines, filtered 1,453 (1%). 118,934 unknown (203 distinct) from 18 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 11:01:25 b0b02.cs.umd.edu rustdesk[1309265]: cannot open display:
== grosh (35 distinct, 41 total) ==
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for claude-code
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-app-library
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-applets
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-epoch [x3]
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-files
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-greeter
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-initial-setup
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-launcher
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-monitor
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-notifications
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-osd
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-panel
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-randr
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-screenshot
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-session
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-settings
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-settings-daemon
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-term
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-workspaces
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for pop-launcher
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for xdg-desktop-portal-cosmic
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for libxml2
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for python3-libxml2
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-modules-extra-matched [x3]
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-tools
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-tools-libs
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for python3-cryptography
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for cosmic-osk
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel [x3]
Sep 26 10:37:46 grosh packagekitd[116385]: Failed to get cache filename for kernel-core
... 5 more distinct messages not shown
== idm00 (3 distinct, 3 total) ==
Sep 26 10:40:57 idm00 named[4166701]: client @0x7f119806f9c8 10.73.245.14#56667: update '73.10.in-addr.arpa/IN' denied
Sep 26 10:41:15 idm00 named[4166701]: client @0x7f1198541268 10.73.245.14#56667: update '73.10.in-addr.arpa/IN' denied
Sep 26 10:54:09 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#57792: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 10:39:27 idmp0 named[1598691]: client @0x7f2d2c050c58 10.73.240.43#52523: update '73.10.in-addr.arpa/IN' denied
== irb2156 (25 distinct, 25 total) ==
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for firefox-nightly
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for claude-code
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-app-library
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-applets
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-epoch
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-files
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-greeter
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-initial-setup
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-launcher
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-monitor
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-notifications
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-osd
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-panel
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-randr
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-screenshot
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-session
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-settings
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-settings-daemon
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-term
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-workspaces
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for pop-launcher
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for xdg-desktop-portal-cosmic
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for cosmic-osk
Sep 26 10:55:04 irb2156 packagekitd[1490311]: Failed to get cache filename for kernel
Sep 26 11:00:01 irb2156 (da-udp.*)[1491165]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory
== itmon02 (1 distinct, 4 total) ==
Sep 26 10:43:37 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== krispykreme.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 10:26:11 krispykreme.cs.umd.edu sshd-session[2802158]: pam_access(sshd:auth): access denied for user `bahar' from `173.66.227.191'
== lifepix (1 distinct, 1 total) ==
Sep 26 11:00:01 lifepix (da-udp.*)[270711]: amanda-udp-restart.service: Failed at step EXEC spawning /usr/bin/systemctl restart amanda-udp.*: No such file or directory
== munin (2 distinct, 2 total) ==
Sep 26 10:09:04 munin sudo[3881020]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory
Sep 26 10:09:04 munin sudo[3881020]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order.
== newhonors2 (1 distinct, 24 total) ==
Sep 26 10:13:02 newhonors2 dhcpcd[3180850]: dhcpcd is not running [x24]
== ntop00 (70 distinct, 118728 total) ==
Sep 26 10:07:51 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 ] [x7596]
Sep 26 10:07:51 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 ] [x56706]
Sep 26 10:07:51 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 ] [x53903]
Sep 26 10:07:51 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 ] [x216]
Sep 26 10:07:51 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 ] [x216]
Sep 26 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 635) ***
Sep 26 10:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 635, QN: 5547/5547, ET: 0) ***
Sep 26 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 635) ***
Sep 26 10:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 635, QN: 51/51, ET: 0) ***
Sep 26 10:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 636) ***
Sep 26 10:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 636, QN: 0/5964, ET: 0) ***
Sep 26 10:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 636) ***
Sep 26 10:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 636, QN: 0/49, ET: 0) ***
Sep 26 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 637) ***
Sep 26 10:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 637, QN: 5673/5673, ET: 0) ***
Sep 26 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 637) ***
Sep 26 10:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 637, QN: 49/49, ET: 0) ***
Sep 26 10:14:02 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 ] [x7]
Sep 26 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 639) ***
Sep 26 10:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 639, QN: 5791/5791, ET: 0) ***
Sep 26 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 639) ***
Sep 26 10:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 639, QN: 50/50, ET: 0) ***
Sep 26 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 640) ***
Sep 26 10:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 640, QN: 0/6126, ET: 0) ***
Sep 26 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 640) ***
Sep 26 10:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 640, QN: 0/54, ET: 0) ***
... 40 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 10:09:09 outbound00.cs.umd.edu python3[4071116]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 10:13:06 outbound01.cs.umd.edu python3[2137977]: ldapdb [x6]
== quiss (1 distinct, 1 total) ==
Sep 26 11:00:09 quiss (da-udp.*)[3029696]: 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 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149605]: link_config: could not get ethtool features for veth12bfe0d
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149605]: Could not set offload features of veth12bfe0d: No such device
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149621]: Could not generate persistent MAC address for veth8193ae8: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149622]: Could not generate persistent MAC address for veth2583be0: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149692]: Could not generate persistent MAC address for vethd06b0d6: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149693]: Could not generate persistent MAC address for veth232a67b: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149716]: Could not generate persistent MAC address for veth2d45e2b: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149709]: Could not generate persistent MAC address for veth77fa8e3: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149726]: Could not generate persistent MAC address for veth2c14be8: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149728]: Could not generate persistent MAC address for vethfe099da: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149744]: Could not generate persistent MAC address for vetha281b39: No such file or directory
Sep 26 10:16:01 sentry-docker00.cs.umd.edu systemd-udevd[4149728]: Could not generate persistent MAC address for veth17c87a9: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159084]: Could not generate persistent MAC address for veth57a4be3: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159085]: Could not generate persistent MAC address for veth03785a3: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159103]: Could not generate persistent MAC address for veth4f27a5e: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159109]: Could not generate persistent MAC address for veth70f7a51: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159112]: Could not generate persistent MAC address for veth8f63698: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159113]: Could not generate persistent MAC address for veth62a396a: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159131]: Could not generate persistent MAC address for veth0017044: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159136]: Could not generate persistent MAC address for veth77076c0: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159151]: Could not generate persistent MAC address for vethc281e78: No such file or directory
Sep 26 10:36:09 sentry-docker00.cs.umd.edu systemd-udevd[4159158]: Could not generate persistent MAC address for veth8fccd05: No such file or directory
Sep 26 10:56:17 sentry-docker00.cs.umd.edu systemd-udevd[4168536]: link_config: could not get ethtool features for veth57a4be3
Sep 26 10:56:17 sentry-docker00.cs.umd.edu systemd-udevd[4168536]: Could not set offload features of veth57a4be3: No such device
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168573]: Could not generate persistent MAC address for vethb3d832d: No such file or directory
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168574]: Could not generate persistent MAC address for vethf7cd2a7: No such file or directory
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168577]: Could not generate persistent MAC address for vethc8b2c6b: No such file or directory
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168578]: Could not generate persistent MAC address for vethbc63730: No such file or directory
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168601]: Could not generate persistent MAC address for veth1f9bd8f: No such file or directory
Sep 26 10:56:18 sentry-docker00.cs.umd.edu systemd-udevd[4168602]: Could not generate persistent MAC address for veth202f6a5: No such file or directory
... 4 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 10:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 10:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 10:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 10:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 10:25:56 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Aad9Fa/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Aad9Fa. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 10:25:57 submit26-b9-f1 setroubleshoot[3763283]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (9 distinct, 9 total) ==
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.uKTlu8/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.uKTlu8. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 10:06:51 submit26-b9-f2 setroubleshoot[2841193]: 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.8321s
Status : exited 0
Output :
Syslog digest — 2026-09-26 10:05 EDT
Processed 120,451 lines, filtered 1,528 (1%). 118,923 unknown (164 distinct) from 16 host(s).
== b0b02.cs.umd.edu (2 distinct, 2 total) ==
Sep 26 09:42:28 b0b02.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly.
Sep 26 10:01:23 b0b02.cs.umd.edu rustdesk[1294047]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 09:11:22 biggulp.cs.umd.edu sshd-session[185123]: error: send_error: write: Connection reset by peer
== idm00 (1 distinct, 1 total) ==
Sep 26 09:54:09 idm00 named[4166701]: client @0x7f1198541268 10.73.240.42#60910: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 09:39:29 idmp0 named[1598691]: client @0x7f2d2402e528 10.73.240.43#57757: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 3 total) ==
Sep 26 09:28:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3]
== mcstic (1 distinct, 2 total) ==
Sep 26 09:36:38 mcstic krb5_child[1148061]: Client 'admin(a)UMD.EDU' not found in Kerberos database [x2]
== munin (2 distinct, 12 total) ==
Sep 26 09:08:12 munin sudo[3858966]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6]
Sep 26 09:08:12 munin sudo[3858966]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 09:13:03 newhonors2 dhcpcd[3178990]: dhcpcd is not running [x24]
== ntop00 (82 distinct, 118756 total) ==
Sep 26 09:07:21 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56665]
Sep 26 09:07:21 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 ] [x53732]
Sep 26 09:07:21 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 ] [x221]
Sep 26 09:07:21 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 ] [x221]
Sep 26 09:07:21 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 ] [x7820]
Sep 26 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 611) ***
Sep 26 09:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 611, QN: 69/69, ET: 0) ***
Sep 26 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 611) ***
Sep 26 09:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 611, QN: 6560/6560, ET: 0) ***
Sep 26 09:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 612) ***
Sep 26 09:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 612, QN: 0/6654, ET: 0) ***
Sep 26 09:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 612) ***
Sep 26 09:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 612, QN: 0/64, ET: 0) ***
Sep 26 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 613) ***
Sep 26 09:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 613, QN: 5738/5738, ET: 0) ***
Sep 26 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 613) ***
Sep 26 09:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 613, QN: 62/62, ET: 0) ***
Sep 26 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 615) ***
Sep 26 09:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 615, QN: 4872/4872, ET: 0) ***
Sep 26 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 615) ***
Sep 26 09:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 615, QN: 59/59, ET: 0) ***
Sep 26 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 616) ***
Sep 26 09:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 616, QN: 0/5669, ET: 0) ***
Sep 26 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 616) ***
Sep 26 09:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 616, QN: 0/58, ET: 0) ***
Sep 26 09:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 617) ***
... 52 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 09:09:09 outbound00.cs.umd.edu python3[4057180]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 09:13:07 outbound01.cs.umd.edu python3[2123863]: ldapdb [x6]
== quiss (6 distinct, 10 total) ==
Sep 26 09:08:40 quiss gnome-software[191719]: failed to get featured apps: no apps to show
Sep 26 09:08:40 quiss gnome-software[191719]: Only 0 apps for curated list, hiding
Sep 26 09:08:40 quiss gnome-software[191719]: Only 0 apps for recent list, hiding
Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for claude-code
Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for perl [x3]
Sep 26 09:08:49 quiss packagekitd[3010295]: Failed to get cache filename for kernel [x3]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120939]: link_config: could not get ethtool features for veth835142c
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120939]: Could not set offload features of veth835142c: No such device
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120965]: Could not generate persistent MAC address for veth3e997b3: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120966]: Could not generate persistent MAC address for veth2467fe9: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120991]: Could not generate persistent MAC address for veth2334793: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120993]: Could not generate persistent MAC address for veth4fd7824: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121013]: Could not generate persistent MAC address for vethade818e: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4120991]: Could not generate persistent MAC address for veth535e907: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121011]: Could not generate persistent MAC address for vethc8b1a86: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121015]: Could not generate persistent MAC address for veth04551f3: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121060]: Could not generate persistent MAC address for veth68fad4d: No such file or directory
Sep 26 09:15:36 sentry-docker00.cs.umd.edu systemd-udevd[4121055]: Could not generate persistent MAC address for veth51752a3: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130800]: link_config: could not get ethtool features for veth2334793
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130800]: Could not set offload features of veth2334793: No such device
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130895]: link_config: could not get ethtool features for veth3e997b3
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130895]: Could not set offload features of veth3e997b3: No such device
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130924]: Could not generate persistent MAC address for vethf601589: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130925]: Could not generate persistent MAC address for vethdcfb3c6: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130928]: Could not generate persistent MAC address for vethb043135: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130939]: Could not generate persistent MAC address for veth82c949d: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130949]: Could not generate persistent MAC address for vethe55c147: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130938]: Could not generate persistent MAC address for vethb9da126: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130948]: Could not generate persistent MAC address for veth6fd4da2: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130931]: Could not generate persistent MAC address for vethc3def5d: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130949]: Could not generate persistent MAC address for vethfb444d1: No such file or directory
Sep 26 09:35:44 sentry-docker00.cs.umd.edu systemd-udevd[4130933]: Could not generate persistent MAC address for vethaff41e7: No such file or directory
Sep 26 09:55:52 sentry-docker00.cs.umd.edu systemd-udevd[4140252]: link_config: could not get ethtool features for vethe55c147
Sep 26 09:55:52 sentry-docker00.cs.umd.edu systemd-udevd[4140252]: Could not set offload features of vethe55c147: No such device
Sep 26 09:55:53 sentry-docker00.cs.umd.edu systemd-udevd[4140287]: Could not generate persistent MAC address for veth18d7ba7: No such file or directory
Sep 26 09:55:53 sentry-docker00.cs.umd.edu systemd-udevd[4140288]: Could not generate persistent MAC address for vethb349a5a: No such file or directory
... 8 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (10 distinct, 14 total) ==
Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.meXjIW/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.meXjIW. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 [x2]
Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: 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 [x2]
Sep 26 09:06:45 submit26-b9-f3 setroubleshoot[3520328]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.q4xsFl. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.VmKVbq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.VmKVbq. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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 26 09:24:48 submit26-b9-f4 setroubleshoot[2579601]: 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.5373s
Status : exited 0
Output :
Syslog digest — 2026-09-26 09:05 EDT
Processed 120,405 lines, filtered 1,502 (1%). 118,903 unknown (152 distinct) from 19 host(s).
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 08:12:12 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 09:01:19 b0b02.cs.umd.edu rustdesk[1278845]: cannot open display:
== cheezit.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 08:13:20 cheezit.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly.
== emaar (2 distinct, 2 total) ==
Sep 26 08:33:39 emaar systemd[1]: insights-client.service: Start request repeated too quickly.
Sep 26 08:43:21 emaar puppet-agent[2349309]: (Facter) invalid or malformed lldp data: MalformedDataError: no lldp interface data found
== galax (1 distinct, 1 total) ==
Sep 26 08:41:12 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 4099 times, consider switching to WQ_UNBOUND
== hackerman (1 distinct, 1 total) ==
Sep 26 08:53:14 hackerman systemd[1]: insights-client.service: Start request repeated too quickly.
== idm00 (1 distinct, 1 total) ==
Sep 26 08:54:09 idm00 named[4166701]: client @0x7f11a0064678 10.73.240.42#50815: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 08:39:29 idmp0 named[1598691]: client @0x7f2d20000cc8 10.73.240.43#49219: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 5 total) ==
Sep 26 08:13:35 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x5]
== mirrors.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 08:37:00 mirrors.cs.umd.edu puppet-agent[28683]: (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: 28889
== munin (2 distinct, 6 total) ==
Sep 26 09:03:18 munin sudo[3856750]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x3]
Sep 26 09:03:18 munin sudo[3856750]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x3]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 08:13:03 newhonors2 dhcpcd[3177144]: dhcpcd is not running [x24]
== ntop00 (81 distinct, 118757 total) ==
Sep 26 08:06:56 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 ] [x56616]
Sep 26 08:06:56 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 ] [x53824]
Sep 26 08:06:56 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 ] [x225]
Sep 26 08:06:56 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 ] [x225]
Sep 26 08:06:56 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 ] [x7771]
Sep 26 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 587) ***
Sep 26 08:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 587, QN: 51/51, ET: 0) ***
Sep 26 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 587) ***
Sep 26 08:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 587, QN: 4991/4991, ET: 0) ***
Sep 26 08:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 588) ***
Sep 26 08:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 588, QN: 0/4826, ET: 0) ***
Sep 26 08:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 588) ***
Sep 26 08:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 588, QN: 0/58, ET: 0) ***
Sep 26 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 589) ***
Sep 26 08:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 589, QN: 5791/5791, ET: 0) ***
Sep 26 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 589) ***
Sep 26 08:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 589, QN: 79/79, ET: 0) ***
Sep 26 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 591) ***
Sep 26 08:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 591, QN: 6617/6617, ET: 0) ***
Sep 26 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 591) ***
Sep 26 08:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 591, QN: 64/64, ET: 0) ***
Sep 26 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 592) ***
Sep 26 08:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 592, QN: 0/5718, ET: 0) ***
Sep 26 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 592) ***
Sep 26 08:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 592, QN: 0/72, ET: 0) ***
Sep 26 08:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 593) ***
... 51 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 08:09:09 outbound00.cs.umd.edu python3[4043264]: ldapdb [x6]
== outbound01.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 08:13:06 outbound01.cs.umd.edu python3[2109905]: ldapdb [x6]
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091290]: link_config: could not get ethtool features for vethab4601f
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091290]: Could not set offload features of vethab4601f: No such device
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091371]: Could not generate persistent MAC address for vethadd9d06: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091372]: Could not generate persistent MAC address for veth6ba18e8: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091375]: Could not generate persistent MAC address for vethc4af472: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091376]: Could not generate persistent MAC address for veth81ffb0f: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091397]: Could not generate persistent MAC address for veth8130069: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091382]: Could not generate persistent MAC address for vethd29d497: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091384]: Could not generate persistent MAC address for veth627dd69: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091382]: Could not generate persistent MAC address for veth5d22473: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091371]: Could not generate persistent MAC address for vethf352ffa: No such file or directory
Sep 26 08:15:11 sentry-docker00.cs.umd.edu systemd-udevd[4091372]: Could not generate persistent MAC address for veth77fbdc1: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100573]: link_config: could not get ethtool features for veth627dd69
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100573]: Could not set offload features of veth627dd69: No such device
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100602]: Could not generate persistent MAC address for vethbd37076: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth69d9ab3: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100606]: Could not generate persistent MAC address for veth4ae9683: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100607]: Could not generate persistent MAC address for veth0f46268: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100624]: Could not generate persistent MAC address for veth73fb4f4: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100617]: Could not generate persistent MAC address for vethc8b15db: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100612]: Could not generate persistent MAC address for veth97e2d71: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth3fe9cd4: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100621]: Could not generate persistent MAC address for vetha7af021: No such file or directory
Sep 26 08:35:19 sentry-docker00.cs.umd.edu systemd-udevd[4100603]: Could not generate persistent MAC address for veth791d9cf: No such file or directory
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111682]: link_config: could not get ethtool features for veth791d9cf
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111682]: Could not set offload features of veth791d9cf: No such device
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111708]: link_config: could not get ethtool features for vethbd37076
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111708]: Could not set offload features of vethbd37076: No such device
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111798]: Could not generate persistent MAC address for vetha12c4b5: No such file or directory
Sep 26 08:55:27 sentry-docker00.cs.umd.edu systemd-udevd[4111799]: Could not generate persistent MAC address for veth15d6a72: No such file or directory
... 8 more distinct messages not shown
== smokeping-slave (1 distinct, 1 total) ==
Sep 26 08:58:16 smokeping-slave nologin[2674829]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 08:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 08:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 08:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-fclone (9 distinct, 12 total) ==
Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: 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 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: 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 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 [x2]
Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.aPW1vd/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc [x2]
Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 [x2]
Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.aPW1vd. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5
Sep 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: 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 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: 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 26 08:22:00 submit26-b9-fclone setroubleshoot[519039]: 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.5487s
Status : exited 0
Output :
Syslog digest — 2026-09-26 08:05 EDT
Processed 121,035 lines, filtered 1,870 (1%). 119,165 unknown (118 distinct) from 13 host(s).
== atif01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 07:35:37 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 08:01:15 b0b02.cs.umd.edu rustdesk[1263476]: cannot open display:
== idm00 (1 distinct, 1 total) ==
Sep 26 07:54:09 idm00 named[4166701]: client @0x7f11a93c7eb8 10.73.240.42#62947: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 07:39:29 idmp0 named[1598691]: client @0x7f2d3400d5c8 10.73.240.43#65503: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 1 total) ==
Sep 26 07:08:41 itmon02 sshd[1483508]: error: beginning MaxStartups throttling
== munin (2 distinct, 4 total) ==
Sep 26 07:58:41 munin sudo[3832306]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2]
Sep 26 07:58:41 munin sudo[3832306]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 07:13:03 newhonors2 dhcpcd[3175298]: dhcpcd is not running [x24]
== ntop00 (63 distinct, 119043 total) ==
Sep 26 07:06:09 ntop00 rsyslogd[1208]: imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2433 ] [x7605]
Sep 26 07:06:09 ntop00 rsyslogd[1208]: file '/var/log/messages'[13] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x56817]
Sep 26 07:06:09 ntop00 rsyslogd[1208]: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x54087]
Sep 26 07:06:16 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 ] [x224]
Sep 26 07:06:16 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 ] [x224]
Sep 26 07:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 563) ***
Sep 26 07:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 563, QN: 6099/6099, ET: 0) ***
Sep 26 07:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 563) ***
Sep 26 07:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 563, QN: 74/74, ET: 0) ***
Sep 26 07:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 07:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 564) ***
Sep 26 07:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 564, QN: 0/5762, ET: 0) ***
Sep 26 07:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 07:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 564) ***
Sep 26 07:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 564, QN: 0/64, ET: 0) ***
Sep 26 07:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 567) ***
Sep 26 07:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 567, QN: 89/89, ET: 0) ***
Sep 26 07:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 567) ***
Sep 26 07:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 567, QN: 5495/5495, ET: 0) ***
Sep 26 07:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 568) ***
Sep 26 07:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 568, QN: 0/5294, ET: 0) ***
Sep 26 07:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 568) ***
Sep 26 07:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 568, QN: 0/68, ET: 0) ***
Sep 26 07:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 571) ***
Sep 26 07:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 571, QN: 5770/5770, ET: 0) ***
Sep 26 07:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 571) ***
Sep 26 07:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 571, QN: 63/63, ET: 0) ***
Sep 26 07:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 572) ***
... 33 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 07:09:09 outbound00.cs.umd.edu python3[4028775]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 26 07:13:06 outbound01.cs.umd.edu python3[2095014]: ldapdb [x6]
Sep 26 07:13:25 outbound01.cs.umd.edu cockpit-ws[2095119]: /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]
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4062976]: link_config: could not get ethtool features for veth66e4c35
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4062976]: Could not set offload features of veth66e4c35: No such device
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063012]: Could not generate persistent MAC address for vethf97b3a3: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063013]: Could not generate persistent MAC address for vethb727384: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063016]: Could not generate persistent MAC address for veth225e326: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063017]: Could not generate persistent MAC address for veth718d346: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063036]: Could not generate persistent MAC address for vethb179796: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063020]: Could not generate persistent MAC address for vethb8e672a: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063026]: Could not generate persistent MAC address for vethbee4a1e: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063022]: Could not generate persistent MAC address for veth81dbbae: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063026]: Could not generate persistent MAC address for vethbfd3d53: No such file or directory
Sep 26 07:14:46 sentry-docker00.cs.umd.edu systemd-udevd[4063020]: Could not generate persistent MAC address for veth9755159: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072362]: link_config: could not get ethtool features for veth81dbbae
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072362]: Could not set offload features of veth81dbbae: No such device
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072396]: Could not generate persistent MAC address for vethc069e72: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072397]: Could not generate persistent MAC address for vethfd8519e: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072400]: Could not generate persistent MAC address for veth6459867: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072401]: Could not generate persistent MAC address for veth999777c: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072414]: Could not generate persistent MAC address for vethe450bf9: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072409]: Could not generate persistent MAC address for vethd195316: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072409]: Could not generate persistent MAC address for veth5efbe0f: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072414]: Could not generate persistent MAC address for vethfbfc22f: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072414]: Could not generate persistent MAC address for veth31e63cd: No such file or directory
Sep 26 07:34:54 sentry-docker00.cs.umd.edu systemd-udevd[4072408]: Could not generate persistent MAC address for vethe088b04: No such file or directory
Sep 26 07:55:02 sentry-docker00.cs.umd.edu systemd-udevd[4081722]: link_config: could not get ethtool features for vethe088b04
Sep 26 07:55:02 sentry-docker00.cs.umd.edu systemd-udevd[4081722]: Could not set offload features of vethe088b04: No such device
Sep 26 07:55:03 sentry-docker00.cs.umd.edu systemd-udevd[4081795]: Could not generate persistent MAC address for veth398b7f9: No such file or directory
Sep 26 07:55:03 sentry-docker00.cs.umd.edu systemd-udevd[4081796]: Could not generate persistent MAC address for veth31a1e65: No such file or directory
Sep 26 07:55:03 sentry-docker00.cs.umd.edu systemd-udevd[4081799]: Could not generate persistent MAC address for veth9b21d33: No such file or directory
Sep 26 07:55:03 sentry-docker00.cs.umd.edu systemd-udevd[4081805]: Could not generate persistent MAC address for vethf132c04: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 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 26 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 26 07:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 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 26 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 26 07:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 07:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit10-cln25 (1 distinct, 1 total) ==
Sep 26 07:37:00 submit10-cln25 systemd: Failed at step EXEC spawning /usr/local/bin/cronjob: No such file or directory
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5723s
Status : exited 0
Output :
Syslog digest — 2026-09-26 07:05 EDT
Processed 121,163 lines, filtered 1,779 (1%). 119,384 unknown (159 distinct) from 27 host(s).
== abadi-computer (2 distinct, 2 total) ==
Sep 26 06:15:00 abadi-computer nologin[1034473]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 26 06:15:00 abadi-computer pipewire[1034469]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 07:01:10 b0b02.cs.umd.edu rustdesk[1247297]: cannot open display:
== biggulp.cs.umd.edu (1 distinct, 3 total) ==
Sep 26 06:12:48 biggulp.cs.umd.edu sshd-session[154058]: error: send_error: write: Connection reset by peer [x3]
== galahad.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 06:19:12 galahad.cs.umd.edu gnome-software[2904800]: Only 0 apps for recent list, hiding
== hazfs.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 06:22:01 hazfs.cs.umd.edu rpc.mountd[1586325]: /export/home exported to both 10.73.255.0/24 and 10.73.0.0/16, arbitrarily choosing options from first
== idm00 (1 distinct, 1 total) ==
Sep 26 06:54:09 idm00 named[4166701]: client @0x7f11a0005288 10.73.240.42#59109: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 06:39:29 idmp0 named[1598691]: client @0x7f2d30000cc8 10.73.240.43#51147: update '73.10.in-addr.arpa/IN' denied
== inbound00.cs.umd.edu (2 distinct, 3 total) ==
Sep 26 06:07:01 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.
Sep 26 06:53:35 inbound00.cs.umd.edu cockpit-ws[4174323]: /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 (2 distinct, 3 total) ==
Sep 26 06:18:16 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.
Sep 26 06:53:33 inbound01.cs.umd.edu cockpit-ws[2193221]: /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 26 06:20:06 irb2156 systemd[1]: insights-client.service: Start request repeated too quickly.
== itmon02 (1 distinct, 2 total) ==
Sep 26 06:12:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2]
== kadath.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 06:14:30 kadath.cs.umd.edu gnome-software[589638]: Only 0 apps for recent list, hiding
== librenms (1 distinct, 1 total) ==
Sep 26 06:48:28 librenms puppet-agent[2722349]: 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
== munin (2 distinct, 8 total) ==
Sep 26 06:48:30 munin sudo[3807765]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 06:48:30 munin sudo[3807765]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== neodontcare.cs.umd.edu (4 distinct, 5 total) ==
Sep 26 06:14:49 neodontcare.cs.umd.edu gnome-software[10171]: Only 0 apps for recent list, hiding
Sep 26 06:14:58 neodontcare.cs.umd.edu packagekitd[2787224]: Failed to get cache filename for gnu-free-mono-fonts
Sep 26 06:14:58 neodontcare.cs.umd.edu packagekitd[2787224]: Failed to get cache filename for gnu-free-serif-fonts
Sep 26 06:15:01 neodontcare.cs.umd.edu packagekitd[2787224]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 06:13:02 newhonors2 dhcpcd[3172865]: dhcpcd is not running [x24]
== ntop00 (57 distinct, 119196 total) ==
Sep 26 06:05:16 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 ] [x8019]
Sep 26 06:05:16 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 ] [x56818]
Sep 26 06:05:16 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 ] [x53831]
Sep 26 06:05:16 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 ] [x228]
Sep 26 06:05:16 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 ] [x228]
Sep 26 06:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 539) ***
Sep 26 06:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 539, QN: 5546/5546, ET: 0) ***
Sep 26 06:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 539) ***
Sep 26 06:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 539, QN: 66/66, ET: 0) ***
Sep 26 06:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 06:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 540) ***
Sep 26 06:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 540, QN: 0/5559, ET: 0) ***
Sep 26 06:10:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x6]
Sep 26 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 26 06:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 540) ***
Sep 26 06:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 540, QN: 0/82, ET: 0) ***
Sep 26 06:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 543) ***
Sep 26 06:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 543, QN: 5471/5471, ET: 0) ***
Sep 26 06:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 543) ***
Sep 26 06:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 543, QN: 70/70, ET: 0) ***
Sep 26 06:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 544) ***
Sep 26 06:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 544, QN: 0/5836, ET: 0) ***
Sep 26 06:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 544) ***
Sep 26 06:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 544, QN: 0/53, ET: 0) ***
Sep 26 06:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 547) ***
Sep 26 06:28:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 547, QN: 6948/6948, ET: 0) ***
Sep 26 06:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 547) ***
Sep 26 06:28:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 547, QN: 69/69, ET: 0) ***
Sep 26 06:30:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 548) ***
... 27 more distinct messages not shown
== orchids (5 distinct, 6 total) ==
Sep 26 06:11:31 orchids gnome-software[1516991]: Only 0 apps for recent list, hiding
Sep 26 06:11:38 orchids packagekitd[876368]: Failed to get cache filename for libreoffice
Sep 26 06:11:38 orchids packagekitd[876368]: Failed to get cache filename for cups-filesystem
Sep 26 06:11:38 orchids packagekitd[876368]: Failed to get cache filename for kernel
Sep 26 06:11:41 orchids packagekitd[876368]: failed to parse public key for /etc/pki/rpm-gpg/RPM-GPG-KEY-PQC-redhat-release [x2]
== outbound00.cs.umd.edu (2 distinct, 7 total) ==
Sep 26 06:09:09 outbound00.cs.umd.edu python3[4014497]: ldapdb [x6]
Sep 26 06:50:20 outbound00.cs.umd.edu cockpit-ws[4023939]: /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
== outbound01.cs.umd.edu (2 distinct, 7 total) ==
Sep 26 06:13:06 outbound01.cs.umd.edu python3[2080937]: ldapdb [x6]
Sep 26 06:50:24 outbound01.cs.umd.edu cockpit-ws[2089429]: /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
== sentry-docker00.cs.umd.edu (38 distinct, 38 total) ==
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034666]: link_config: could not get ethtool features for vethb268998
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034666]: Could not set offload features of vethb268998: No such device
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034689]: Could not generate persistent MAC address for veth7afaf31: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034688]: Could not generate persistent MAC address for vethc75f29b: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034714]: Could not generate persistent MAC address for veth4a08043: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034715]: Could not generate persistent MAC address for veth247fb3b: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034733]: Could not generate persistent MAC address for veth5c8be30: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034729]: Could not generate persistent MAC address for veth49e1e64: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034729]: Could not generate persistent MAC address for vethe868aa2: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034732]: Could not generate persistent MAC address for vethe7e2283: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034725]: Could not generate persistent MAC address for veth64446e9: No such file or directory
Sep 26 06:14:21 sentry-docker00.cs.umd.edu systemd-udevd[4034720]: Could not generate persistent MAC address for veth46792f1: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044078]: link_config: could not get ethtool features for vethc75f29b
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044078]: Could not set offload features of vethc75f29b: No such device
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044108]: Could not generate persistent MAC address for vethc17888a: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044109]: Could not generate persistent MAC address for veth39c58cf: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044112]: Could not generate persistent MAC address for veth1baa353: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044131]: Could not generate persistent MAC address for veth3994659: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044108]: Could not generate persistent MAC address for vethea9457d: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044122]: Could not generate persistent MAC address for veth5f43731: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044122]: Could not generate persistent MAC address for veth7e2258d: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044114]: Could not generate persistent MAC address for veth8089f93: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044115]: Could not generate persistent MAC address for veth1469234: No such file or directory
Sep 26 06:34:29 sentry-docker00.cs.umd.edu systemd-udevd[4044114]: Could not generate persistent MAC address for veth70c71fe: No such file or directory
Sep 26 06:54:37 sentry-docker00.cs.umd.edu systemd-udevd[4053527]: link_config: could not get ethtool features for veth1469234
Sep 26 06:54:37 sentry-docker00.cs.umd.edu systemd-udevd[4053527]: Could not set offload features of veth1469234: No such device
Sep 26 06:54:37 sentry-docker00.cs.umd.edu systemd-udevd[4053530]: link_config: could not get ethtool features for vethc17888a
Sep 26 06:54:37 sentry-docker00.cs.umd.edu systemd-udevd[4053530]: Could not set offload features of vethc17888a: No such device
Sep 26 06:54:38 sentry-docker00.cs.umd.edu systemd-udevd[4053558]: Could not generate persistent MAC address for vethec219b6: No such file or directory
Sep 26 06:54:38 sentry-docker00.cs.umd.edu systemd-udevd[4053560]: Could not generate persistent MAC address for vethbae44a9: No such file or directory
... 8 more distinct messages not shown
== strawberry (9 distinct, 46 total) ==
Sep 26 06:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 26 06:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 26 06:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x7]
Sep 26 06:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x7]
Sep 26 06:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x7]
Sep 26 06:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x7]
Sep 26 06:31:04 strawberry nologin[3662295]: Attempted login by UNKNOWN (UID: 65534) on UNKNOWN
Sep 26 06:31:04 strawberry pipewire[3662294]: 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 26 06:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f1 (9 distinct, 9 total) ==
Sep 26 06:25:56 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c
Sep 26 06:25:56 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36
Sep 26 06:25:56 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6
Sep 26 06:25:56 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GuT6qc/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d
Sep 26 06:25:57 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee
Sep 26 06:25:57 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GuT6qc. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8
Sep 26 06:25:57 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d
Sep 26 06:25:57 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9
Sep 26 06:25:57 submit26-b9-f1 setroubleshoot[3753010]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848
== submit26-b9-f2 (9 distinct, 12 total) ==
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: 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 [x2]
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.xPfz1e/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2]
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: 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 [x2]
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.xPfz1e. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af
Sep 26 06:06:51 submit26-b9-f2 setroubleshoot[2831428]: 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
== teaching-awards (1 distinct, 1 total) ==
Sep 26 06:30:11 teaching-awards sshd-session[1696366]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth]
== tlsrpt (1 distinct, 1 total) ==
Sep 26 06:38:03 tlsrpt (httpd)[3220193]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
== wraith (3 distinct, 3 total) ==
Sep 26 07:01:48 wraith (smartd)[55612]: smartmontools.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts
Sep 26 07:01:48 wraith (nin-node)[55625]: munin-node.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
Sep 26 07:01:49 wraith systemd[1]: resmon.service: Supervising process 55963 which is not our child. We'll most likely not notice when it exits.
1
0
Command: /usr/local/sbin/syslog-digest.py
Time : 7.5015s
Status : exited 0
Output :
Syslog digest — 2026-09-26 06:05 EDT
Processed 120,092 lines, filtered 1,728 (1%). 118,364 unknown (154 distinct) from 15 host(s).
== b0b02.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 06:01:06 b0b02.cs.umd.edu rustdesk[1232075]: cannot open display:
== grades01.cs.umd.edu (1 distinct, 1 total) ==
Sep 26 05:48:19 grades01.cs.umd.edu puppet-agent[10880]: The directory '/srv/grades' contains 2471 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees
== idm00 (1 distinct, 1 total) ==
Sep 26 05:54:08 idm00 named[4166701]: client @0x7f11a00218e8 10.73.240.42#49530: update '73.10.in-addr.arpa/IN' denied
== idmp0 (1 distinct, 1 total) ==
Sep 26 05:39:29 idmp0 named[1598691]: client @0x7f2d440131e8 10.73.240.43#49306: update '73.10.in-addr.arpa/IN' denied
== itmon02 (1 distinct, 4 total) ==
Sep 26 05:18:45 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4]
== matrix (12 distinct, 14 total) ==
Sep 26 05:27:46 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3742988, but reception only permitted for main PID 720
Sep 26 05:27:46 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3742992, but reception only permitted for main PID 720
Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743101, but reception only permitted for main PID 720
Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743105, but reception only permitted for main PID 720
Sep 26 05:27:54 matrix networkctl[3743118]: Interface "veth78752a8" not found.
Sep 26 05:27:54 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743118, but reception only permitted for main PID 720 [x2]
Sep 26 05:27:55 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743197, but reception only permitted for main PID 720
Sep 26 05:27:55 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3743210, but reception only permitted for main PID 720
Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745974, but reception only permitted for main PID 720
Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745980, but reception only permitted for main PID 720
Sep 26 05:31:24 matrix networkctl[3745993]: Interface "vethdc4eeee" not found.
Sep 26 05:31:24 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 3745993, but reception only permitted for main PID 720 [x2]
== munin (2 distinct, 8 total) ==
Sep 26 05:18:49 munin sudo[3775227]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4]
Sep 26 05:18:49 munin sudo[3775227]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4]
== newhonors2 (1 distinct, 24 total) ==
Sep 26 05:13:03 newhonors2 dhcpcd[3171022]: dhcpcd is not running [x24]
== ntop00 (70 distinct, 118204 total) ==
Sep 26 05:05:01 ntop00 nfacctd[381405]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x10]
Sep 26 05:05: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 26 05:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 514) ***
Sep 26 05:05:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 514, QN: 0/81, ET: 0) ***
Sep 26 05:05:02 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 ] [x7858]
Sep 26 05:05:02 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 ] [x56329]
Sep 26 05:05:02 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 ] [x53486]
Sep 26 05:05:15 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 ] [x216]
Sep 26 05:05:15 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 ] [x216]
Sep 26 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 26 05:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 5088/5088, ET: 0) ***
Sep 26 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 515) ***
Sep 26 05:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 515, QN: 60/60, ET: 0) ***
Sep 26 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): PRIMARY 'mysql' backend trouble. [x8]
Sep 26 05:10:01 ntop00 sfacctd[381335]: ERROR ( m1/mysql ): The SQL server says: Can't connect to MySQL server on '127.0.0.1' (115) [x8]
Sep 26 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 26 05:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 0/5285, ET: 0) ***
Sep 26 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 516) ***
Sep 26 05:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 516, QN: 0/58, ET: 0) ***
Sep 26 05:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 26 05:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 0/4905, ET: 0) ***
Sep 26 05:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 518) ***
Sep 26 05:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 518, QN: 0/60, ET: 0) ***
Sep 26 05:15:02 ntop00 rsyslogd[1208]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2510.0-5.el10_2.1 try https://www.rsyslog.com/e/2027 ] [x3]
Sep 26 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 26 05:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 5882/5882, ET: 0) ***
Sep 26 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 519) ***
Sep 26 05:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 519, QN: 70/70, ET: 0) ***
Sep 26 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 520) ***
Sep 26 05:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 520, QN: 0/51, ET: 0) ***
... 40 more distinct messages not shown
== outbound00.cs.umd.edu (1 distinct, 6 total) ==
Sep 26 05:09:09 outbound00.cs.umd.edu python3[4000563]: ldapdb [x6]
== outbound01.cs.umd.edu (2 distinct, 8 total) ==
Sep 26 05:08:33 outbound01.cs.umd.edu python3[2065100]: ldapdb [x7]
Sep 26 05:09:42 outbound01.cs.umd.edu systemd[1]: Configuration file /usr/lib/systemd/system/authentication_milter.service is marked executable. Please remove executable permission bits. Proceeding anyway.
== sentry-docker00.cs.umd.edu (36 distinct, 36 total) ==
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006076]: link_config: could not get ethtool features for veth8572ff8
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006076]: Could not set offload features of veth8572ff8: No such device
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006100]: Could not generate persistent MAC address for veth85b7b06: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006101]: Could not generate persistent MAC address for vethf96ac07: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethe6b076a: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006139]: Could not generate persistent MAC address for vethfb74621: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006164]: Could not generate persistent MAC address for vethc6750ce: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethfe87997: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006138]: Could not generate persistent MAC address for vethf36c608: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006164]: Could not generate persistent MAC address for veth0bac43c: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006161]: Could not generate persistent MAC address for vethfd91ef0: No such file or directory
Sep 26 05:13:56 sentry-docker00.cs.umd.edu systemd-udevd[4006155]: Could not generate persistent MAC address for veth02f732f: No such file or directory
Sep 26 05:34:04 sentry-docker00.cs.umd.edu systemd-udevd[4015734]: link_config: could not get ethtool features for vethc6750ce
Sep 26 05:34:04 sentry-docker00.cs.umd.edu systemd-udevd[4015734]: Could not set offload features of vethc6750ce: No such device
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015770]: Could not generate persistent MAC address for vethb6d68df: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015771]: Could not generate persistent MAC address for veth77a0ba2: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015774]: Could not generate persistent MAC address for vethbded419: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015775]: Could not generate persistent MAC address for veth7de582a: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015798]: Could not generate persistent MAC address for vethcf63320: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015799]: Could not generate persistent MAC address for veth8c3e104: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015817]: Could not generate persistent MAC address for veth9716d80: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015824]: Could not generate persistent MAC address for veth6e173b1: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015842]: Could not generate persistent MAC address for vethd88ef8d: No such file or directory
Sep 26 05:34:05 sentry-docker00.cs.umd.edu systemd-udevd[4015845]: Could not generate persistent MAC address for veth5768623: No such file or directory
Sep 26 05:54:12 sentry-docker00.cs.umd.edu systemd-udevd[4025194]: link_config: could not get ethtool features for vethb6d68df
Sep 26 05:54:12 sentry-docker00.cs.umd.edu systemd-udevd[4025194]: Could not set offload features of vethb6d68df: No such device
Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025228]: Could not generate persistent MAC address for vethb268998: No such file or directory
Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025229]: Could not generate persistent MAC address for veth95b4a7a: No such file or directory
Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025232]: Could not generate persistent MAC address for veth6d2ebc4: No such file or directory
Sep 26 05:54:13 sentry-docker00.cs.umd.edu systemd-udevd[4025233]: Could not generate persistent MAC address for veth3a2568d: No such file or directory
... 6 more distinct messages not shown
== strawberry (7 distinct, 38 total) ==
Sep 26 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 05:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 05:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6]
Sep 26 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6]
Sep 26 05:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6]
Sep 26 05:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6]
Sep 26 05:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2]
== submit26-b9-f3 (9 distinct, 9 total) ==
Sep 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Yj2SEV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f
Sep 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Yj2SEV. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd
Sep 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: 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 26 05:06:45 submit26-b9-f3 setroubleshoot[3510578]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68
== submit26-b9-f4 (9 distinct, 9 total) ==
Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.x38Vqy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0
Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.x38Vqy. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c
Sep 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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 26 05:24:49 submit26-b9-f4 setroubleshoot[2569862]: 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