Command: /usr/local/sbin/syslog-digest.py Time : 0.0478s Status : exited 0 Output : Syslog digest — 2026-10-01 22:05 EDT Processed 1,815 lines, filtered 1,429 (78%). 386 unknown (202 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 1 21:09:10 b0b02.cs.umd.edu rustdesk[3367940]: cannot open display: == biggulp.cs.umd.edu (6 distinct, 6 total) == Oct 1 21:53:52 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 20 seq 2 [preauth] Oct 1 21:53:52 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 30 seq 3 [preauth] Oct 1 21:53:54 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 20 seq 4 [preauth] Oct 1 21:53:54 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 30 seq 5 [preauth] Oct 1 21:53:56 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 20 seq 6 [preauth] Oct 1 21:53:56 biggulp.cs.umd.edu sshd-session[1674372]: error: kex_protocol_error: type 30 seq 7 [preauth] == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 1 21:22:08 cheezit.cs.umd.edu systemd[1]: insights-client.service: Start request repeated too quickly. == gle-dind04 (5 distinct, 7 total) == Oct 1 21:52:16 gle-dind04 kernel: overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x2] Oct 1 21:52:16 gle-dind04 kernel: overlayfs: workdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [x2] Oct 1 21:55:11 gle-dind04 lldpd[1171]: unable to send packet on real device for veth4f9af23: No such device or address Oct 1 21:59:31 gle-dind04 lldpd[1171]: unable to send packet on real device for veth013d3fc: No such device or address Oct 1 22:00:01 gle-dind04 lldpd[1171]: unable to send packet on real device for vethf15dc35: No such device or address == idm00 (1 distinct, 1 total) == Oct 1 21:54:24 idm00 named[4166701]: client @0x7f11a4040908 10.73.240.42#56942: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 1 21:39:26 idmp0 named[1598691]: client @0x7f2d2c035088 10.73.240.43#61002: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Oct 1 21:18:54 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 26 total) == Oct 1 21:19:03 munin sudo[2545571]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x13] Oct 1 21:19:03 munin sudo[2545571]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x13] == netman.cs.umd.edu (2 distinct, 2 total) == Oct 1 21:53:51 netman.cs.umd.edu sshd[3307260]: error: type 20 seq 2 [preauth] Oct 1 21:53:51 netman.cs.umd.edu sshd[3307260]: error: type 30 seq 3 [preauth] == newhonors2 (3 distinct, 26 total) == Oct 1 21:13:03 newhonors2 dhcpcd[3429548]: dhcpcd is not running [x24] Oct 1 21:53:25 newhonors2 systemd[1]: choria-server.service: Found left-over process 3430966 (systemctl) in control group while starting unit. Ignoring. Oct 1 21:53:25 newhonors2 systemd[1]: choria-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. == ntop00 (98 distinct, 98 total) == Oct 1 21:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1474) *** Oct 1 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1474) *** Oct 1 21:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1474, QN: 46/46, ET: 0) *** Oct 1 21:05:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1474, QN: 5737/5737, ET: 7) *** Oct 1 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1475) *** Oct 1 21:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1475, QN: 5355/5355, ET: 0) *** Oct 1 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1475) *** Oct 1 21:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1475, QN: 46/46, ET: 0) *** Oct 1 21:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1476) *** Oct 1 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1476) *** Oct 1 21:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1476, QN: 52/52, ET: 0) *** Oct 1 21:10:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1476, QN: 5783/5783, ET: 8) *** Oct 1 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1477) *** Oct 1 21:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1477, QN: 6986/6986, ET: 0) *** Oct 1 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1477) *** Oct 1 21:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1477, QN: 60/60, ET: 0) *** Oct 1 21:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1478) *** Oct 1 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1478) *** Oct 1 21:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1478, QN: 62/62, ET: 0) *** Oct 1 21:15:10 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1478, QN: 6776/6776, ET: 9) *** Oct 1 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1479) *** Oct 1 21:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1479, QN: 5841/5841, ET: 0) *** Oct 1 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1479) *** Oct 1 21:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1479, QN: 55/55, ET: 0) *** Oct 1 21:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1480) *** Oct 1 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1480) *** Oct 1 21:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1480, QN: 46/46, ET: 0) *** Oct 1 21:20:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1480, QN: 5482/5482, ET: 7) *** Oct 1 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1481) *** Oct 1 21:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1481, QN: 5029/5029, ET: 0) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Oct 1 21:09:09 outbound00.cs.umd.edu python3[1763104]: ldapdb [x6] Oct 1 21:46:04 outbound00.cs.umd.edu sshd-session[1771539]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == outbound01.cs.umd.edu (2 distinct, 7 total) == Oct 1 21:11:50 outbound01.cs.umd.edu krb5_child[4027682]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 1 21:13:07 outbound01.cs.umd.edu python3[4027987]: ldapdb [x6] == portal (1 distinct, 75 total) == Oct 1 21:06:02 portal setroubleshoot[4183892]: SELinux is preventing /usr/local/bin/traefik from connectto access on the unix_stream_socket /run/podman/podman.sock. For complete SELinux messages run: sealert -l e0a307a3-2c22-4320-8f9d-6a166c45222d [x75] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658433]: link_config: could not get ethtool features for veth6bee059 Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658433]: Could not set offload features of veth6bee059: No such device Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658469]: Could not generate persistent MAC address for veth52fc3ae: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658470]: Could not generate persistent MAC address for veth8523922: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658473]: Could not generate persistent MAC address for veth7854a98: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658474]: Could not generate persistent MAC address for veth6128d39: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658497]: Could not generate persistent MAC address for vethcf7f6d4: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658498]: Could not generate persistent MAC address for veth2159bf4: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658516]: Could not generate persistent MAC address for vethe9a7178: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658511]: Could not generate persistent MAC address for veth0f0da88: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658526]: Could not generate persistent MAC address for veth60fa385: No such file or directory Oct 1 21:10:22 sentry-docker00.cs.umd.edu systemd-udevd[3658530]: Could not generate persistent MAC address for vethd81e273: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668310]: link_config: could not get ethtool features for veth60fa385 Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668310]: Could not set offload features of veth60fa385: No such device Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668346]: Could not generate persistent MAC address for veth89921ec: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668347]: Could not generate persistent MAC address for vethcdaaeab: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668350]: Could not generate persistent MAC address for veth11ad619: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668351]: Could not generate persistent MAC address for veth16bc27e: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668374]: Could not generate persistent MAC address for veth2b34a90: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668375]: Could not generate persistent MAC address for veth791d603: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668382]: Could not generate persistent MAC address for veth8348237: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668394]: Could not generate persistent MAC address for vethb639818: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668391]: Could not generate persistent MAC address for vethf6636eb: No such file or directory Oct 1 21:30:30 sentry-docker00.cs.umd.edu systemd-udevd[3668375]: Could not generate persistent MAC address for veth55db18c: No such file or directory Oct 1 21:50:38 sentry-docker00.cs.umd.edu systemd-udevd[3677389]: link_config: could not get ethtool features for veth2b34a90 Oct 1 21:50:38 sentry-docker00.cs.umd.edu systemd-udevd[3677389]: Could not set offload features of veth2b34a90: No such device Oct 1 21:50:38 sentry-docker00.cs.umd.edu systemd-udevd[3677485]: link_config: could not get ethtool features for veth8348237 Oct 1 21:50:38 sentry-docker00.cs.umd.edu systemd-udevd[3677485]: Could not set offload features of veth8348237: No such device Oct 1 21:50:39 sentry-docker00.cs.umd.edu systemd-udevd[3677514]: Could not generate persistent MAC address for veth595bf0f: No such file or directory Oct 1 21:50:39 sentry-docker00.cs.umd.edu systemd-udevd[3677515]: Could not generate persistent MAC address for veth562678e: No such file or directory ... 8 more distinct messages not shown == soul (1 distinct, 1 total) == Oct 1 22:00:17 soul krb5_child[2210144]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Oct 1 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 1 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 1 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 1 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 1 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 4 total) == Oct 1 21:10:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f2 (1 distinct, 4 total) == Oct 1 21:25:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (10 distinct, 16 total) == Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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] Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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] Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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 Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.WqCnr3/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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 Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.WqCnr3. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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 Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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 Oct 1 21:06:47 submit26-b9-f3 setroubleshoot[472911]: 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 Oct 1 21:07:19 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (10 distinct, 15 total) == Oct 1 21:05:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 [x2] Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 [x2] Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gql5Cq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gql5Cq. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 Oct 1 21:24:51 submit26-b9-f4 setroubleshoot[3380917]: 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 (6 distinct, 6 total) == Oct 1 21:53:52 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 20 seq 2 [preauth] Oct 1 21:53:52 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 30 seq 3 [preauth] Oct 1 21:53:54 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 20 seq 4 [preauth] Oct 1 21:53:54 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 30 seq 5 [preauth] Oct 1 21:53:56 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 20 seq 6 [preauth] Oct 1 21:53:56 teaching-awards sshd-session[2155833]: error: kex_protocol_error: type 30 seq 7 [preauth] == unknown (2 distinct, 2 total) == -using-explainable-ai using-explainable-ai