Command: /usr/local/sbin/syslog-digest.py Time : 0.0525s Status : exited 0 Output : Syslog digest — 2026-09-19 03:05 EDT Processed 2,670 lines, filtered 2,160 (80%). 510 unknown (188 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 02:50:20 b0b02.cs.umd.edu rustdesk[2739014]: cannot open display: == bale (5 distinct, 87 total) == Sep 19 02:05:14 bale setroubleshoot[729337]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 19 02:05:15 bale setroubleshoot[729337]: 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 [x13] Sep 19 02:05:29 bale setroubleshoot[729947]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 19 02:05:29 bale setroubleshoot[729947]: 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] Sep 19 02:10:15 bale setroubleshoot[730100]: 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 [x11] == biggulp.cs.umd.edu (4 distinct, 4 total) == Sep 19 02:38:48 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 20 seq 2 [preauth] Sep 19 02:38:48 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 30 seq 3 [preauth] Sep 19 02:38:50 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 20 seq 4 [preauth] Sep 19 02:38:50 biggulp.cs.umd.edu sshd-session[2461355]: error: kex_protocol_error: type 30 seq 5 [preauth] == cheezit.cs.umd.edu (4 distinct, 4 total) == Sep 19 02:28:03 cheezit.cs.umd.edu sshd-session[760593]: pam_access(sshd:auth): access denied for user `admin' from `207.175.221.71' Sep 19 02:28:03 cheezit.cs.umd.edu krb5_child[760595]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 19 02:28:03 cheezit.cs.umd.edu sshd-session[760591]: error: PAM: System error for admin from 207.175.221.71 Sep 19 02:31:58 cheezit.cs.umd.edu sshd-session[761686]: error: Protocol major versions differ: 2 vs. 1 == cmsc436-0101-redis (2 distinct, 2 total) == Sep 19 02:30:13 cmsc436-0101-redis krb5_child[3260689]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 19 02:30:15 cmsc436-0101-redis sshd-session[3260685]: error: PAM: Authentication failure for admin from 35.187.86.229 == csfw00a (1 distinct, 126 total) == Sep 19 02:03:58 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x126] == idm00 (1 distinct, 1 total) == Sep 19 02:53:58 idm00 named[4166701]: client @0x7f11a004b338 10.73.240.42#64785: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 02:37:58 idmp0 named[1598691]: client @0x7f2d34041cc8 10.73.240.43#61568: update '73.10.in-addr.arpa/IN' denied == inbound00.cs.umd.edu (1 distinct, 1 total) == Sep 19 02:47:38 inbound00.cs.umd.edu krb5_child[1691598]: Client 'admin@UMD.EDU' not found in Kerberos database == itmon02 (1 distinct, 7 total) == Sep 19 02:23:52 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x7] == krispykreme.cs.umd.edu (3 distinct, 4 total) == Sep 19 02:07:56 krispykreme.cs.umd.edu sshd-session[3919551]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 19 02:07:57 krispykreme.cs.umd.edu sshd-session[3919551]: Error in Duo login for 'larry' from 71.191.93.172 Sep 19 02:07:57 krispykreme.cs.umd.edu sshd-session[3919549]: error: PAM: Authentication failure for larry from 71.191.93.172 == munin (2 distinct, 2 total) == Sep 19 03:03:08 munin sudo[69853]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory Sep 19 03:03:08 munin sudo[69853]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. == newhonors2 (1 distinct, 24 total) == Sep 19 02:13:03 newhonors2 dhcpcd[2839855]: dhcpcd is not running [x24] == ntop00 (98 distinct, 142 total) == Sep 19 02:05:27 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 9132/9132, ET: 26) *** Sep 19 02:05:27 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 58/58, ET: 26) *** Sep 19 02:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 19 02:08:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 70/70, ET: 0) *** Sep 19 02:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 19 02:08:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 8641/8641, ET: 0) *** Sep 19 02:08:02 ntop00 setroubleshoot[555019]: 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 19 02:08:02 ntop00 setroubleshoot[555019]: 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 19 02:08:02 ntop00 setroubleshoot[555019]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 02:08:02 ntop00 setroubleshoot[555019]: 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 19 02:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 19 02:10:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 19 02:10:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 76/76, ET: 0) *** Sep 19 02:10:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 8519/8519, ET: 24) *** Sep 19 02:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 19 02:13:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 8414/8414, ET: 0) *** Sep 19 02:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 19 02:13:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 75/75, ET: 0) *** Sep 19 02:15:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 19 02:15:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 19 02:15:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 8129/8129, ET: 24) *** Sep 19 02:15:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 67/67, ET: 24) *** Sep 19 02:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 19 02:18:01 ntop00 sfacctd[409803]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 8084/8084, ET: 0) *** Sep 19 02:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 19 02:18:01 ntop00 nfacctd[409883]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 58/58, ET: 0) *** Sep 19 02:20:01 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 19 02:20:01 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 19 02:20:25 ntop00 sfacctd[409803]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 8138/8138, ET: 24) *** Sep 19 02:20:25 ntop00 nfacctd[409883]: INFO ( m1/mysql ): *** Purging cache - END (PID: 448, QN: 52/52, ET: 24) *** ... 68 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 02:09:09 outbound00.cs.umd.edu python3[1553955]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 02:13:06 outbound01.cs.umd.edu python3[3812324]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348884]: link_config: could not get ethtool features for veth347fdab Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348884]: Could not set offload features of veth347fdab: No such device Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348921]: Could not generate persistent MAC address for veth755eca7: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348922]: Could not generate persistent MAC address for vethd61fd3a: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348926]: Could not generate persistent MAC address for veth5446cd2: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348925]: Could not generate persistent MAC address for vetheb2462e: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348930]: Could not generate persistent MAC address for veth6e5a698: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348933]: Could not generate persistent MAC address for veth5fa3319: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348951]: Could not generate persistent MAC address for veth80716b9: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348952]: Could not generate persistent MAC address for veth9fe78cb: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348977]: Could not generate persistent MAC address for vethb446c28: No such file or directory Sep 19 02:23:17 sentry-docker00.cs.umd.edu systemd-udevd[3348989]: Could not generate persistent MAC address for vethe453c06: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358688]: link_config: could not get ethtool features for veth755eca7 Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358688]: Could not set offload features of veth755eca7: No such device Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358721]: Could not generate persistent MAC address for veth6e99b32: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358722]: Could not generate persistent MAC address for veth78277ab: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358725]: Could not generate persistent MAC address for veth7e10ebd: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358726]: Could not generate persistent MAC address for vetha6c27ae: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for vethf24e852: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for veth6e17f0f: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for veth7ed5c30: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for veth25f98d7: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358741]: Could not generate persistent MAC address for vethfd370ab: No such file or directory Sep 19 02:43:25 sentry-docker00.cs.umd.edu systemd-udevd[3358727]: Could not generate persistent MAC address for veth7d26920: No such file or directory Sep 19 03:03:33 sentry-docker00.cs.umd.edu systemd-udevd[3368184]: link_config: could not get ethtool features for vethfd370ab Sep 19 03:03:33 sentry-docker00.cs.umd.edu systemd-udevd[3368184]: Could not set offload features of vethfd370ab: No such device Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368235]: Could not generate persistent MAC address for vethdff059c: No such file or directory Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368236]: Could not generate persistent MAC address for veth4ceb219: No such file or directory Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368246]: Could not generate persistent MAC address for vethd417f9a: No such file or directory Sep 19 03:03:34 sentry-docker00.cs.umd.edu systemd-udevd[3368247]: Could not generate persistent MAC address for vethc7bfc8f: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 02: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 02: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 02:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (9 distinct, 9 total) == Sep 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NxgO88/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NxgO88. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 19 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 02:25:53 submit26-b9-f1 setroubleshoot[2463817]: 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 (9 distinct, 9 total) == Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.amKiSy/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.amKiSy. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 19 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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 02:06:48 submit26-b9-f2 setroubleshoot[1580643]: 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