Command: /usr/local/sbin/syslog-digest.py Time : 0.0501s Status : exited 0 Output : Syslog digest — 2026-09-21 18:05 EDT Processed 1,895 lines, filtered 1,373 (72%). 522 unknown (187 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 17:54:12 b0b02.cs.umd.edu rustdesk[3703975]: cannot open display: == bale (5 distinct, 85 total) == Sep 21 17:05:10 bale setroubleshoot[1537329]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 21 17:05:10 bale setroubleshoot[1537329]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12] Sep 21 17:05:13 bale setroubleshoot[1537329]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 21 17:05:16 bale setroubleshoot[1537329]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x11] Sep 21 17:05:28 bale setroubleshoot[1537945]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x13] == cheezit.cs.umd.edu (2 distinct, 2 total) == Sep 21 17:38:50 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): Could not retrieve DisableProxy value: c0000225 Sep 21 17:38:50 cheezit.cs.umd.edu falcon-sensor-bpf[1347]: CrowdStrike(4): ConnectWithProxy: Unable to get application proxy host from CsConfig: c0000225 == csfw00a (1 distinct, 118 total) == Sep 21 17:04:03 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x118] == frozone (1 distinct, 1 total) == Sep 21 17:35:40 frozone systemd-tmpfiles[2305593]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == galax (1 distinct, 1 total) == Sep 21 17:53:05 galax kernel: workqueue: mmput_async_fn hogged CPU for >10000us 67 times, consider switching to WQ_UNBOUND == idm00 (1 distinct, 1 total) == Sep 21 17:54:02 idm00 named[4166701]: client @0x7f11a00218e8 10.73.240.42#50262: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 17:37:55 idmp0 named[1598691]: client @0x7f2d480190a8 10.73.240.43#63233: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 21 17:33:48 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == krispykreme.cs.umd.edu (3 distinct, 6 total) == Sep 21 17:30:07 krispykreme.cs.umd.edu sshd-session[797903]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214' [x2] Sep 21 17:30:07 krispykreme.cs.umd.edu krb5_child[797905]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 21 17:30:07 krispykreme.cs.umd.edu sshd-session[797901]: error: PAM: System error for admin from 193.187.110.214 [x2] == matrix (2 distinct, 6 total) == Sep 21 17:30:30 matrix krb5_child[1551]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 21 17:30:32 matrix sshd[1545]: error: PAM: Authentication failure for admin from 193.187.110.214 [x2] == munin (2 distinct, 4 total) == Sep 21 17:18:56 munin sudo[1424734]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 21 17:18:56 munin sudo[1424734]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 21 17:13:03 newhonors2 dhcpcd[2959044]: dhcpcd is not running [x24] == ntop00 (98 distinct, 142 total) == Sep 21 17:05:50 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 10089/10089, ET: 49) *** Sep 21 17:05:50 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 65/65, ET: 49) *** Sep 21 17:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 21 17:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 9441/9441, ET: 0) *** Sep 21 17:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 21 17:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 57/57, ET: 0) *** Sep 21 17:08:02 ntop00 setroubleshoot[1056825]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12] Sep 21 17:08:02 ntop00 setroubleshoot[1056825]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12] Sep 21 17:08:02 ntop00 setroubleshoot[1056825]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 17:08:02 ntop00 setroubleshoot[1056825]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12] Sep 21 17:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 21 17:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 21 17:10:55 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 11092/11092, ET: 54) *** Sep 21 17:10:55 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 48/48, ET: 54) *** Sep 21 17:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 21 17:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 11465/11465, ET: 0) *** Sep 21 17:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 21 17:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 51/51, ET: 0) *** Sep 21 17:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 21 17:15:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 21 17:15:52 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 10547/10547, ET: 51) *** Sep 21 17:15:52 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 49/49, ET: 51) *** Sep 21 17:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 21 17:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 10474/10474, ET: 0) *** Sep 21 17:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 21 17:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 54/54, ET: 0) *** Sep 21 17:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** Sep 21 17:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** Sep 21 17:20:51 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 10301/10301, ET: 50) *** Sep 21 17:20:51 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 70/70, ET: 50) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 17:09:09 outbound00.cs.umd.edu python3[2442508]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 21 17:13:06 outbound01.cs.umd.edu python3[509522]: ldapdb [x6] == quiss (2 distinct, 5 total) == Sep 21 17:08:50 quiss nautilus[1581193]: Attempted to add a non-existent file to the view. Sep 21 17:57:37 quiss krb5_child[1624438]: Preauthentication failed [x4] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932096]: link_config: could not get ethtool features for veth9c67fcd Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932096]: Could not set offload features of veth9c67fcd: No such device Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932131]: Could not generate persistent MAC address for vethd144b06: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932132]: Could not generate persistent MAC address for vethb26f7b1: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932135]: Could not generate persistent MAC address for veth3a9b366: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932136]: Could not generate persistent MAC address for veth054d80c: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932151]: Could not generate persistent MAC address for vethfa6a328: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932135]: Could not generate persistent MAC address for veth9391e0a: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932135]: Could not generate persistent MAC address for veth21b8857: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932157]: Could not generate persistent MAC address for veth2921da8: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932181]: Could not generate persistent MAC address for veth90890a4: No such file or directory Sep 21 17:09:13 sentry-docker00.cs.umd.edu systemd-udevd[932180]: Could not generate persistent MAC address for vetha17488d: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941722]: Could not generate persistent MAC address for vethbe5f4e8: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941723]: Could not generate persistent MAC address for veth142f112: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941726]: Could not generate persistent MAC address for veth7306b6b: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941727]: Could not generate persistent MAC address for veth624eefd: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941750]: Could not generate persistent MAC address for vetha86582b: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941751]: Could not generate persistent MAC address for vethcd29507: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941776]: Could not generate persistent MAC address for veth8914fda: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941777]: Could not generate persistent MAC address for veth1abcbc9: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941810]: Could not generate persistent MAC address for veth995305d: No such file or directory Sep 21 17:29:21 sentry-docker00.cs.umd.edu systemd-udevd[941813]: Could not generate persistent MAC address for veth6558ed0: No such file or directory Sep 21 17:49:29 sentry-docker00.cs.umd.edu systemd-udevd[951133]: link_config: could not get ethtool features for vetha86582b Sep 21 17:49:29 sentry-docker00.cs.umd.edu systemd-udevd[951133]: Could not set offload features of vetha86582b: No such device Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951165]: Could not generate persistent MAC address for veth19e5799: No such file or directory Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951166]: Could not generate persistent MAC address for veth84c2cc3: No such file or directory Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951169]: Could not generate persistent MAC address for veth6f0b9cb: No such file or directory Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951170]: Could not generate persistent MAC address for vethdef502b: No such file or directory Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951187]: Could not generate persistent MAC address for vethb2da204: No such file or directory Sep 21 17:49:30 sentry-docker00.cs.umd.edu systemd-udevd[951186]: Could not generate persistent MAC address for vethbd02027: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 21 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 17:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 17:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 3 total) == Sep 21 17:20:05 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 8 total) == Sep 21 17:08:22 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] == submit26-b9-f3 (10 distinct, 16 total) == Sep 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XxWgQp/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XxWgQp. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: 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 21 17:06:43 submit26-b9-f3 setroubleshoot[2327712]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 Sep 21 17:18:16 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f4 (10 distinct, 13 total) == Sep 21 17:18:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CciqKm/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:47 submit26-b9-f4 setroubleshoot[1681361]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CciqKm. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 21 17:24:48 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:48 submit26-b9-f4 setroubleshoot[1681361]: 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 21 17:24:48 submit26-b9-f4 setroubleshoot[1681361]: 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