Command: /usr/local/sbin/syslog-digest.py Time : 0.0486s Status : exited 0 Output : Syslog digest — 2026-09-30 02:05 EDT Processed 1,959 lines, filtered 1,547 (78%). 412 unknown (203 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 30 01:06:35 b0b02.cs.umd.edu rustdesk[2627263]: cannot open display: == biggulp.cs.umd.edu (10 distinct, 10 total) == Sep 30 01:27:58 biggulp.cs.umd.edu sshd-session[1110560]: pam_access(sshd:auth): access denied for user `admin' from `34.53.194.115' Sep 30 01:27:58 biggulp.cs.umd.edu krb5_child[1110562]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 30 01:27:58 biggulp.cs.umd.edu sshd-session[1110558]: error: PAM: System error for admin from 34.53.194.115 Sep 30 01:28:10 biggulp.cs.umd.edu sshd-session[1110604]: error: Protocol major versions differ: 2 vs. 1 Sep 30 02:03:38 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 02:03:38 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 02:03:40 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 02:03:40 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 02:03:42 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 02:03:42 biggulp.cs.umd.edu sshd-session[1116440]: error: kex_protocol_error: type 30 seq 7 [preauth] == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 30 01:33:17 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 30 01:54:22 idm00 named[4166701]: client @0x7f11980829a8 10.73.240.42#63882: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 30 01:39:27 idmp0 named[1598691]: client @0x7f2d4803e0e8 10.73.240.43#52290: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 30 01:18:56 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x4] == krispykreme.cs.umd.edu (6 distinct, 6 total) == Sep 30 01:54:09 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 30 01:54:09 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 30 01:54:11 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 30 01:54:11 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 30 01:54:13 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 30 01:54:13 krispykreme.cs.umd.edu sshd-session[80004]: error: kex_protocol_error: type 30 seq 7 [preauth] == munin (2 distinct, 2 total) == Sep 30 01:08:14 munin sudo[1581979]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 30 01:08:14 munin sudo[1581979]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 30 01:13:03 newhonors2 dhcpcd[3345495]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 30 01:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 30 01:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 84/84, ET: 0) *** Sep 30 01:05:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 30 01:05:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 5176/5176, ET: 8) *** Sep 30 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 30 01:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 4933/4933, ET: 0) *** Sep 30 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 30 01:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 81/81, ET: 0) *** Sep 30 01:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 30 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 30 01:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 70/70, ET: 0) *** Sep 30 01:10:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 4923/4923, ET: 7) *** Sep 30 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 30 01:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 4990/4990, ET: 0) *** Sep 30 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 30 01:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 62/62, ET: 0) *** Sep 30 01:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 30 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 30 01:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 81/81, ET: 0) *** Sep 30 01:15:08 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 5042/5042, ET: 7) *** Sep 30 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 30 01:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 5123/5123, ET: 0) *** Sep 30 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 30 01:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 66/66, ET: 0) *** Sep 30 01:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 30 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 30 01:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 60/60, ET: 0) *** Sep 30 01:20:09 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 5094/5094, ET: 8) *** Sep 30 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 30 01:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 5166/5166, ET: 0) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 30 01:09:09 outbound00.cs.umd.edu python3[1110842]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 30 01:13:06 outbound01.cs.umd.edu python3[3374760]: ldapdb [x6] == portal (1 distinct, 71 total) == Sep 30 01:05:29 portal setroubleshoot[3618844]: 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 [x71] == sebatinsky.cs.umd.edu (4 distinct, 4 total) == Sep 30 01:09:45 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts Sep 30 01:52:45 sebatinsky.cs.umd.edu kernel: hpet1: lost 2 rtc interrupts Sep 30 01:52:45 sebatinsky.cs.umd.edu kernel: hpet1: lost 4 rtc interrupts Sep 30 01:52:45 sebatinsky.cs.umd.edu kernel: hpet1: lost 3 rtc interrupts == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413602]: link_config: could not get ethtool features for veth60393f0 Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413602]: Could not set offload features of veth60393f0: No such device Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413628]: Could not generate persistent MAC address for vethf1df3f1: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413627]: Could not generate persistent MAC address for vethee0ccf3: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413653]: Could not generate persistent MAC address for veth003cacb: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413654]: Could not generate persistent MAC address for veth708eb03: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413672]: Could not generate persistent MAC address for vethc8e6c3b: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413666]: Could not generate persistent MAC address for veth75578de: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413682]: Could not generate persistent MAC address for vethcd56313: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413686]: Could not generate persistent MAC address for veth591808b: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413717]: Could not generate persistent MAC address for vethc584d1d: No such file or directory Sep 30 01:12:04 sentry-docker00.cs.umd.edu systemd-udevd[2413716]: Could not generate persistent MAC address for vethe4c6248: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423269]: link_config: could not get ethtool features for vethc8e6c3b Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423269]: Could not set offload features of vethc8e6c3b: No such device Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423307]: Could not generate persistent MAC address for veth514635b: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423308]: Could not generate persistent MAC address for vethdd52083: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423311]: Could not generate persistent MAC address for vethb77117e: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423312]: Could not generate persistent MAC address for veth447f8d2: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423329]: Could not generate persistent MAC address for vethff1e5c1: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423328]: Could not generate persistent MAC address for veth9d2f970: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423307]: Could not generate persistent MAC address for veth747f658: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423308]: Could not generate persistent MAC address for veth2344b18: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423339]: Could not generate persistent MAC address for veth540dcd4: No such file or directory Sep 30 01:32:12 sentry-docker00.cs.umd.edu systemd-udevd[2423340]: Could not generate persistent MAC address for veth13bb268: No such file or directory Sep 30 01:52:20 sentry-docker00.cs.umd.edu systemd-udevd[2432683]: link_config: could not get ethtool features for vethff1e5c1 Sep 30 01:52:20 sentry-docker00.cs.umd.edu systemd-udevd[2432683]: Could not set offload features of vethff1e5c1: No such device Sep 30 01:52:21 sentry-docker00.cs.umd.edu systemd-udevd[2432719]: Could not generate persistent MAC address for veth53aa69d: No such file or directory Sep 30 01:52:21 sentry-docker00.cs.umd.edu systemd-udevd[2432720]: Could not generate persistent MAC address for veth7418220: No such file or directory Sep 30 01:52:21 sentry-docker00.cs.umd.edu systemd-udevd[2432723]: Could not generate persistent MAC address for vethd315546: No such file or directory Sep 30 01:52:21 sentry-docker00.cs.umd.edu systemd-udevd[2432724]: Could not generate persistent MAC address for veth067ee3f: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 30 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 30 01:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 30 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 30 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 30 01:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 30 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 30 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 3 total) == Sep 30 01:08:11 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 4 total) == Sep 30 01:05:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (10 distinct, 14 total) == Sep 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LRR6pj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LRR6pj. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:06:46 submit26-b9-f3 setroubleshoot[212421]: 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 30 01:30:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (11 distinct, 19 total) == Sep 30 01:09:23 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 [x2] Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.nYHD1D/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 [x2] Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.nYHD1D. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 [x2] Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: 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 Sep 30 01:24:51 submit26-b9-f4 setroubleshoot[3198692]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JZr30E/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0