Command: /usr/local/sbin/syslog-digest.py Time : 0.0456s Status : exited 0 Output : Syslog digest — 2026-10-02 03:05 EDT Processed 1,699 lines, filtered 1,366 (80%). 333 unknown (176 distinct) from 16 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Oct 2 02:09:30 b0b02.cs.umd.edu rustdesk[3444464]: cannot open display: == biggulp.cs.umd.edu (4 distinct, 4 total) == Oct 2 02:18:23 biggulp.cs.umd.edu sshd-session[1728515]: pam_access(sshd:auth): access denied for user `admin' from `34.78.238.107' Oct 2 02:18:24 biggulp.cs.umd.edu krb5_child[1728518]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 2 02:18:24 biggulp.cs.umd.edu sshd-session[1728513]: error: PAM: System error for admin from 34.78.238.107 Oct 2 02:18:42 biggulp.cs.umd.edu sshd-session[1728545]: error: Protocol major versions differ: 2 vs. 1 == cheezit.cs.umd.edu (4 distinct, 4 total) == Oct 2 02:56:39 cheezit.cs.umd.edu sshd-session[1167228]: pam_access(sshd:auth): access denied for user `admin' from `34.140.170.175' Oct 2 02:56:40 cheezit.cs.umd.edu krb5_child[1167230]: Client 'admin@UMD.EDU' not found in Kerberos database Oct 2 02:56:40 cheezit.cs.umd.edu sshd-session[1167226]: error: PAM: System error for admin from 34.140.170.175 Oct 2 02:57:01 cheezit.cs.umd.edu sshd-session[1167242]: error: Protocol major versions differ: 2 vs. 1 == idm00 (1 distinct, 1 total) == Oct 2 02:54:25 idm00 named[4166701]: client @0x7f11a4296188 10.73.240.42#51015: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Oct 2 02:39:27 idmp0 named[1598691]: client @0x7f2d2000e0b8 10.73.240.43#64391: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Oct 2 02:18:53 itmon02 sshd[805675]: error: beginning MaxStartups throttling [x5] == munin (2 distinct, 16 total) == Oct 2 02:28:10 munin sudo[2657168]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x8] Oct 2 02:28:10 munin sudo[2657168]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x8] == newhonors2 (1 distinct, 24 total) == Oct 2 02:13:03 newhonors2 dhcpcd[3439077]: dhcpcd is not running [x24] == ntop00 (95 distinct, 95 total) == Oct 2 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1594) *** Oct 2 02:05:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1594, QN: 45/45, ET: 0) *** Oct 2 02:05:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1594, QN: 3293/3293, ET: 5) *** Oct 2 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1595) *** Oct 2 02:08:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1595, QN: 3183/3183, ET: 0) *** Oct 2 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1595) *** Oct 2 02:08:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1595, QN: 44/44, ET: 0) *** Oct 2 02:10:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1596) *** Oct 2 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1596) *** Oct 2 02:10:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1596, QN: 53/53, ET: 0) *** Oct 2 02:10:06 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1596, QN: 3501/3501, ET: 5) *** Oct 2 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1597) *** Oct 2 02:13:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1597, QN: 3665/3665, ET: 0) *** Oct 2 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1597) *** Oct 2 02:13:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1597, QN: 53/53, ET: 0) *** Oct 2 02:15:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1598) *** Oct 2 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1598) *** Oct 2 02:15:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1598, QN: 49/49, ET: 0) *** Oct 2 02:15:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1598, QN: 3364/3364, ET: 4) *** Oct 2 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1599) *** Oct 2 02:18:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1599, QN: 3172/3172, ET: 0) *** Oct 2 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1599) *** Oct 2 02:18:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - END (PID: 1599, QN: 45/45, ET: 0) *** Oct 2 02:20:01 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1600) *** Oct 2 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - START (PID: 1600) *** Oct 2 02:20:01 ntop00 nfacctd[1075699]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1600, QN: 49/49, ET: 0) *** Oct 2 02:20:05 ntop00 sfacctd[1075592]: INFO ( m1/mysql ): *** Purging cache - END (PID: 1600, QN: 3208/3208, ET: 4) *** Oct 2 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - START (PID: 1601) *** Oct 2 02:23:01 ntop00 sfacctd[1075592]: INFO ( p1/print ): *** Purging cache - END (PID: 1601, QN: 3344/3344, ET: 0) *** Oct 2 02:23:01 ntop00 nfacctd[1075699]: INFO ( p1/print ): *** Purging cache - START (PID: 1601) *** ... 65 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Oct 2 02:09:08 outbound00.cs.umd.edu python3[1833488]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Oct 2 02:13:06 outbound01.cs.umd.edu python3[4098800]: ldapdb [x6] == portal (1 distinct, 73 total) == Oct 2 02:05:09 portal setroubleshoot[57222]: 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 (38 distinct, 38 total) == Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800013]: link_config: could not get ethtool features for vetha1f10c5 Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800013]: Could not set offload features of vetha1f10c5: No such device Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800067]: link_config: could not get ethtool features for vethb743bf3 Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800067]: Could not set offload features of vethb743bf3: No such device Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800123]: Could not generate persistent MAC address for vethca2f906: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800124]: Could not generate persistent MAC address for veth0c4b1fc: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800185]: Could not generate persistent MAC address for veth13201ae: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800186]: Could not generate persistent MAC address for vethc9b1316: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800210]: Could not generate persistent MAC address for veth97206db: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800212]: Could not generate persistent MAC address for vethe03eb3f: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800223]: Could not generate persistent MAC address for veth69b7658: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800228]: Could not generate persistent MAC address for veth9b9a34a: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800240]: Could not generate persistent MAC address for veth13b4cee: No such file or directory Oct 2 02:12:27 sentry-docker00.cs.umd.edu systemd-udevd[3800252]: Could not generate persistent MAC address for veth3ea14e9: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809584]: link_config: could not get ethtool features for vethca2f906 Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809584]: Could not set offload features of vethca2f906: No such device Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809620]: Could not generate persistent MAC address for veth61cf9e0: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809621]: Could not generate persistent MAC address for veth21047a8: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809624]: Could not generate persistent MAC address for veth66a3f74: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809625]: Could not generate persistent MAC address for veth361dfe4: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809630]: Could not generate persistent MAC address for vethc0b7274: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809634]: Could not generate persistent MAC address for veth4962a88: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809629]: Could not generate persistent MAC address for vethdac4bf7: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809630]: Could not generate persistent MAC address for vethfb6f2e6: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809725]: Could not generate persistent MAC address for veth8e49f45: No such file or directory Oct 2 02:32:35 sentry-docker00.cs.umd.edu systemd-udevd[3809727]: Could not generate persistent MAC address for veth0c15327: No such file or directory Oct 2 02:52:43 sentry-docker00.cs.umd.edu systemd-udevd[3819318]: link_config: could not get ethtool features for veth66a3f74 Oct 2 02:52:43 sentry-docker00.cs.umd.edu systemd-udevd[3819318]: Could not set offload features of veth66a3f74: No such device Oct 2 02:52:43 sentry-docker00.cs.umd.edu systemd-udevd[3819341]: Could not generate persistent MAC address for vethcb74773: No such file or directory Oct 2 02:52:43 sentry-docker00.cs.umd.edu systemd-udevd[3819342]: Could not generate persistent MAC address for vethe16a99b: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Oct 2 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 2 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 2 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Oct 2 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 2 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 2 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Oct 2 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.RCMo5q/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Oct 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.RCMo5q. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Oct 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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 2 02:25:59 submit26-b9-f1 setroubleshoot[498108]: 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, 12 total) == Oct 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 [x2] Oct 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.C7OqBy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Oct 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 [x2] Oct 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.C7OqBy. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Oct 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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 2 02:06:53 submit26-b9-f2 setroubleshoot[3810685]: 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