Command: /usr/local/sbin/syslog-digest.py Time : 0.0422s Status : exited 0 Output : Syslog digest — 2026-09-28 03:05 EDT Processed 2,117 lines, filtered 1,865 (88%). 252 unknown (173 distinct) from 16 host(s). == atif01.cs.umd.edu (3 distinct, 3 total) == Sep 28 02:27:31 atif01.cs.umd.edu kernel: net_ratelimit: 9 callbacks suppressed Sep 28 02:27:39 atif01.cs.umd.edu kernel: net_ratelimit: 2 callbacks suppressed Sep 28 02:27:39 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 28 03:03:54 b0b02.cs.umd.edu rustdesk[1921774]: cannot open display: == idm00 (1 distinct, 1 total) == Sep 28 02:54:10 idm00 named[4166701]: client @0x7f11a93d3738 10.73.240.42#62461: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 28 02:39:27 idmp0 named[1598691]: client @0x7f2d4802a308 10.73.240.43#59508: update '73.10.in-addr.arpa/IN' denied == inbound01.cs.umd.edu (1 distinct, 1 total) == Sep 28 02:28:34 inbound01.cs.umd.edu krb5_child[2814826]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 2 total) == Sep 28 02:38:10 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 16 total) == Sep 28 02:08:25 munin sudo[558011]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Sep 28 02:08:25 munin sudo[558011]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == newhonors2 (1 distinct, 24 total) == Sep 28 02:13:03 newhonors2 dhcpcd[3256178]: dhcpcd is not running [x24] == ntop00 (96 distinct, 96 total) == Sep 28 02:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 144) *** Sep 28 02:05:02 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 144, QN: 81/81, ET: 1) *** Sep 28 02:05:09 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 145, QN: 4870/4870, ET: 8) *** Sep 28 02:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 145) *** Sep 28 02:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 145, QN: 89/89, ET: 0) *** Sep 28 02:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 146) *** Sep 28 02:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 146, QN: 79/79, ET: 0) *** Sep 28 02:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 146) *** Sep 28 02:10:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 147) *** Sep 28 02:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 146, QN: 5095/5095, ET: 0) *** Sep 28 02:10:08 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 147, QN: 5095/5095, ET: 7) *** Sep 28 02:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 147) *** Sep 28 02:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 147, QN: 70/70, ET: 0) *** Sep 28 02:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 148) *** Sep 28 02:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 148) *** Sep 28 02:15:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 149) *** Sep 28 02:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 148, QN: 3963/3963, ET: 0) *** Sep 28 02:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 148, QN: 83/83, ET: 0) *** Sep 28 02:15:06 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 149, QN: 3963/3963, ET: 5) *** Sep 28 02:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 149) *** Sep 28 02:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 149, QN: 87/87, ET: 0) *** Sep 28 02:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 151) *** Sep 28 02:20:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 150) *** Sep 28 02:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 151, QN: 4621/4621, ET: 0) *** Sep 28 02:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 150) *** Sep 28 02:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 150, QN: 88/88, ET: 0) *** Sep 28 02:20:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 150, QN: 4621/4621, ET: 6) *** Sep 28 02:21:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 151) *** Sep 28 02:21:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 151, QN: 90/90, ET: 0) *** Sep 28 02:25:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 152) *** ... 66 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 28 02:09:09 outbound00.cs.umd.edu python3[442699]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 28 02:13:06 outbound01.cs.umd.edu python3[2708997]: ldapdb [x6] == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084812]: link_config: could not get ethtool features for veth4bcb796 Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084812]: Could not set offload features of veth4bcb796: No such device Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084813]: link_config: could not get ethtool features for veth1daaebb Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084813]: Could not set offload features of veth1daaebb: No such device Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084843]: Could not generate persistent MAC address for veth0492dc2: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084844]: Could not generate persistent MAC address for veth0e82b04: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084847]: Could not generate persistent MAC address for veth651945f: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084848]: Could not generate persistent MAC address for vethd387ce9: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084869]: Could not generate persistent MAC address for veth2c520bd: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084847]: Could not generate persistent MAC address for veth403947a: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084881]: Could not generate persistent MAC address for veth127693d: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084877]: Could not generate persistent MAC address for veth4e2ff5c: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084918]: Could not generate persistent MAC address for vethd091d74: No such file or directory Sep 28 02:12:31 sentry-docker00.cs.umd.edu systemd-udevd[1084906]: Could not generate persistent MAC address for vethc36e8fb: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094417]: link_config: could not get ethtool features for veth651945f Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094417]: Could not set offload features of veth651945f: No such device Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094455]: Could not generate persistent MAC address for veth48ff612: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094456]: Could not generate persistent MAC address for veth55e73a1: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094459]: Could not generate persistent MAC address for veth9a1d88f: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094460]: Could not generate persistent MAC address for veth997339c: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094483]: Could not generate persistent MAC address for vethab1fb4e: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094484]: Could not generate persistent MAC address for vethcec79c6: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094503]: Could not generate persistent MAC address for vetha5abeca: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094509]: Could not generate persistent MAC address for vethfe4b697: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094500]: Could not generate persistent MAC address for veth1054e40: No such file or directory Sep 28 02:32:39 sentry-docker00.cs.umd.edu systemd-udevd[1094505]: Could not generate persistent MAC address for veth0d72f22: No such file or directory Sep 28 02:52:47 sentry-docker00.cs.umd.edu systemd-udevd[1103990]: link_config: could not get ethtool features for vetha5abeca Sep 28 02:52:47 sentry-docker00.cs.umd.edu systemd-udevd[1103990]: Could not set offload features of vetha5abeca: No such device Sep 28 02:52:48 sentry-docker00.cs.umd.edu systemd-udevd[1104037]: Could not generate persistent MAC address for veth5372078: No such file or directory Sep 28 02:52:48 sentry-docker00.cs.umd.edu systemd-udevd[1104038]: Could not generate persistent MAC address for veth0ed1de2: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 28 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 28 02:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 28 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 28 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 28 02:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 28 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 28 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.BA2Cyn/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.BA2Cyn. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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 Sep 28 02:25:57 submit26-b9-f1 setroubleshoot[4083669]: 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) == Sep 28 02:06:51 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:51 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:51 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.clm8Eb/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.clm8Eb. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: 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 Sep 28 02:06:52 submit26-b9-f2 setroubleshoot[3165164]: 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) == Sep 28 02:59:47 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL