Command: /usr/local/sbin/syslog-digest.py Time : 0.0517s Status : exited 0 Output : Syslog digest — 2026-09-20 10:05 EDT Processed 2,410 lines, filtered 1,902 (78%). 508 unknown (194 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 09:52:11 b0b02.cs.umd.edu rustdesk[3214570]: cannot open display: == bale (5 distinct, 86 total) == Sep 20 09:05:10 bale setroubleshoot[1127318]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 20 09:05:10 bale setroubleshoot[1127318]: 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 09:05:13 bale setroubleshoot[1127318]: 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 09:05:16 bale setroubleshoot[1127318]: 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 09:05:28 bale setroubleshoot[1127935]: 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, 6 total) == Sep 20 09:36:12 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 09:36:12 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 09:36:13 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 09:36:13 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 09:36:15 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 09:36:15 biggulp.cs.umd.edu sshd-session[2780786]: error: kex_protocol_error: type 30 seq 7 [preauth] == cheezit.cs.umd.edu (6 distinct, 6 total) == Sep 20 09:41:18 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 09:41:18 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 09:41:18 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 09:41:18 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 09:41:20 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 09:41:20 cheezit.cs.umd.edu sshd-session[1198538]: error: kex_protocol_error: type 30 seq 7 [preauth] == csfw00a (1 distinct, 123 total) == Sep 20 09:03:45 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x123] == idm00 (1 distinct, 1 total) == Sep 20 09:54:00 idm00 named[4166701]: client @0x7f11a0005288 10.73.240.42#61019: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 09:37:57 idmp0 named[1598691]: client @0x7f2d50036288 10.73.240.43#49687: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 20 09:33:52 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (6 distinct, 6 total) == Sep 20 09:36:51 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 20 09:36:51 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 20 09:36:52 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 20 09:36:52 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 20 09:36:54 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 20 09:36:54 krispykreme.cs.umd.edu sshd-session[255837]: error: kex_protocol_error: type 30 seq 7 [preauth] == munin (2 distinct, 4 total) == Sep 20 09:43:13 munin sudo[737399]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 20 09:43:13 munin sudo[737399]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 20 09:13:03 newhonors2 dhcpcd[2898770]: dhcpcd is not running [x24] == ntop00 (100 distinct, 140 total) == Sep 20 09:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 34) *** Sep 20 09:05:22 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 5844/5844, ET: 21) *** Sep 20 09:05:22 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 34, QN: 51/51, ET: 21) *** Sep 20 09:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 20 09:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 5621/5621, ET: 0) *** Sep 20 09:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 35) *** Sep 20 09:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 35, QN: 40/40, ET: 0) *** Sep 20 09:08:02 ntop00 setroubleshoot[802255]: 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 [x11] Sep 20 09:08:02 ntop00 setroubleshoot[802255]: 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 [x11] Sep 20 09:08:02 ntop00 setroubleshoot[802255]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 20 09:08:02 ntop00 setroubleshoot[802255]: 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 [x11] Sep 20 09:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 20 09:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 36) *** Sep 20 09:10:21 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 5207/5207, ET: 20) *** Sep 20 09:10:21 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 36, QN: 59/59, ET: 20) *** Sep 20 09:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 20 09:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 5456/5456, ET: 0) *** Sep 20 09:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 37) *** Sep 20 09:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 37, QN: 61/61, ET: 0) *** Sep 20 09:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 20 09:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 38) *** Sep 20 09:15:22 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 5706/5706, ET: 21) *** Sep 20 09:15:22 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 38, QN: 49/49, ET: 21) *** Sep 20 09:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 20 09:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 5074/5074, ET: 0) *** Sep 20 09:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 39) *** Sep 20 09:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 39, QN: 52/52, ET: 0) *** Sep 20 09:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** Sep 20 09:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 40) *** Sep 20 09:20:19 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 40, QN: 4824/4824, ET: 18) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 09:09:09 outbound00.cs.umd.edu python3[1989842]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 09:13:06 outbound01.cs.umd.edu python3[55560]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30447]: Could not generate persistent MAC address for veth939e4d7: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30448]: Could not generate persistent MAC address for veth5eb8aca: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30451]: Could not generate persistent MAC address for veth059ea47: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30452]: Could not generate persistent MAC address for veth6fbd5ae: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30459]: Could not generate persistent MAC address for vethd4ad8de: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30468]: Could not generate persistent MAC address for veth2a3ff26: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30471]: Could not generate persistent MAC address for veth46020e5: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30459]: Could not generate persistent MAC address for vethbbb8b48: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30459]: Could not generate persistent MAC address for veth4bb2486: No such file or directory Sep 20 09:16:03 sentry-docker00.cs.umd.edu systemd-udevd[30468]: Could not generate persistent MAC address for veth1663044: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40028]: link_config: could not get ethtool features for vethd4ad8de Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40028]: Could not set offload features of vethd4ad8de: No such device Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40089]: Could not generate persistent MAC address for vetha4bf58d: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40090]: Could not generate persistent MAC address for veth400ec52: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40115]: Could not generate persistent MAC address for vethac61d9e: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40116]: Could not generate persistent MAC address for veth0dfbda2: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40141]: Could not generate persistent MAC address for vethe5e3760: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40142]: Could not generate persistent MAC address for veth30f6779: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40160]: Could not generate persistent MAC address for veth43b4930: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40146]: Could not generate persistent MAC address for veth68644ff: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40244]: Could not generate persistent MAC address for veth409ca60: No such file or directory Sep 20 09:36:11 sentry-docker00.cs.umd.edu systemd-udevd[40240]: Could not generate persistent MAC address for vetheca2bf6: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49469]: link_config: could not get ethtool features for veth43b4930 Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49469]: Could not set offload features of veth43b4930: No such device Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49499]: Could not generate persistent MAC address for veth8bc0e53: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49500]: Could not generate persistent MAC address for vethd94fdee: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49503]: Could not generate persistent MAC address for veth59f9044: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49504]: Could not generate persistent MAC address for veth8de7ee3: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49511]: Could not generate persistent MAC address for vethd83345d: No such file or directory Sep 20 09:56:19 sentry-docker00.cs.umd.edu systemd-udevd[49524]: Could not generate persistent MAC address for vethe2891e5: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 09:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 09:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 09:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 09:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 09:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f2 (1 distinct, 2 total) == Sep 20 09:10:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l a653b772-cbcd-438b-bae5-23c3dc69b31b Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 3e904634-6caa-4202-8c92-f139db798859 Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 580b20e4-ec2c-433d-905c-5bd417fba033 Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.KRhWb1/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l bff72452-d40a-430b-9060-dd0a48f5b6ba Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.KRhWb1. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 6da64b94-7024-45a9-b8c2-3b9812517407 Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l 64cbe179-abf1-4d5a-bade-bb164897ee65 Sep 20 09:06:43 submit26-b9-f3 setroubleshoot[2092845]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l d2e35b1a-e27c-4f91-9217-2bb1204e1e68 == submit26-b9-f4 (10 distinct, 13 total) == Sep 20 09:15:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] Sep 20 09:24:46 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l ee160f23-b161-4f4a-9985-c4edfd3a5beb [x2] Sep 20 09:24:46 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l 89a83821-4b24-4081-9973-0a79ca6ed5b4 [x2] Sep 20 09:24:46 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l f73955d6-1416-45f9-bab6-ff1f3ea07e9d Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.XQLR9f/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 20293136-86a3-40ba-a651-cff48d36059e Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.XQLR9f. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l eec250fb-073f-456d-93bc-f98776fd476d Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l c9209e04-a349-43d5-8cb2-3e303e48df74 Sep 20 09:24:47 submit26-b9-f4 setroubleshoot[1507609]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 3178d5f5-80e9-404b-92b7-9bef397a8915