Command: /usr/local/sbin/syslog-digest.py Time : 0.0470s Status : exited 0 Output : Syslog digest — 2026-09-28 23:05 EDT Processed 1,742 lines, filtered 1,380 (79%). 362 unknown (188 distinct) from 23 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 28 22:05:03 b0b02.cs.umd.edu rustdesk[2212553]: cannot open display: == cheezit.cs.umd.edu (3 distinct, 5 total) == Sep 28 22:16:23 cheezit.cs.umd.edu sshd-session[4159808]: pam_access(sshd:auth): access denied for user `root' from `158.173.89.129' [x2] Sep 28 22:16:26 cheezit.cs.umd.edu sshd-session[4159806]: error: PAM: Authentication failure for root from 158.173.89.129 [x2] Sep 28 22:42:39 cheezit.cs.umd.edu sshd-session[4165709]: pam_access(sshd:auth): access denied for user `amchilds' from `108.56.227.155' == cmsc436-0101-redis (1 distinct, 2 total) == Sep 28 22:13:38 cmsc436-0101-redis sshd-session[3807084]: error: PAM: Authentication failure for root from 158.173.89.129 [x2] == idm00 (1 distinct, 1 total) == Sep 28 22:54:11 idm00 named[4166701]: client @0x7f11a93e0168 10.73.240.42#55236: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 28 22:39:27 idmp0 named[1598691]: client @0x7f2d480360f8 10.73.240.43#55829: update '73.10.in-addr.arpa/IN' denied == irb2156 (4 distinct, 4 total) == Sep 28 22:11:08 irb2156 systemd-resolved[3579]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.14. Sep 28 22:14:33 irb2156 systemd-resolved[3579]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 128.8.74.3. Sep 28 22:14:39 irb2156 systemd-resolved[3579]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 128.8.76.3. Sep 28 22:14:54 irb2156 systemd-resolved[3579]: Using degraded feature set TCP instead of UDP for DNS server 128.8.74.3. == itmon02 (1 distinct, 3 total) == Sep 28 22:38:27 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x3] == krispykreme.cs.umd.edu (3 distinct, 13 total) == Sep 28 22:09:09 krispykreme.cs.umd.edu sshd-session[3811383]: pam_access(sshd:auth): access denied for user `anwar' from `71.241.227.222' [x7] Sep 28 22:09:30 krispykreme.cs.umd.edu krb5_child[3811509]: Preauthentication failed [x3] Sep 28 22:09:30 krispykreme.cs.umd.edu sshd-session[3811477]: error: PAM: Authentication failure for anwar from 71.241.227.222 [x3] == matrix (2 distinct, 3 total) == Sep 28 22:45:45 matrix krb5_child[1807519]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 28 22:45:47 matrix sshd[1807513]: error: PAM: Authentication failure for admin from 34.34.147.151 == munin (2 distinct, 20 total) == Sep 28 22:28:57 munin sudo[1000211]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10] Sep 28 22:28:57 munin sudo[1000211]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10] == newhonors2 (1 distinct, 24 total) == Sep 28 22:13:03 newhonors2 dhcpcd[3294438]: dhcpcd is not running [x24] == ntop00 (94 distinct, 94 total) == Sep 28 22:05:06 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 3503/3503, ET: 5) *** Sep 28 22:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 28 22:08:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 3556/3556, ET: 0) *** Sep 28 22:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 28 22:08:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 78/78, ET: 0) *** Sep 28 22:10:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 28 22:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 28 22:10:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 64/64, ET: 0) *** Sep 28 22:10:07 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 3878/3878, ET: 6) *** Sep 28 22:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 28 22:13:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 4188/4188, ET: 0) *** Sep 28 22:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 28 22:13:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 67/67, ET: 0) *** Sep 28 22:15:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 28 22:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 28 22:15:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 82/82, ET: 0) *** Sep 28 22:15:08 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 3993/3993, ET: 7) *** Sep 28 22:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 28 22:18:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 3296/3296, ET: 0) *** Sep 28 22:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 28 22:18:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 71/71, ET: 0) *** Sep 28 22:20:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 28 22:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 28 22:20:01 ntop00 nfacctd[874460]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 67/67, ET: 0) *** Sep 28 22:20:05 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 2971/2971, ET: 4) *** Sep 28 22:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - START (PID: 353) *** Sep 28 22:23:01 ntop00 sfacctd[874386]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 2811/2811, ET: 0) *** Sep 28 22:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - START (PID: 353) *** Sep 28 22:23:01 ntop00 nfacctd[874460]: INFO ( p1/print ): *** Purging cache - END (PID: 353, QN: 64/64, ET: 0) *** Sep 28 22:25:01 ntop00 sfacctd[874386]: INFO ( m1/mysql ): *** Purging cache - START (PID: 354) *** ... 64 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 28 22:09:09 outbound00.cs.umd.edu python3[724821]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 28 22:13:06 outbound01.cs.umd.edu python3[2991175]: ldapdb [x6] == portal (1 distinct, 72 total) == Sep 28 22:05:35 portal setroubleshoot[3270220]: 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] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 28 22:44:44 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654858]: link_config: could not get ethtool features for veth62b54f5 Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654858]: Could not set offload features of veth62b54f5: No such device Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654891]: Could not generate persistent MAC address for veth390bdd7: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654892]: Could not generate persistent MAC address for vetha462907: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654895]: Could not generate persistent MAC address for vethd8cd8c0: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654899]: Could not generate persistent MAC address for veth1fe4d7b: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654911]: Could not generate persistent MAC address for vethbd46e9d: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654892]: Could not generate persistent MAC address for vethdaf417d: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654917]: Could not generate persistent MAC address for vetha3b0e14: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654897]: Could not generate persistent MAC address for veth0304dbe: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654923]: Could not generate persistent MAC address for vetha4d9047: No such file or directory Sep 28 22:20:54 sentry-docker00.cs.umd.edu systemd-udevd[1654924]: Could not generate persistent MAC address for vethd43d703: No such file or directory Sep 28 22:41:02 sentry-docker00.cs.umd.edu systemd-udevd[1663972]: link_config: could not get ethtool features for vetha3b0e14 Sep 28 22:41:02 sentry-docker00.cs.umd.edu systemd-udevd[1663972]: Could not set offload features of vetha3b0e14: No such device Sep 28 22:41:02 sentry-docker00.cs.umd.edu systemd-udevd[1663975]: link_config: could not get ethtool features for veth390bdd7 Sep 28 22:41:02 sentry-docker00.cs.umd.edu systemd-udevd[1663975]: Could not set offload features of veth390bdd7: No such device Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664010]: Could not generate persistent MAC address for veth783252b: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664011]: Could not generate persistent MAC address for veth362bbb5: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664015]: Could not generate persistent MAC address for vethe1fad8b: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664014]: Could not generate persistent MAC address for vetha3d53e8: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664038]: Could not generate persistent MAC address for veth2536d7c: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664039]: Could not generate persistent MAC address for veth8e32c71: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664058]: Could not generate persistent MAC address for vethe149723: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664053]: Could not generate persistent MAC address for veth7dddf71: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664049]: Could not generate persistent MAC address for vethe272ad1: No such file or directory Sep 28 22:41:03 sentry-docker00.cs.umd.edu systemd-udevd[1664057]: Could not generate persistent MAC address for veth0b65f65: No such file or directory Sep 28 23:01:11 sentry-docker00.cs.umd.edu systemd-udevd[1673587]: link_config: could not get ethtool features for vethe149723 Sep 28 23:01:11 sentry-docker00.cs.umd.edu systemd-udevd[1673587]: Could not set offload features of vethe149723: No such device Sep 28 23:01:11 sentry-docker00.cs.umd.edu systemd-udevd[1673646]: Could not generate persistent MAC address for veth9476f24: No such file or directory Sep 28 23:01:11 sentry-docker00.cs.umd.edu systemd-udevd[1673647]: Could not generate persistent MAC address for vethef1ead7: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 28 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 28 22:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 28 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 28 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 28 22:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 28 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 28 22: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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tfyg1s/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 28 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tfyg1s. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 28 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 22:25:58 submit26-b9-f1 setroubleshoot[26062]: 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 (10 distinct, 10 total) == Sep 28 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.lA0U2M/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 28 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.lA0U2M. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 28 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 22:06:52 submit26-b9-f2 setroubleshoot[3292336]: 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 Sep 28 22:13:08 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (1 distinct, 3 total) == Sep 28 22:13:38 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (1 distinct, 4 total) == Sep 28 22:13:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 28 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[30640]: Process 26223 (driver) of user 33 killed by SIGABRT - dumping core Sep 28 22:11:58 vacuum.cs.umd.edu abrt-server[30642]: Package 'amanda-backup_server' isn't signed with proper key Sep 28 22:11:58 vacuum.cs.umd.edu abrt-server[30642]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-28-22:11:58-26223' exited with 1 Sep 28 22:11:58 vacuum.cs.umd.edu abrt-server[30642]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-28-22:11:58-26223'