Command: /usr/local/sbin/syslog-digest.py Time : 0.0451s Status : exited 0 Output : Syslog digest — 2026-10-04 03:05 EDT Processed 1,699 lines, filtered 1,383 (81%). 316 unknown (175 distinct) from 13 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 4 02:12:39 b0b02.cs.umd.edu rustdesk[4175244]: cannot open display: == gle-dind02.cs.umd.edu (6 distinct, 6 total) == Oct 4 02:51:13 gle-dind02.cs.umd.edu systemd-udevd[671594]: link_config: could not get ethtool features for veth4c798f8 Oct 4 02:51:13 gle-dind02.cs.umd.edu systemd-udevd[671594]: Could not set offload features of veth4c798f8: No such device Oct 4 02:51:13 gle-dind02.cs.umd.edu systemd-udevd[671613]: Could not generate persistent MAC address for vethd8bb2e5: No such file or directory Oct 4 02:51:13 gle-dind02.cs.umd.edu systemd-udevd[671614]: Could not generate persistent MAC address for vethe1ed306: No such file or directory Oct 4 02:51:15 gle-dind02.cs.umd.edu systemd-udevd[671730]: Could not generate persistent MAC address for veth35394eb: No such file or directory Oct 4 02:51:15 gle-dind02.cs.umd.edu systemd-udevd[671731]: Could not generate persistent MAC address for veth1ae118d: No such file or directory == idm00 (1 distinct, 1 total) == Oct 4 02:54:37 idm00 named[4166701]: client @0x7f11980829a8 10.73.240.42#61594: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 4 02:39:23 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#52687: update '73.10.in-addr.arpa/IN' denied == newhonors2 (1 distinct, 24 total) == Oct 4 02:13:03 newhonors2 dhcpcd[3529971]: dhcpcd is not running [x24] == ntop00 (98 distinct, 98 total) == Oct 4 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2746) *** Oct 4 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2746, QN: 68/68, ET: 0) *** Oct 4 02:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2746, QN: 3499/3499, ET: 5) *** Oct 4 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2747) *** Oct 4 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2747, QN: 3566/3566, ET: 0) *** Oct 4 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2747) *** Oct 4 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2747, QN: 69/69, ET: 0) *** Oct 4 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2748) *** Oct 4 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2748) *** Oct 4 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2748, QN: 70/70, ET: 0) *** Oct 4 02:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2748, QN: 3643/3643, ET: 5) *** Oct 4 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2749) *** Oct 4 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2749, QN: 3644/3644, ET: 0) *** Oct 4 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2749) *** Oct 4 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2749, QN: 78/78, ET: 0) *** Oct 4 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2750) *** Oct 4 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2750) *** Oct 4 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2750, QN: 66/66, ET: 0) *** Oct 4 02:15:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2750, QN: 3534/3534, ET: 5) *** Oct 4 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2751) *** Oct 4 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2751, QN: 3490/3490, ET: 0) *** Oct 4 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2751) *** Oct 4 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 2751, QN: 83/83, ET: 0) *** Oct 4 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2752) *** Oct 4 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 2752) *** Oct 4 02:20:02 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2752, QN: 97/97, ET: 1) *** Oct 4 02:20:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 2752, QN: 3508/3508, ET: 5) *** Oct 4 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 2753) *** Oct 4 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 2753, QN: 3472/3472, ET: 0) *** Oct 4 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 2753) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 4 02:09:09 outbound00.cs.umd.edu python3[2508016]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Oct 4 02:12:52 outbound01.cs.umd.edu krb5_child[580840]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 4 02:13:07 outbound01.cs.umd.edu python3[581071]: ldapdb [x6] Oct 4 02:14:10 outbound01.cs.umd.edu sshd-session[581296]: error: Protocol major versions differ: 2 vs. 1 == portal (1 distinct, 74 total) == Oct 4 02:05:11 portal setroubleshoot[700993]: 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 [x74] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Oct 4 02:12:16 sentry-docker00.cs.umd.edu systemd-udevd[959272]: link_config: could not get ethtool features for veth0dacb5c Oct 4 02:12:16 sentry-docker00.cs.umd.edu systemd-udevd[959272]: Could not set offload features of veth0dacb5c: No such device Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959341]: Could not generate persistent MAC address for veth65a74bf: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959342]: Could not generate persistent MAC address for veth58a9add: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959345]: Could not generate persistent MAC address for vethda18788: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959346]: Could not generate persistent MAC address for vethcc0f9ef: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959360]: Could not generate persistent MAC address for veth11299af: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959345]: Could not generate persistent MAC address for vethbacad6a: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959356]: Could not generate persistent MAC address for vethd3db72e: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959358]: Could not generate persistent MAC address for vethd7b3253: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959396]: Could not generate persistent MAC address for veth794218e: No such file or directory Oct 4 02:12:17 sentry-docker00.cs.umd.edu systemd-udevd[959400]: Could not generate persistent MAC address for veth30a5b38: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968812]: link_config: could not get ethtool features for vethda18788 Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968812]: Could not set offload features of vethda18788: No such device Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968843]: Could not generate persistent MAC address for veth0550a72: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968844]: Could not generate persistent MAC address for veth40b6600: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968862]: Could not generate persistent MAC address for veth94aa187: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968868]: Could not generate persistent MAC address for vethbd68202: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968854]: Could not generate persistent MAC address for veth074827e: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968857]: Could not generate persistent MAC address for vethe46bab8: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968921]: Could not generate persistent MAC address for vethb1a2a46: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968925]: Could not generate persistent MAC address for vethaa9242a: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968942]: Could not generate persistent MAC address for veth3e2abba: No such file or directory Oct 4 02:32:25 sentry-docker00.cs.umd.edu systemd-udevd[968939]: Could not generate persistent MAC address for vethc332fc3: No such file or directory Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978475]: link_config: could not get ethtool features for veth3e2abba Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978475]: Could not set offload features of veth3e2abba: No such device Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978507]: Could not generate persistent MAC address for veth2d94a28: No such file or directory Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978508]: Could not generate persistent MAC address for veth7978269: No such file or directory Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978511]: Could not generate persistent MAC address for veth7fc2166: No such file or directory Oct 4 02:52:33 sentry-docker00.cs.umd.edu systemd-udevd[978512]: Could not generate persistent MAC address for veth7d21784: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 4 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 4 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 4 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 4 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 4 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 4 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 4 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 14 total) == Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 [x2] Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 [x2] Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GZhtik/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GZhtik. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 [x2] Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: 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 [x2] Oct 4 02:26:00 submit26-b9-f1 setroubleshoot[789117]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hDQYqv. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (9 distinct, 9 total) == Oct 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.ST9D9j/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Oct 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.ST9D9j. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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 4 02:06:54 submit26-b9-f2 setroubleshoot[4092030]: 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