Command: /usr/local/sbin/syslog-digest.py Time : 0.0463s Status : exited 0 Output : Syslog digest — 2026-09-29 02:05 EDT Processed 1,661 lines, filtered 1,277 (76%). 384 unknown (183 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 29 01:05:13 b0b02.cs.umd.edu rustdesk[2259103]: cannot open display: == hazfs.cs.umd.edu (11 distinct, 66 total) == Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: send response: Failure in sendto [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userweb" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."zfslist" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendStatus."userhome" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userweb" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."zfslist" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutput1Line."userhome" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userweb" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."zfslist" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutputFull."userhome" [x6] Sep 29 01:32:43 hazfs.cs.umd.edu snmpd[1431]: -- NET-SNMP-EXTEND-MIB::nsExtendOutNumLines."userweb" [x6] == idm00 (1 distinct, 1 total) == Sep 29 01:54:11 idm00 named[4166701]: client @0x7f11986ceb28 10.73.240.42#50627: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 29 01:39:28 idmp0 named[1598691]: client @0x7f2d34106cd8 10.73.240.43#64369: update '73.10.in-addr.arpa/IN' denied == irb2156 (2 distinct, 2 total) == Sep 29 01:07:35 irb2156 systemd-resolved[3579]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 100.100.100.100. Sep 29 01:42:52 irb2156 systemd[1]: cgroup compatibility translation between legacy and unified hierarchy settings activated. See cgroup-compat debug messages for details. == itmon02 (1 distinct, 2 total) == Sep 29 01:17:59 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 12 total) == Sep 29 01:48:43 munin sudo[1072797]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 29 01:48:43 munin sudo[1072797]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors2 (1 distinct, 24 total) == Sep 29 01:13:03 newhonors2 dhcpcd[3300232]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Sep 29 01:05:05 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 2941/2941, ET: 4) *** Sep 29 01:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 29 01:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 4097/4097, ET: 0) *** Sep 29 01:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 29 01:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 64/64, ET: 0) *** Sep 29 01:10:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 29 01:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 29 01:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 66/66, ET: 0) *** Sep 29 01:10:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 4765/4765, ET: 6) *** Sep 29 01:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 29 01:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 4997/4997, ET: 0) *** Sep 29 01:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 29 01:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 56/56, ET: 0) *** Sep 29 01:15:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 29 01:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 29 01:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 40/40, ET: 0) *** Sep 29 01:15:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 4485/4485, ET: 6) *** Sep 29 01:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 29 01:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 3734/3734, ET: 0) *** Sep 29 01:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 29 01:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 39/39, ET: 0) *** Sep 29 01:20:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 29 01:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 29 01:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 48/48, ET: 0) *** Sep 29 01:20:06 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 3763/3763, ET: 5) *** Sep 29 01:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 29 01:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 3563/3563, ET: 0) *** Sep 29 01:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 29 01:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 56/56, ET: 0) *** Sep 29 01:25:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 426) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 29 01:09:09 outbound00.cs.umd.edu python3[767755]: ldapdb [x6] Sep 29 01:18:07 outbound00.cs.umd.edu krb5_child[769488]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 29 01:13:06 outbound01.cs.umd.edu python3[3034067]: ldapdb [x6] == portal (1 distinct, 72 total) == Sep 29 01:05:58 portal setroubleshoot[3308654]: 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 [x72] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739664]: link_config: could not get ethtool features for vethd0543ba Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739664]: Could not set offload features of vethd0543ba: No such device Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739699]: Could not generate persistent MAC address for veth20fd14d: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739700]: Could not generate persistent MAC address for vethe560e45: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739703]: Could not generate persistent MAC address for veth9deb5c7: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739704]: Could not generate persistent MAC address for vethf10b035: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739727]: Could not generate persistent MAC address for veth509681f: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739728]: Could not generate persistent MAC address for vethe3fc9f3: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739734]: Could not generate persistent MAC address for vethec950e7: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739750]: Could not generate persistent MAC address for vethaea25bb: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739766]: Could not generate persistent MAC address for vethec3ee98: No such file or directory Sep 29 01:22:09 sentry-docker00.cs.umd.edu systemd-udevd[1739765]: Could not generate persistent MAC address for veth98ac47a: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749299]: link_config: could not get ethtool features for veth20fd14d Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749299]: Could not set offload features of veth20fd14d: No such device Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749333]: Could not generate persistent MAC address for veth8e4efcd: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749334]: Could not generate persistent MAC address for vethdee868b: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749338]: Could not generate persistent MAC address for veth201d04b: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749337]: Could not generate persistent MAC address for veth04382af: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749361]: Could not generate persistent MAC address for veth16a2516: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749362]: Could not generate persistent MAC address for veth2dfc006: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749385]: Could not generate persistent MAC address for veth7b736f1: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749378]: Could not generate persistent MAC address for vethee79042: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749371]: Could not generate persistent MAC address for veth4fb04b1: No such file or directory Sep 29 01:42:17 sentry-docker00.cs.umd.edu systemd-udevd[1749366]: Could not generate persistent MAC address for vethc35182b: No such file or directory Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758694]: link_config: could not get ethtool features for veth4fb04b1 Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758694]: Could not set offload features of veth4fb04b1: No such device Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758733]: Could not generate persistent MAC address for vethe6b919f: No such file or directory Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758734]: Could not generate persistent MAC address for veth5e0dd75: No such file or directory Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758737]: Could not generate persistent MAC address for vethcf2e1c4: No such file or directory Sep 29 02:02:26 sentry-docker00.cs.umd.edu systemd-udevd[1758738]: Could not generate persistent MAC address for vetha0fe66e: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 29 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 29 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 29 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 29 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 29 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 29 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 29 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 29 01:23:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 1 total) == Sep 29 01:20:05 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 9 total) == Sep 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.kcPd5C/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.kcPd5C. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 29 01:06:46 submit26-b9-f3 setroubleshoot[4155691]: 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 == submit26-b9-f4 (10 distinct, 10 total) == Sep 29 01:18:08 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.opGVeY/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.opGVeY. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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 29 01:24:50 submit26-b9-f4 setroubleshoot[3017757]: 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