Command: /usr/local/sbin/syslog-digest.py Time : 0.0527s Status : exited 0 Output : Syslog digest — 2026-09-19 23:05 EDT Processed 2,618 lines, filtered 2,084 (79%). 534 unknown (199 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 22:51:31 b0b02.cs.umd.edu rustdesk[3045031]: cannot open display: == bale (5 distinct, 86 total) == Sep 19 22:05:09 bale setroubleshoot[985556]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 19 22:05:10 bale setroubleshoot[985556]: 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 19 22:05:13 bale setroubleshoot[985556]: 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 19 22:05:16 bale setroubleshoot[985556]: 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 19 22:05:27 bale setroubleshoot[986172]: 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 [x13] == biggulp.cs.umd.edu (6 distinct, 7 total) == Sep 19 22:08:01 biggulp.cs.umd.edu sshd-session[2661875]: pam_access(sshd:auth): access denied for user `admin' from `34.78.143.65' Sep 19 22:08:03 biggulp.cs.umd.edu krb5_child[2661890]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 19 22:08:03 biggulp.cs.umd.edu sshd-session[2661872]: error: PAM: System error for admin from 34.78.143.65 Sep 19 22:08:35 biggulp.cs.umd.edu sshd-session[2661915]: pam_access(sshd:auth): access denied for user `admin' from `146.148.113.204' Sep 19 22:08:37 biggulp.cs.umd.edu sshd-session[2661907]: error: PAM: System error for admin from 146.148.113.204 Sep 19 22:09:29 biggulp.cs.umd.edu sshd-session[2661979]: error: Protocol major versions differ: 2 vs. 1 == csfw00a (1 distinct, 133 total) == Sep 19 22:04:22 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133] == idm00 (1 distinct, 1 total) == Sep 19 22:53:59 idm00 named[4166701]: client @0x7f1198074538 10.73.240.42#56959: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 22:37:57 idmp0 named[1598691]: client @0x7f2d20030738 10.73.240.43#60129: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 19 22:23:05 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 2 total) == Sep 19 23:03:41 munin sudo[504453]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 19 23:03:41 munin sudo[504453]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == netman.cs.umd.edu (3 distinct, 6 total) == Sep 19 22:05:37 netman.cs.umd.edu krb5_child[2558877]: Client 'admin@UMD.EDU' not found in Kerberos database [x4] Sep 19 22:05:44 netman.cs.umd.edu sshd[2558872]: error: PAM: Authentication failure for admin from 34.79.116.107 Sep 19 22:10:40 netman.cs.umd.edu sshd[2559669]: error: Protocol major versions differ: 2 vs. 1 == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 19 22:58: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 19 22:13:03 newhonors2 dhcpcd[2877515]: dhcpcd is not running [x24] == ntop00 (101 distinct, 145 total) == Sep 19 22:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 19 22:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 346) *** Sep 19 22:05:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 6048/6048, ET: 23) *** Sep 19 22:05:24 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 59/59, ET: 23) *** Sep 19 22:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 19 22:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5963/5963, ET: 0) *** Sep 19 22:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 19 22:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 62/62, ET: 0) *** Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 977904f2-b1d5-479f-af5f-8f979ecc6b5a [x12] Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 7ff4701c-77ae-4c43-938b-2b711cad9847 [x12] Sep 19 22:08:02 ntop00 setroubleshoot[714301]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 22:08:02 ntop00 setroubleshoot[714301]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l c2ce2f7a-3ea8-46d2-8a8a-6e46548752ef [x12] Sep 19 22:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 19 22:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 19 22:10:22 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5895/5895, ET: 21) *** Sep 19 22:10:22 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 67/67, ET: 21) *** Sep 19 22:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 19 22:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 5694/5694, ET: 0) *** Sep 19 22:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 19 22:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 61/61, ET: 0) *** Sep 19 22:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 19 22:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 19 22:15:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 5433/5433, ET: 19) *** Sep 19 22:15:20 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 66/66, ET: 19) *** Sep 19 22:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 19 22:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 5440/5440, ET: 0) *** Sep 19 22:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 19 22:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 59/59, ET: 1) *** Sep 19 22:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 19 22:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 22:09:09 outbound00.cs.umd.edu python3[1834392]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 9 total) == Sep 19 22:13:06 outbound01.cs.umd.edu python3[4093644]: ldapdb [x6] Sep 19 22:53:09 outbound01.cs.umd.edu krb5_child[4102714]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 19 22:55:08 outbound01.cs.umd.edu krb5_child[4103049]: Preauthentication failed == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909654]: link_config: could not get ethtool features for veth76ae185 Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909654]: Could not set offload features of veth76ae185: No such device Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909749]: link_config: could not get ethtool features for vethdadc635 Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909749]: Could not set offload features of vethdadc635: No such device Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909770]: Could not generate persistent MAC address for vethc982304: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909771]: Could not generate persistent MAC address for vetha95abd2: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909774]: Could not generate persistent MAC address for vethfcf2ace: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909775]: Could not generate persistent MAC address for veth8f1046c: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909830]: Could not generate persistent MAC address for veth09195c5: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909831]: Could not generate persistent MAC address for vetha344954: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909869]: Could not generate persistent MAC address for veth68a1f3a: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909875]: Could not generate persistent MAC address for veth718697f: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909895]: Could not generate persistent MAC address for veth630a736: No such file or directory Sep 19 22:11:28 sentry-docker00.cs.umd.edu systemd-udevd[3909887]: Could not generate persistent MAC address for vethd65d293: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919146]: link_config: could not get ethtool features for veth09195c5 Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919146]: Could not set offload features of veth09195c5: No such device Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919182]: Could not generate persistent MAC address for vethe103e49: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919183]: Could not generate persistent MAC address for veth6e1f8e2: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919186]: Could not generate persistent MAC address for vethd19e050: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for vethb3e1c9d: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for veth9e0d5c1: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919196]: Could not generate persistent MAC address for veth4a70f7d: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919196]: Could not generate persistent MAC address for veth31bde4a: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919187]: Could not generate persistent MAC address for veth3614537: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919214]: Could not generate persistent MAC address for vethdedf544: No such file or directory Sep 19 22:31:36 sentry-docker00.cs.umd.edu systemd-udevd[3919215]: Could not generate persistent MAC address for vethb89bc6e: No such file or directory Sep 19 22:51:44 sentry-docker00.cs.umd.edu systemd-udevd[3928528]: link_config: could not get ethtool features for veth3614537 Sep 19 22:51:44 sentry-docker00.cs.umd.edu systemd-udevd[3928528]: Could not set offload features of veth3614537: No such device Sep 19 22:51:45 sentry-docker00.cs.umd.edu systemd-udevd[3928595]: Could not generate persistent MAC address for veth15dc03e: No such file or directory Sep 19 22:51:45 sentry-docker00.cs.umd.edu systemd-udevd[3928596]: Could not generate persistent MAC address for veth9c13283: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 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 19 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 19 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 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 19 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 19 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 13 total) == Sep 19 22:08:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] Sep 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:53 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.JFZGWw/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.JFZGWw. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: 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 19 22:25:54 submit26-b9-f1 setroubleshoot[2545739]: 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, 12 total) == Sep 19 22:05:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2zz6WM/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2zz6WM. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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 19 22:06:49 submit26-b9-f2 setroubleshoot[1655828]: 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-f3 (1 distinct, 2 total) == Sep 19 22:26:27 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f4 (1 distinct, 2 total) == Sep 19 22:08:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 19 22:11:58 vacuum.cs.umd.edu abrt-hook-ccpp[3949]: Process 31785 (driver) of user 33 killed by SIGABRT - dumping core Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: Package 'amanda-backup_server' isn't signed with proper key Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-19-22:11:58-31785' exited with 1 Sep 19 22:11:58 vacuum.cs.umd.edu abrt-server[3951]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-19-22:11:58-31785'