Command: /usr/local/sbin/syslog-digest.py Time : 0.0512s Status : exited 0 Output : Syslog digest — 2026-09-20 23:05 EDT Processed 2,088 lines, filtered 1,530 (73%). 558 unknown (193 distinct) from 22 host(s). == atif01.cs.umd.edu (2 distinct, 2 total) == Sep 20 22:13:29 atif01.cs.umd.edu kernel: net_ratelimit: 6 callbacks suppressed Sep 20 22:40:29 atif01.cs.umd.edu kernel: nfsd: peername failed (err 107)! == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 22:53:00 b0b02.cs.umd.edu rustdesk[3412508]: cannot open display: == bale (5 distinct, 88 total) == Sep 20 22:05:31 bale setroubleshoot[1293442]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 20 22:05:31 bale setroubleshoot[1293442]: 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 20 22:05:34 bale setroubleshoot[1293442]: 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 20 22:05:37 bale setroubleshoot[1293442]: 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 20 22:05:49 bale setroubleshoot[1294080]: 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 [x14] == biggulp.cs.umd.edu (2 distinct, 2 total) == Sep 20 22:51:29 biggulp.cs.umd.edu sshd-session[2916301]: pam_access(sshd:auth): access denied for user `operator' from `193.187.110.214' Sep 20 22:51:31 biggulp.cs.umd.edu sshd-session[2916295]: error: PAM: Authentication failure for operator from 193.187.110.214 == cmsc436-0101-redis (3 distinct, 3 total) == Sep 20 22:10:08 cmsc436-0101-redis sshd-session[3357493]: error: PAM: Authentication failure for root from 193.187.110.214 Sep 20 22:34:15 cmsc436-0101-redis krb5_child[3358346]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 20 22:34:17 cmsc436-0101-redis sshd-session[3358342]: error: PAM: Authentication failure for admin from 34.156.126.241 == csfw00a (2 distinct, 140 total) == Sep 20 22:03:49 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x138] Sep 20 22:54:21 csfw00a ospf6d[1477]: [EC 100663307] Could not send entire message [x2] == idm00 (1 distinct, 1 total) == Sep 20 22:54:01 idm00 named[4166701]: client @0x7f11986ceb28 10.73.240.42#53770: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 22:37:56 idmp0 named[1598691]: client @0x7f2d3002f808 10.73.240.43#49191: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 20 22:08:07 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == munin (2 distinct, 28 total) == Sep 20 22:43:33 munin sudo[1019808]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x14] Sep 20 22:43:33 munin sudo[1019808]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x14] == newhonors.cs.umd.edu (1 distinct, 1 total) == Sep 20 22:59: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 20 22:13:03 newhonors2 dhcpcd[2922976]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 20 22:05:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 6458/6458, ET: 27) *** Sep 20 22:05:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 346, QN: 56/56, ET: 27) *** Sep 20 22:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 20 22:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 5966/5966, ET: 0) *** Sep 20 22:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 347) *** Sep 20 22:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 347, QN: 61/61, ET: 0) *** Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12] Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12] Sep 20 22:08:02 ntop00 setroubleshoot[905324]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 20 22:08:02 ntop00 setroubleshoot[905324]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12] Sep 20 22:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 20 22:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 348) *** Sep 20 22:10:25 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 5864/5864, ET: 24) *** Sep 20 22:10:26 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 348, QN: 60/60, ET: 25) *** Sep 20 22:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 20 22:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 6461/6461, ET: 0) *** Sep 20 22:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 349) *** Sep 20 22:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 349, QN: 69/69, ET: 0) *** Sep 20 22:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 20 22:15:02 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 350) *** Sep 20 22:15:28 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 6625/6625, ET: 27) *** Sep 20 22:15:28 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 350, QN: 68/68, ET: 26) *** Sep 20 22:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 20 22:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 6410/6410, ET: 0) *** Sep 20 22:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 351) *** Sep 20 22:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 351, QN: 84/84, ET: 0) *** Sep 20 22:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 20 22:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 352) *** Sep 20 22:20:27 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 6172/6172, ET: 26) *** Sep 20 22:20:27 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 352, QN: 77/77, ET: 26) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 22:09:09 outbound00.cs.umd.edu python3[2173321]: ldapdb [x6] == outbound01.cs.umd.edu (3 distinct, 8 total) == Sep 20 22:13:07 outbound01.cs.umd.edu python3[239672]: ldapdb [x6] Sep 20 22:13:30 outbound01.cs.umd.edu krb5_child[239844]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 20 22:20:30 outbound01.cs.umd.edu sshd-session[240980]: error: Protocol major versions differ: 2 vs. 1 == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[399967]: link_config: could not get ethtool features for vethce0bb98 Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[399967]: Could not set offload features of vethce0bb98: No such device Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400002]: Could not generate persistent MAC address for veth85f034d: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400003]: Could not generate persistent MAC address for vethb3a3e11: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400006]: Could not generate persistent MAC address for vethbe17271: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400007]: Could not generate persistent MAC address for veth11b2042: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400011]: Could not generate persistent MAC address for vetha2e2eb4: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400019]: Could not generate persistent MAC address for veth8ba3604: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400019]: Could not generate persistent MAC address for veth224563b: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400011]: Could not generate persistent MAC address for veth310e414: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400014]: Could not generate persistent MAC address for veth2381731: No such file or directory Sep 20 22:21:27 sentry-docker00.cs.umd.edu systemd-udevd[400013]: Could not generate persistent MAC address for veth1d9d829: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409464]: Could not generate persistent MAC address for vetha18ac36: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409465]: Could not generate persistent MAC address for veth605402f: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409468]: Could not generate persistent MAC address for veth41eb912: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409469]: Could not generate persistent MAC address for vethe149c0f: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409484]: Could not generate persistent MAC address for veth7e5c7dc: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409471]: Could not generate persistent MAC address for veth2e54722: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409494]: Could not generate persistent MAC address for veth763e633: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409495]: Could not generate persistent MAC address for veth52b4004: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409511]: Could not generate persistent MAC address for vethd997755: No such file or directory Sep 20 22:41:36 sentry-docker00.cs.umd.edu systemd-udevd[409517]: Could not generate persistent MAC address for veth44f7944: No such file or directory Sep 20 23:01:43 sentry-docker00.cs.umd.edu systemd-udevd[418861]: link_config: could not get ethtool features for veth763e633 Sep 20 23:01:43 sentry-docker00.cs.umd.edu systemd-udevd[418861]: Could not set offload features of veth763e633: No such device Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418895]: Could not generate persistent MAC address for vethf86a822: No such file or directory Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418896]: Could not generate persistent MAC address for veth73dff1a: No such file or directory Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418899]: Could not generate persistent MAC address for veth902b1c2: No such file or directory Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418900]: Could not generate persistent MAC address for veth4879303: No such file or directory Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418923]: Could not generate persistent MAC address for veth76b01be: No such file or directory Sep 20 23:01:44 sentry-docker00.cs.umd.edu systemd-udevd[418924]: Could not generate persistent MAC address for vethad4f364: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 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 20 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 20 22:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 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 20 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 20 22:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 22:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (10 distinct, 14 total) == Sep 20 22:10:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.h0ESKV/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.h0ESKV. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:25:54 submit26-b9-f1 setroubleshoot[2649468]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.CcGYzx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.CcGYzx. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:06:49 submit26-b9-f2 setroubleshoot[1759123]: 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 20 22:15:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f3 (1 distinct, 3 total) == Sep 20 22:15:04 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == teaching-awards (2 distinct, 2 total) == Sep 20 22:23:35 teaching-awards krb5_child[1202557]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 20 22:30:20 teaching-awards sshd-session[1203046]: error: Protocol major versions differ: 2 vs. 1 == vacuum.cs.umd.edu (4 distinct, 4 total) == Sep 20 22:12:00 vacuum.cs.umd.edu abrt-hook-ccpp[24837]: Process 20422 (driver) of user 33 killed by SIGABRT - dumping core Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: Package 'amanda-backup_server' isn't signed with proper key Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: 'post-create' on '/var/spool/abrt/ccpp-2026-09-20-22:12:00-20422' exited with 1 Sep 20 22:12:00 vacuum.cs.umd.edu abrt-server[24838]: Deleting problem directory '/var/spool/abrt/ccpp-2026-09-20-22:12:00-20422'
participants (1)
-
cron/syslog01.cs.umd.edu