Command: /usr/local/sbin/syslog-digest.py Time : 0.0581s Status : exited 0 Output : Syslog digest — 2026-09-18 23:05 EDT Processed 2,865 lines, filtered 2,282 (79%). 583 unknown (202 distinct) from 24 host(s). == abadi-computer (2 distinct, 2 total) == Sep 18 22:18:33 abadi-computer systemd-tmpfiles[1238541]: Opening file "/tmp/code-d3f5f468-a541-4c48-86b8-68d2e40cb325" failed, ignoring: No such device or address Sep 18 22:18:33 abadi-computer systemd-tmpfiles[1238541]: Opening file "/tmp/code-820064ef-588d-4ff0-b797-7ee04527a374" failed, ignoring: No such device or address == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 18 22:50:10 b0b02.cs.umd.edu rustdesk[2677642]: cannot open display: == bale (5 distinct, 84 total) == Sep 18 22:05:39 bale setroubleshoot[677795]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 18 22:05:40 bale setroubleshoot[677795]: SELinux is preventing /usr/libexec/platform-python3.6 from getattr access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l e098d0bd-ac29-4737-9018-de9a71e328ee [x12] Sep 18 22:05:42 bale setroubleshoot[677795]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x12] Sep 18 22:05:45 bale setroubleshoot[677795]: SELinux is preventing smartctl from open access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 2c1d6b29-3343-488c-84c7-92d46f8010b6 [x12] Sep 18 22:05:57 bale setroubleshoot[678410]: SELinux is preventing /usr/sbin/smartctl from ioctl access on the chr_file /dev/nvme0. For complete SELinux messages run: sealert -l 8ea740c2-97d8-42fb-b550-a236b114507d [x12] == csfw00a (2 distinct, 152 total) == Sep 18 22:04:03 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x146] Sep 18 22:37:04 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x6] == idm00 (1 distinct, 1 total) == Sep 18 22:53:58 idm00 named[4166701]: client @0x7f11a402f3b8 10.73.240.42#61776: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 18 22:37:58 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#58052: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (3 distinct, 21 total) == Sep 18 22:05:58 inbound00.cs.umd.edu krb5_child[1622814]: Preauthentication failed [x8] Sep 18 22:08:12 inbound00.cs.umd.edu krb5_child[1623408]: Client 'admin@UMD.EDU' not found in Kerberos database [x12] Sep 18 22:12:41 inbound00.cs.umd.edu krb5_child[1624626]: Client 'brenda@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 2 total) == Sep 18 22:08:10 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == matrix (2 distinct, 3 total) == Sep 18 23:04:44 matrix krb5_child[1893718]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 18 23:04:46 matrix sshd[1893712]: error: PAM: Authentication failure for admin from 207.175.221.71 == mcstic (3 distinct, 6 total) == Sep 18 22:25:37 mcstic krb5_child[786667]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 18 22:25:43 mcstic sshd[786662]: error: PAM: Authentication failure for admin from 34.34.148.123 Sep 18 22:31:41 mcstic sshd[786753]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 12 total) == Sep 18 22:43:38 munin sudo[4169530]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x6] Sep 18 22:43:38 munin sudo[4169530]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x6] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 18 22:57:41 newhonors.cs.umd.edu systemd-tmpfiles: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. == newhonors2 (1 distinct, 24 total) == Sep 18 22:13:02 newhonors2 dhcpcd[2832281]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 18 22:05:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 18 22:05:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 18 22:05:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 7810/7810, ET: 24) *** Sep 18 22:05:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 61/61, ET: 24) *** Sep 18 22:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 18 22:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 7683/7683, ET: 0) *** Sep 18 22:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 18 22:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 59/59, ET: 0) *** Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l ba17169a-f61e-45e0-9bfd-16245ab8d860 [x12] Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 85ad2812-105d-4895-83cc-04883c3725e4 [x12] Sep 18 22:08:02 ntop00 setroubleshoot[523323]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 18 22:08:02 ntop00 setroubleshoot[523323]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l d37d529f-f576-4d65-b493-960c1591cf89 [x12] Sep 18 22:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 18 22:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 18 22:10:24 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 7697/7697, ET: 23) *** Sep 18 22:10:24 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 60/60, ET: 23) *** Sep 18 22:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 18 22:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 7380/7380, ET: 0) *** Sep 18 22:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 18 22:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 67/67, ET: 0) *** Sep 18 22:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 18 22:15:02 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 18 22:15:23 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 7433/7433, ET: 22) *** Sep 18 22:15:23 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 66/66, ET: 21) *** Sep 18 22:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 18 22:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 61/61, ET: 0) *** Sep 18 22:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 18 22:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 7284/7284, ET: 0) *** Sep 18 22:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 18 22:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (4 distinct, 9 total) == Sep 18 22:05:21 outbound00.cs.umd.edu krb5_child[1494538]: Client 'backup@UMD.EDU' not found in Kerberos database Sep 18 22:09:09 outbound00.cs.umd.edu python3[1495464]: ldapdb [x6] Sep 18 22:11:56 outbound00.cs.umd.edu krb5_child[1496130]: Preauthentication failed Sep 18 22:21:11 outbound00.cs.umd.edu krb5_child[1498298]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 18 22:13:06 outbound01.cs.umd.edu python3[3754178]: ldapdb [x6] Sep 18 22:24:21 outbound01.cs.umd.edu krb5_child[3756490]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235619]: link_config: could not get ethtool features for veth4415fcf Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235619]: Could not set offload features of veth4415fcf: No such device Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235653]: Could not generate persistent MAC address for vethe3e0407: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235654]: Could not generate persistent MAC address for veth52d2037: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235657]: Could not generate persistent MAC address for vethe46109f: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235658]: Could not generate persistent MAC address for vethd611c1f: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235681]: Could not generate persistent MAC address for veth798d99e: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235682]: Could not generate persistent MAC address for veth7320007: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235682]: Could not generate persistent MAC address for veth12d6f69: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235689]: Could not generate persistent MAC address for vethc023c7f: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235742]: Could not generate persistent MAC address for veth6763bb4: No such file or directory Sep 18 22:21:37 sentry-docker00.cs.umd.edu systemd-udevd[3235748]: Could not generate persistent MAC address for veth9396cd1: No such file or directory Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3244969]: link_config: could not get ethtool features for vethe46109f Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3244969]: Could not set offload features of vethe46109f: No such device Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245045]: Could not generate persistent MAC address for veth290c308: No such file or directory Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245046]: Could not generate persistent MAC address for veth1fa5d3e: No such file or directory Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245071]: Could not generate persistent MAC address for vetha583529: No such file or directory Sep 18 22:41:45 sentry-docker00.cs.umd.edu systemd-udevd[3245072]: Could not generate persistent MAC address for veth18b30c6: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245101]: Could not generate persistent MAC address for vethc2204f4: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245076]: Could not generate persistent MAC address for veth313c91b: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245075]: Could not generate persistent MAC address for veth7236f39: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245091]: Could not generate persistent MAC address for veth72d18de: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245171]: Could not generate persistent MAC address for vethe2ac62f: No such file or directory Sep 18 22:41:46 sentry-docker00.cs.umd.edu systemd-udevd[3245173]: Could not generate persistent MAC address for vetha4e8aee: No such file or directory Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254380]: link_config: could not get ethtool features for vethc2204f4 Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254380]: Could not set offload features of vethc2204f4: No such device Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254493]: Could not generate persistent MAC address for vethfe09d09: No such file or directory Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254494]: Could not generate persistent MAC address for veth68da808: No such file or directory Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254503]: Could not generate persistent MAC address for veth0711688: No such file or directory Sep 18 23:01:54 sentry-docker00.cs.umd.edu systemd-udevd[3254496]: Could not generate persistent MAC address for veth26d5a38: No such file or directory ... 6 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 18 22:05:35 soul krb5_child[3391301]: Preauthentication failed == strawberry (7 distinct, 38 total) == Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 22:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 18 22:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 18 22:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 18 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (11 distinct, 15 total) == Sep 18 22:17:59 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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] Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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] Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.LvJHDh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.LvJHDh. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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] Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: 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] Sep 18 22:25:54 submit26-b9-f1 setroubleshoot[2425000]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GXZqnU. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 == submit26-b9-f2 (10 distinct, 16 total) == Sep 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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] Sep 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.q71MoX/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 [x2] Sep 18 22:06:48 submit26-b9-f2 setroubleshoot[1533678]: 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] Sep 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.q71MoX. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:06:49 submit26-b9-f2 setroubleshoot[1533678]: 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 18 22:33:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f4 (1 distinct, 2 total) == Sep 18 22:10:21 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == teaching-awards (1 distinct, 1 total) == Sep 18 23:02:05 teaching-awards sshd-session[1056971]: error: maximum authentication attempts exceeded for root from 80.180.212.218 port 54576 ssh2 [preauth] == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 18 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[15218]: Process 10780 (driver) of user 33 killed by SIGABRT - dumping core Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: Package 'amanda-backup_server' isn't signed with proper key Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-18-22:11:58-10780' exited with 1 Sep 18 22:11:59 vacuum.cs.umd.edu abrt-server[15220]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-18-22:11:58-10780'