Command: /usr/local/sbin/syslog-digest.py Time : 0.0549s Status : exited 0 Output : Syslog digest — 2026-09-19 22:05 EDT Processed 2,974 lines, filtered 2,429 (81%). 545 unknown (202 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 21:51:27 b0b02.cs.umd.edu rustdesk[3029867]: cannot open display: == bale (5 distinct, 88 total) == Sep 19 21:05:09 bale setroubleshoot[972665]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 19 21:05:10 bale setroubleshoot[972665]: 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 21:05:13 bale setroubleshoot[972665]: 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 21:05:16 bale setroubleshoot[972665]: 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 21:05:27 bale setroubleshoot[973281]: 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 (5 distinct, 5 total) == Sep 19 21:18:12 biggulp.cs.umd.edu sshd-session[2653247]: error: send_error: write: Connection reset by peer Sep 19 21:58:48 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 19 21:58:48 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 19 21:58:50 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 19 21:58:50 biggulp.cs.umd.edu sshd-session[2660542]: error: kex_protocol_error: type 30 seq 5 [preauth] == csfw00a (1 distinct, 138 total) == Sep 19 21:04:02 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x138] == idm00 (1 distinct, 1 total) == Sep 19 21:53:59 idm00 named[4166701]: client @0x7f11986d48e8 10.73.240.42#63046: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 21:37:57 idmp0 named[1598691]: client @0x7f2d4c039bf8 10.73.240.43#60244: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 19 21:07:58 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5] == krispykreme.cs.umd.edu (4 distinct, 4 total) == Sep 19 21:59:19 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 19 21:59:19 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 19 21:59:21 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 19 21:59:21 krispykreme.cs.umd.edu sshd-session[64575]: error: kex_protocol_error: type 30 seq 5 [preauth] == munin (2 distinct, 4 total) == Sep 19 21:57:57 munin sudo[480728]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 19 21:57:57 munin sudo[480728]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == netman.cs.umd.edu (2 distinct, 2 total) == Sep 19 21:58:48 netman.cs.umd.edu sshd[2556612]: error: type 20 seq 2 [preauth] Sep 19 21:58:48 netman.cs.umd.edu sshd[2556612]: error: type 30 seq 3 [preauth] == newhonors2 (1 distinct, 24 total) == Sep 19 21:13:03 newhonors2 dhcpcd[2875673]: dhcpcd is not running [x24] == ntop00 (99 distinct, 143 total) == Sep 19 21:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 19 21:05:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 6250/6250, ET: 22) *** Sep 19 21:05:24 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 43/43, ET: 23) *** Sep 19 21:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 19 21:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6476/6476, ET: 0) *** Sep 19 21:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 19 21:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 42/42, ET: 0) *** Sep 19 21:08:02 ntop00 setroubleshoot[706258]: 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 21:08:02 ntop00 setroubleshoot[706258]: 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 21:08:03 ntop00 setroubleshoot[706258]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 21:08:03 ntop00 setroubleshoot[706258]: 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 21:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 19 21:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 19 21:10:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 6655/6655, ET: 25) *** Sep 19 21:10:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 48/48, ET: 25) *** Sep 19 21:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 19 21:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6777/6777, ET: 0) *** Sep 19 21:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 19 21:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 46/46, ET: 0) *** Sep 19 21:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 19 21:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 19 21:15:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6648/6648, ET: 25) *** Sep 19 21:15:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 53/53, ET: 25) *** Sep 19 21:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 19 21:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 6248/6248, ET: 0) *** Sep 19 21:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 19 21:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 55/55, ET: 0) *** Sep 19 21:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 19 21:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 19 21:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 328, QN: 51/51, ET: 0) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (7 distinct, 12 total) == Sep 19 21:09:09 outbound00.cs.umd.edu python3[1820447]: ldapdb [x6] Sep 19 21:49:53 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 19 21:49:53 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 19 21:49:54 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 19 21:49:54 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 19 21:49:57 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 19 21:49:57 outbound00.cs.umd.edu sshd-session[1829556]: error: kex_protocol_error: type 30 seq 7 [preauth] == outbound01.cs.umd.edu (7 distinct, 12 total) == Sep 19 21:13:06 outbound01.cs.umd.edu python3[4079481]: ldapdb [x6] Sep 19 21:49:52 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 19 21:49:52 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 19 21:49:54 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 19 21:49:54 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 5 [preauth] Sep 19 21:49:56 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 20 seq 6 [preauth] Sep 19 21:49:56 outbound01.cs.umd.edu sshd-session[4087872]: error: kex_protocol_error: type 30 seq 7 [preauth] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881214]: link_config: could not get ethtool features for vethcc8dbd5 Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881214]: Could not set offload features of vethcc8dbd5: No such device Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881249]: Could not generate persistent MAC address for vethadbd008: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881250]: Could not generate persistent MAC address for vethaabb594: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881259]: Could not generate persistent MAC address for veth036eaea: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881269]: Could not generate persistent MAC address for veth6ba88ff: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881273]: Could not generate persistent MAC address for veth3d05ec9: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881268]: Could not generate persistent MAC address for veth983b7e7: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881271]: Could not generate persistent MAC address for vethbb4cb0b: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881268]: Could not generate persistent MAC address for vethb2e77aa: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881349]: Could not generate persistent MAC address for veth655c4ff: No such file or directory Sep 19 21:11:03 sentry-docker00.cs.umd.edu systemd-udevd[3881353]: Could not generate persistent MAC address for veth0cf726f: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890624]: link_config: could not get ethtool features for vethb2e77aa Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890624]: Could not set offload features of vethb2e77aa: No such device Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890658]: Could not generate persistent MAC address for vethbb8f393: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890659]: Could not generate persistent MAC address for veth26af7b4: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890662]: Could not generate persistent MAC address for vethce13964: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890663]: Could not generate persistent MAC address for veth403c27c: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890679]: Could not generate persistent MAC address for vethf49e63c: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890669]: Could not generate persistent MAC address for veth905ef90: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890689]: Could not generate persistent MAC address for veth1d25d40: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890688]: Could not generate persistent MAC address for vethfe3531e: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890693]: Could not generate persistent MAC address for veth212d9de: No such file or directory Sep 19 21:31:11 sentry-docker00.cs.umd.edu systemd-udevd[3890688]: Could not generate persistent MAC address for vethd74e3dc: No such file or directory Sep 19 21:51:19 sentry-docker00.cs.umd.edu systemd-udevd[3900239]: link_config: could not get ethtool features for vethd74e3dc Sep 19 21:51:19 sentry-docker00.cs.umd.edu systemd-udevd[3900239]: Could not set offload features of vethd74e3dc: No such device Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900282]: Could not generate persistent MAC address for veth76ae185: No such file or directory Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900283]: Could not generate persistent MAC address for veth8f198a4: No such file or directory Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900286]: Could not generate persistent MAC address for vethc9ec482: No such file or directory Sep 19 21:51:20 sentry-docker00.cs.umd.edu systemd-udevd[3900287]: Could not generate persistent MAC address for veth149a0fc: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 21:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 21:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 19 22:03:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (1 distinct, 5 total) == Sep 19 21:09:51 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (10 distinct, 14 total) == Sep 19 21:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 19 21:06:42 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:42 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.TD96o9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.TD96o9. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: 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 19 21:06:43 submit26-b9-f3 setroubleshoot[2043991]: 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, 11 total) == Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Vwtm2x/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Vwtm2x. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 19 21:24:46 submit26-b9-f4 setroubleshoot[1467279]: 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 Sep 19 21:25:09 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2]