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@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@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@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@UMD.EDU' not found in Kerberos database [x2] Sep 26 14:55:23 netman.cs.umd.edu krb5_child[1037495]: Client 'backup@UMD.EDU' not found in Kerberos database [x2] Sep 26 14:58:57 netman.cs.umd.edu krb5_child[1038668]: Client 'elena@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@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