Command: /usr/local/sbin/syslog-digest.py Time : 0.0497s Status : exited 0 Output : Syslog digest — 2026-10-06 03:05 EDT Processed 2,972 lines, filtered 2,633 (88%). 339 unknown (183 distinct) from 20 host(s). == atif01.cs.umd.edu (4 distinct, 4 total) == Oct 6 02:21:40 atif01.cs.umd.edu kernel: net_ratelimit: 11 callbacks suppressed Oct 6 02:21:57 atif01.cs.umd.edu kernel: net_ratelimit: 21 callbacks suppressed Oct 6 02:22:41 atif01.cs.umd.edu kernel: net_ratelimit: 10 callbacks suppressed Oct 6 02:58:08 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 6 02:15:33 b0b02.cs.umd.edu rustdesk[712712]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Oct 6 02:05:13 cheezit.cs.umd.edu sshd-session[2497627]: error: Protocol major versions differ: 2 vs. 1 == idm00 (1 distinct, 1 total) == Oct 6 02:54:40 idm00 named[4166701]: client @0x7f11980497e8 10.73.240.42#61016: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 6 02:39:24 idmp0 named[1598691]: client @0x7f2d1c04f628 10.73.240.43#61193: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (2 distinct, 2 total) == Oct 6 02:37:34 inbound00.cs.umd.edu krb5_child[3371881]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 02:37:59 inbound00.cs.umd.edu sshd-session[3371971]: error: Protocol major versions differ: 2 vs. 1 == itmon02 (1 distinct, 8 total) == Oct 6 02:13:08 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x8] == munin (2 distinct, 12 total) == Oct 6 02:38:43 munin sudo[550637]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Oct 6 02:38:43 munin sudo[550637]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == netman.cs.umd.edu (2 distinct, 5 total) == Oct 6 02:27:11 netman.cs.umd.edu krb5_child[853848]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Oct 6 02:27:18 netman.cs.umd.edu sshd[853845]: error: PAM: Authentication failure for admin from 35.205.144.81 == newhonors2 (1 distinct, 24 total) == Oct 6 02:13:03 newhonors2 dhcpcd[3620659]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Oct 6 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3898) *** Oct 6 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3898, QN: 67/67, ET: 0) *** Oct 6 02:05:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3898, QN: 2903/2903, ET: 4) *** Oct 6 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3899) *** Oct 6 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3899, QN: 3347/3347, ET: 0) *** Oct 6 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3899) *** Oct 6 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3899, QN: 81/81, ET: 0) *** Oct 6 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3900) *** Oct 6 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3900) *** Oct 6 02:10:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3900, QN: 83/83, ET: 1) *** Oct 6 02:10:07 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3900, QN: 4181/4181, ET: 6) *** Oct 6 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3901) *** Oct 6 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3901, QN: 3968/3968, ET: 0) *** Oct 6 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3901) *** Oct 6 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3901, QN: 76/76, ET: 0) *** Oct 6 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3902) *** Oct 6 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3902, QN: 79/79, ET: 0) *** Oct 6 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3902) *** Oct 6 02:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3902, QN: 3414/3414, ET: 5) *** Oct 6 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3903) *** Oct 6 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 3903, QN: 88/88, ET: 0) *** Oct 6 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3903) *** Oct 6 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3903, QN: 3443/3443, ET: 0) *** Oct 6 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3904) *** Oct 6 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 3904) *** Oct 6 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3904, QN: 75/75, ET: 0) *** Oct 6 02:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 3904, QN: 3653/3653, ET: 5) *** Oct 6 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 3905) *** Oct 6 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 3905, QN: 3654/3654, ET: 0) *** Oct 6 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 3905) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Oct 6 02:09:09 outbound00.cs.umd.edu python3[3184474]: ldapdb [x6] Oct 6 02:30:16 outbound00.cs.umd.edu krb5_child[3189914]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (4 distinct, 9 total) == Oct 6 02:13:06 outbound01.cs.umd.edu python3[1258760]: ldapdb [x6] Oct 6 02:19:04 outbound01.cs.umd.edu krb5_child[1259865]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 6 02:19:30 outbound01.cs.umd.edu sshd-session[1259942]: error: Protocol major versions differ: 2 vs. 1 Oct 6 02:23:31 outbound01.cs.umd.edu sshd-session[1260935]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == portal (1 distinct, 73 total) == Oct 6 02:05:07 portal setroubleshoot[1344665]: 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 [x73] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310023]: link_config: could not get ethtool features for veth1e41acc Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310023]: Could not set offload features of veth1e41acc: No such device Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310057]: Could not generate persistent MAC address for veth018cbe6: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310058]: Could not generate persistent MAC address for veth1282126: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310061]: Could not generate persistent MAC address for veth397b34b: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310062]: Could not generate persistent MAC address for veth2fdd443: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310077]: Could not generate persistent MAC address for veth0d40047: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310072]: Could not generate persistent MAC address for veth0b69993: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310072]: Could not generate persistent MAC address for veth0ac93e5: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310077]: Could not generate persistent MAC address for veth6554465: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310090]: Could not generate persistent MAC address for veth85c566d: No such file or directory Oct 6 02:12:10 sentry-docker00.cs.umd.edu systemd-udevd[2310094]: Could not generate persistent MAC address for veth600e1c4: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319541]: link_config: could not get ethtool features for veth0d40047 Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319541]: Could not set offload features of veth0d40047: No such device Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319567]: Could not generate persistent MAC address for veth3aef7c6: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319568]: Could not generate persistent MAC address for vethaf38be3: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319571]: Could not generate persistent MAC address for veth1bd2652: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319572]: Could not generate persistent MAC address for vethefd4aaa: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319594]: Could not generate persistent MAC address for veth1929537: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319588]: Could not generate persistent MAC address for veth413a44a: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319597]: Could not generate persistent MAC address for veth2425641: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319598]: Could not generate persistent MAC address for vethd972b2a: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319650]: Could not generate persistent MAC address for vethda61ff6: No such file or directory Oct 6 02:32:19 sentry-docker00.cs.umd.edu systemd-udevd[2319651]: Could not generate persistent MAC address for vethca651e0: No such file or directory Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329236]: link_config: could not get ethtool features for veth1bd2652 Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329236]: Could not set offload features of veth1bd2652: No such device Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329270]: Could not generate persistent MAC address for veth71fdee4: No such file or directory Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329271]: Could not generate persistent MAC address for vethef69eaa: No such file or directory Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329274]: Could not generate persistent MAC address for veth46b6bc6: No such file or directory Oct 6 02:52:27 sentry-docker00.cs.umd.edu systemd-udevd[2329275]: Could not generate persistent MAC address for veth00c0d5d: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 6 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 6 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 6 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 6 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Oct 6 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Oct 6 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 6 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 3ef7d677-731f-46bf-9c34-c2c55fea665c Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l aa60e26f-72e1-45f1-bc12-aa8b3b669e36 Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l d088fb43-23ee-4ae8-ae6a-5d1c041ee2d6 Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.m9zjnj/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0fd3339f-3ef2-45f3-9e58-65a58b42f3ee Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.m9zjnj. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 405a8556-cf9f-4ef4-8525-0dca18d4259d Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 3c38e23e-3631-4cb5-81c7-992675c836d9 Oct 6 02:26:01 submit26-b9-f1 setroubleshoot[1216869]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l a070e9b5-2867-47d6-b2e3-3b7d99725848 == submit26-b9-f2 (9 distinct, 9 total) == Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 0659d546-3107-4f75-b00f-008c85f41dc6 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 156d9270-3466-4356-b86f-1a128825961a Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l c8a40bf5-2fc4-46b3-b813-8592b3523339 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.iBryuT/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 988123da-b724-4e6a-900c-33a2723fdaf1 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.iBryuT. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 3a749560-1cec-40ca-a4dc-596841be3885 Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 0aa52f08-94f8-474e-96d8-e818846941af Oct 6 02:06:55 submit26-b9-f2 setroubleshoot[315358]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l de019dc4-408f-439c-902a-676d18dfe8e7 == submit26-b9-f4 (1 distinct, 1 total) == Oct 6 02:08:51 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == wraith (3 distinct, 3 total) == Oct 6 02:18:31 wraith kernel: hrtimer: interrupt took 2836 ns Oct 6 02:34:24 wraith kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND Oct 6 02:35:47 wraith kernel: workqueue: output_poll_execute hogged CPU for >10000us 1027 times, consider switching to WQ_UNBOUND