Command: /usr/local/sbin/syslog-digest.py Time : 0.0490s Status : exited 0 Output : Syslog digest — 2026-09-23 03:05 EDT Processed 2,157 lines, filtered 1,749 (81%). 408 unknown (188 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 23 02:56:21 b0b02.cs.umd.edu rustdesk[82042]: cannot open display: == bale (5 distinct, 88 total) == Sep 23 02:05:48 bale setroubleshoot[1988665]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 23 02:05:49 bale setroubleshoot[1988665]: 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 23 02:05:51 bale setroubleshoot[1988665]: 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 23 02:05:54 bale setroubleshoot[1988665]: 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 23 02:06:06 bale setroubleshoot[1989281]: 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 (3 distinct, 4 total) == Sep 23 02:26:24 biggulp.cs.umd.edu sshd-session[3536884]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' [x2] Sep 23 02:26:32 biggulp.cs.umd.edu krb5_child[3536890]: Preauthentication failed Sep 23 02:26:32 biggulp.cs.umd.edu sshd-session[3536882]: error: PAM: Authentication failure for lin from 74.96.151.253 == galax (2 distinct, 7 total) == Sep 23 02:10:05 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x6] Sep 23 02:53:54 galax systemd[1]: motd-news.service: Main process exited, code=dumped, status=11/SEGV == idm00 (1 distinct, 1 total) == Sep 23 02:54:26 idm00 named[4166701]: client @0x7f11a006da58 10.73.240.42#60409: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 23 02:37:54 idmp0 named[1598691]: client @0x7f2d500408e8 10.73.240.43#63052: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 23 02:13:02 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == matrix (2 distinct, 3 total) == Sep 23 02:29:17 matrix krb5_child[1144466]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 23 02:29:18 matrix sshd[1144440]: error: PAM: Authentication failure for admin from 34.53.192.72 == munin (2 distinct, 20 total) == Sep 23 02:23:34 munin sudo[2142864]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10] Sep 23 02:23:34 munin sudo[2142864]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10] == newhonors2 (1 distinct, 24 total) == Sep 23 02:13:03 newhonors2 dhcpcd[3022002]: dhcpcd is not running [x24] == ntop00 (101 distinct, 145 total) == Sep 23 02:05:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 23 02:05:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 442) *** Sep 23 02:05:27 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 4802/4802, ET: 26) *** Sep 23 02:05:27 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 442, QN: 42/42, ET: 26) *** Sep 23 02:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 23 02:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 4534/4534, ET: 0) *** Sep 23 02:08:02 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 443) *** Sep 23 02:08:02 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 443, QN: 38/38, ET: 0) *** Sep 23 02:08:02 ntop00 setroubleshoot[1319284]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l af369431-37df-4ac9-9292-5066d38787e5 [x12] Sep 23 02:08:02 ntop00 setroubleshoot[1319284]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 244a2465-7b27-44c9-bda6-9cd4f2dd6cbc [x12] Sep 23 02:08:02 ntop00 setroubleshoot[1319284]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 23 02:08:02 ntop00 setroubleshoot[1319284]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l ba3a59c0-2cfe-4a84-9a21-86479d1517da [x12] Sep 23 02:10:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 23 02:10:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 444) *** Sep 23 02:10:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 46/46, ET: 0) *** Sep 23 02:10:26 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 444, QN: 4451/4451, ET: 25) *** Sep 23 02:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 23 02:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 49/49, ET: 0) *** Sep 23 02:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 445) *** Sep 23 02:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 445, QN: 4581/4581, ET: 0) *** Sep 23 02:15:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 23 02:15:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 446) *** Sep 23 02:15:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 53/53, ET: 0) *** Sep 23 02:15:26 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 446, QN: 4639/4639, ET: 25) *** Sep 23 02:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 23 02:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 4547/4547, ET: 0) *** Sep 23 02:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 447) *** Sep 23 02:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 447, QN: 60/60, ET: 0) *** Sep 23 02:20:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** Sep 23 02:20:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 448) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (2 distinct, 7 total) == Sep 23 02:09:09 outbound00.cs.umd.edu python3[2912383]: ldapdb [x6] Sep 23 02:57:28 outbound00.cs.umd.edu krb5_child[2923895]: Client 'admin@UMD.EDU' not found in Kerberos database == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 23 02:13:06 outbound01.cs.umd.edu python3[1005847]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 23 02:22:56 sentry-docker00.cs.umd.edu systemd-udevd[1888983]: link_config: could not get ethtool features for vethce6aec9 Sep 23 02:22:56 sentry-docker00.cs.umd.edu systemd-udevd[1888983]: Could not set offload features of vethce6aec9: No such device Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889016]: Could not generate persistent MAC address for vethc26ebbb: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889017]: Could not generate persistent MAC address for vethc5ca03a: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889020]: Could not generate persistent MAC address for veth97d347d: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889021]: Could not generate persistent MAC address for veth2372930: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889038]: Could not generate persistent MAC address for veth98af0d3: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889026]: Could not generate persistent MAC address for vetha0c0f97: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889030]: Could not generate persistent MAC address for veth32810fb: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889020]: Could not generate persistent MAC address for veth76d55ea: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889050]: Could not generate persistent MAC address for vetha05922b: No such file or directory Sep 23 02:22:57 sentry-docker00.cs.umd.edu systemd-udevd[1889052]: Could not generate persistent MAC address for veth58c497f: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898657]: link_config: could not get ethtool features for veth97d347d Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898657]: Could not set offload features of veth97d347d: No such device Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898746]: link_config: could not get ethtool features for vethc26ebbb Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898746]: Could not set offload features of vethc26ebbb: No such device Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898787]: Could not generate persistent MAC address for vethcca3928: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898786]: Could not generate persistent MAC address for vethe849a11: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898790]: Could not generate persistent MAC address for veth0360f79: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898807]: Could not generate persistent MAC address for vethf76f903: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898804]: Could not generate persistent MAC address for veth85c02d8: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898798]: Could not generate persistent MAC address for veth2a46ea4: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898791]: Could not generate persistent MAC address for vetha5640b6: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898804]: Could not generate persistent MAC address for veth15c9e56: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898818]: Could not generate persistent MAC address for vethb39be52: No such file or directory Sep 23 02:43:05 sentry-docker00.cs.umd.edu systemd-udevd[1898820]: Could not generate persistent MAC address for veth8ccb43a: No such file or directory Sep 23 03:03:13 sentry-docker00.cs.umd.edu systemd-udevd[1908301]: Could not generate persistent MAC address for veth50a7d8d: No such file or directory Sep 23 03:03:13 sentry-docker00.cs.umd.edu systemd-udevd[1908300]: Could not generate persistent MAC address for vethb990cd9: No such file or directory Sep 23 03:03:13 sentry-docker00.cs.umd.edu systemd-udevd[1908324]: Could not generate persistent MAC address for veth7303f9c: No such file or directory Sep 23 03:03:13 sentry-docker00.cs.umd.edu systemd-udevd[1908319]: Could not generate persistent MAC address for vethbeb0d85: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 23 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 02:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 02:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 23 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 23 02:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 23 02:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 23 02:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (11 distinct, 14 total) == Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 [x2] Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Hdbxrq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 [x2] Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Hdbxrq. For complete SELinux messages run: sealert -l 0d661d88-dc9e-469d-986b-52e29b353aa8 Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 [x2] Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: 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 Sep 23 02:25:55 submit26-b9-f1 setroubleshoot[3044583]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.orZtSN/repodata/repomd.xml. For complete SELinux messages run: sealert -l 3b0d8c9a-6637-4d6e-a864-f1dd7c00377d Sep 23 02:43:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f2 (9 distinct, 9 total) == Sep 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.G0mFA7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 7f4c3a8e-0f99-47c4-9baf-e1336fe24876 Sep 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.G0mFA7. For complete SELinux messages run: sealert -l ca585e2b-d50f-4264-8127-6b3fa04070c8 Sep 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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 23 02:06:50 submit26-b9-f2 setroubleshoot[2156587]: 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, 1 total) == Sep 23 02:23:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == tma-0 (1 distinct, 1 total) == Sep 23 02:46:13 tma-0 sshd[28013]: fatal: ssh_packet_get_string: incomplete message [preauth]