Command: /usr/local/sbin/syslog-digest.py Time : 0.0512s Status : exited 0 Output : Syslog digest — 2026-09-20 22:05 EDT Processed 1,995 lines, filtered 1,450 (72%). 545 unknown (198 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 21:52:56 b0b02.cs.umd.edu rustdesk[3397319]: cannot open display: == bale (5 distinct, 90 total) == Sep 20 21:05:53 bale setroubleshoot[1280569]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 20 21:05:53 bale setroubleshoot[1280569]: 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 20 21:05:56 bale setroubleshoot[1280569]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 20 21:05:59 bale setroubleshoot[1280569]: 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 [x12] Sep 20 21:06:11 bale setroubleshoot[1281185]: 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 [x15] == cheezit.cs.umd.edu (6 distinct, 6 total) == Sep 20 21:46:07 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 21:46:07 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 21:46:09 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 21:46:09 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 21:46:11 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 21:46:11 cheezit.cs.umd.edu sshd-session[1367147]: error: kex_protocol_error: type 30 seq 7 [preauth] == csfw00a (1 distinct, 140 total) == Sep 20 21:04:49 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x140] == idm00 (1 distinct, 1 total) == Sep 20 21:54:00 idm00 named[4166701]: client @0x7f11a0062908 10.73.240.42#49275: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 21:37:56 idmp0 named[1598691]: client @0x7f2d3802f8f8 10.73.240.43#54734: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Sep 20 21:34:52 inbound00.cs.umd.edu krb5_child[2298408]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 2 total) == Sep 20 21:38:16 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (9 distinct, 9 total) == Sep 20 21:18:12 krispykreme.cs.umd.edu sshd-session[452223]: pam_access(sshd:auth): access denied for user `admin' from `193.187.110.214' Sep 20 21:18:12 krispykreme.cs.umd.edu krb5_child[452225]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 20 21:18:12 krispykreme.cs.umd.edu sshd-session[452221]: error: PAM: System error for admin from 193.187.110.214 Sep 20 21:58:20 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 21:58:20 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 21:58:21 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 21:58:21 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 21:58:23 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 21:58:23 krispykreme.cs.umd.edu sshd-session[464903]: error: kex_protocol_error: type 30 seq 7 [preauth] == matrix (2 distinct, 3 total) == Sep 20 21:25:39 matrix krb5_child[3498994]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 20 21:25:41 matrix sshd[3498969]: error: PAM: Authentication failure for admin from 193.187.110.214 == munin (2 distinct, 8 total) == Sep 20 21:33:20 munin sudo[993998]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 20 21:33:20 munin sudo[993998]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 20 21:13:02 newhonors2 dhcpcd[2921039]: dhcpcd is not running [x24] == ntop00 (100 distinct, 140 total) == Sep 20 21:05:31 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 7176/7176, ET: 30) *** Sep 20 21:05:31 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 88/88, ET: 30) *** Sep 20 21:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 20 21:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 7322/7322, ET: 0) *** Sep 20 21:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 20 21:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 52/52, ET: 0) *** Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x11] Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x11] Sep 20 21:08:02 ntop00 setroubleshoot[897288]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 20 21:08:02 ntop00 setroubleshoot[897288]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x11] Sep 20 21:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 20 21:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 20 21:10:29 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 7033/7033, ET: 28) *** Sep 20 21:10:30 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 50/50, ET: 29) *** Sep 20 21:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 20 21:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6743/6743, ET: 0) *** Sep 20 21:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 20 21:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 42/42, ET: 0) *** Sep 20 21:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 20 21:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 20 21:15:30 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6711/6711, ET: 29) *** Sep 20 21:15:30 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 49/49, ET: 29) *** Sep 20 21:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 20 21:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 7282/7282, ET: 0) *** Sep 20 21:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 20 21:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 56/56, ET: 0) *** Sep 20 21:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 20 21:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 20 21:20:37 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 7369/7369, ET: 36) *** Sep 20 21:20:38 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 56/56, ET: 37) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 21:09:09 outbound00.cs.umd.edu python3[2159290]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 21:13:06 outbound01.cs.umd.edu python3[225448]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371254]: link_config: could not get ethtool features for vethdae63ea Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371254]: Could not set offload features of vethdae63ea: No such device Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371283]: Could not generate persistent MAC address for vethe3db1ab: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371284]: Could not generate persistent MAC address for veth764c61a: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371287]: Could not generate persistent MAC address for veth8fa5827: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371288]: Could not generate persistent MAC address for veth1341e5d: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371288]: Could not generate persistent MAC address for veth0b14eb0: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371300]: Could not generate persistent MAC address for veth39e0e50: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371283]: Could not generate persistent MAC address for vethbc14b63: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371303]: Could not generate persistent MAC address for veth2719d2b: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371377]: Could not generate persistent MAC address for vethd0f618e: No such file or directory Sep 20 21:21:02 sentry-docker00.cs.umd.edu systemd-udevd[371378]: Could not generate persistent MAC address for vethed3ac50: No such file or directory Sep 20 21:41:10 sentry-docker00.cs.umd.edu systemd-udevd[380895]: link_config: could not get ethtool features for vethbc14b63 Sep 20 21:41:10 sentry-docker00.cs.umd.edu systemd-udevd[380895]: Could not set offload features of vethbc14b63: No such device Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380929]: Could not generate persistent MAC address for vethcd5c892: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380930]: Could not generate persistent MAC address for vethbc08448: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380933]: Could not generate persistent MAC address for veth4bd5303: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380935]: Could not generate persistent MAC address for veth44c9cbe: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380944]: Could not generate persistent MAC address for veth95cf018: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380940]: Could not generate persistent MAC address for veth180ebcd: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380946]: Could not generate persistent MAC address for veth9827b60: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380945]: Could not generate persistent MAC address for veth83b4502: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380955]: Could not generate persistent MAC address for veth2200e39: No such file or directory Sep 20 21:41:11 sentry-docker00.cs.umd.edu systemd-udevd[380937]: Could not generate persistent MAC address for veth89d4c33: No such file or directory Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390519]: link_config: could not get ethtool features for veth9827b60 Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390519]: Could not set offload features of veth9827b60: No such device Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390544]: Could not generate persistent MAC address for vethd17332f: No such file or directory Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390545]: Could not generate persistent MAC address for veth6c0b4d0: No such file or directory Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390548]: Could not generate persistent MAC address for veth6316cfc: No such file or directory Sep 20 22:01:19 sentry-docker00.cs.umd.edu systemd-udevd[390549]: Could not generate persistent MAC address for vethff53c67: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 20 21:54:35 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 3 total) == Sep 20 21:08:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (10 distinct, 15 total) == Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.yphl3N/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.yphl3N. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:06:43 submit26-b9-f3 setroubleshoot[2175733]: 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 20 21:12:26 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f4 (10 distinct, 14 total) == Sep 20 21:15:06 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.csCqFH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.csCqFH. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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 20 21:24:46 submit26-b9-f4 setroubleshoot[1565218]: 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