Command: /usr/local/sbin/syslog-digest.py Time : 0.0535s Status : exited 0 Output : Syslog digest — 2026-09-20 02:05 EDT Processed 2,716 lines, filtered 2,199 (80%). 517 unknown (190 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 01:51:42 b0b02.cs.umd.edu rustdesk[3091615]: cannot open display: == bale (5 distinct, 86 total) == Sep 20 01:05:22 bale setroubleshoot[1024266]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 20 01:05:22 bale setroubleshoot[1024266]: 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 01:05:25 bale setroubleshoot[1024266]: 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 01:05:28 bale setroubleshoot[1024266]: 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 01:05:40 bale setroubleshoot[1024895]: 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] == cheezit.cs.umd.edu (3 distinct, 8 total) == Sep 20 01:27:14 cheezit.cs.umd.edu sshd-session[1083975]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x4] Sep 20 01:27:15 cheezit.cs.umd.edu sshd-session[1083975]: Error in Duo login for 'larry' from 71.191.93.172 [x2] Sep 20 01:27:15 cheezit.cs.umd.edu sshd-session[1083973]: error: PAM: Authentication failure for larry from 71.191.93.172 [x2] == cmsc436-0101-redis (3 distinct, 3 total) == Sep 20 01:15:54 cmsc436-0101-redis krb5_child[3310880]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 20 01:15:55 cmsc436-0101-redis sshd-session[3310876]: error: PAM: Authentication failure for admin from 34.14.2.117 Sep 20 01:19:40 cmsc436-0101-redis sshd-session[3310928]: error: Protocol major versions differ: 2 vs. 1 == csfw00a (1 distinct, 122 total) == Sep 20 01:04:19 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x122] == idm00 (1 distinct, 1 total) == Sep 20 01:53:59 idm00 named[4166701]: client @0x7f11a8045438 10.73.240.42#51806: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 01:37:57 idmp0 named[1598691]: client @0x7f2d4c005288 10.73.240.43#49346: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 20 01:33:30 itmon02 sshd[1750555]: error: beginning MaxStartups throttling == matrix (3 distinct, 4 total) == Sep 20 01:22:38 matrix krb5_child[2806538]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] Sep 20 01:22:40 matrix sshd[2806532]: error: PAM: Authentication failure for admin from 207.175.45.86 Sep 20 01:22:54 matrix sshd[2806656]: error: Protocol major versions differ: 2 vs. 1 == munin (2 distinct, 10 total) == Sep 20 01:23:53 munin sudo[555270]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x5] Sep 20 01:23:53 munin sudo[555270]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x5] == newhonors2 (1 distinct, 24 total) == Sep 20 01:13:03 newhonors2 dhcpcd[2883239]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 20 01:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 418) *** Sep 20 01:05:24 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6018/6018, ET: 23) *** Sep 20 01:05:25 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 53/53, ET: 24) *** Sep 20 01:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 20 01:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 6166/6166, ET: 0) *** Sep 20 01:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 20 01:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 50/50, ET: 0) *** Sep 20 01:08:02 ntop00 setroubleshoot[737926]: 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 20 01:08:02 ntop00 setroubleshoot[737926]: 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 20 01:08:02 ntop00 setroubleshoot[737926]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 20 01:08:02 ntop00 setroubleshoot[737926]: 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 20 01:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 20 01:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 20 01:10:26 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 6326/6326, ET: 25) *** Sep 20 01:10:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 59/59, ET: 25) *** Sep 20 01:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 20 01:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 6601/6601, ET: 0) *** Sep 20 01:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 20 01:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 66/66, ET: 0) *** Sep 20 01:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 20 01:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 20 01:15:25 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 6436/6436, ET: 24) *** Sep 20 01:15:26 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 69/69, ET: 25) *** Sep 20 01:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 20 01:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 6144/6144, ET: 0) *** Sep 20 01:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 20 01:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 77/77, ET: 0) *** Sep 20 01:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 20 01:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 20 01:20:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 6059/6059, ET: 22) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 01:09:09 outbound00.cs.umd.edu python3[1877187]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 20 01:13:06 outbound01.cs.umd.edu python3[4136449]: ldapdb [x6] Sep 20 01:24:50 outbound01.cs.umd.edu krb5_child[4138810]: Client 'admin@UMD.EDU' not found in Kerberos database == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994602]: link_config: could not get ethtool features for vetha1a9337 Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994602]: Could not set offload features of vetha1a9337: No such device Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994637]: Could not generate persistent MAC address for vethf2bfa3a: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994638]: Could not generate persistent MAC address for vethd34b8b5: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994641]: Could not generate persistent MAC address for veth7d52270: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994642]: Could not generate persistent MAC address for veth1028cdc: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994665]: Could not generate persistent MAC address for vethfeb600d: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994666]: Could not generate persistent MAC address for veth15d554a: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994691]: Could not generate persistent MAC address for vethfbd2cf8: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994692]: Could not generate persistent MAC address for veth2636677: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994710]: Could not generate persistent MAC address for veth8171b73: No such file or directory Sep 20 01:12:43 sentry-docker00.cs.umd.edu systemd-udevd[3994716]: Could not generate persistent MAC address for veth769d04d: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004148]: link_config: could not get ethtool features for vethfbd2cf8 Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004148]: Could not set offload features of vethfbd2cf8: No such device Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004263]: Could not generate persistent MAC address for veth59b8582: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004264]: Could not generate persistent MAC address for veth816cb6b: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004289]: Could not generate persistent MAC address for veth9d0b1b9: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004290]: Could not generate persistent MAC address for veth8503f3b: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004290]: Could not generate persistent MAC address for veth226976c: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004295]: Could not generate persistent MAC address for veth4f7810c: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004317]: Could not generate persistent MAC address for veth6ed228a: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004318]: Could not generate persistent MAC address for veth349d1a7: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004334]: Could not generate persistent MAC address for veth22bc751: No such file or directory Sep 20 01:32:51 sentry-docker00.cs.umd.edu systemd-udevd[4004362]: Could not generate persistent MAC address for vethcf29f74: No such file or directory Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013639]: link_config: could not get ethtool features for veth59b8582 Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013639]: Could not set offload features of veth59b8582: No such device Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013641]: link_config: could not get ethtool features for veth6ed228a Sep 20 01:52:59 sentry-docker00.cs.umd.edu systemd-udevd[4013641]: Could not set offload features of veth6ed228a: No such device Sep 20 01:53:00 sentry-docker00.cs.umd.edu systemd-udevd[4013672]: Could not generate persistent MAC address for veth408adde: No such file or directory Sep 20 01:53:00 sentry-docker00.cs.umd.edu systemd-udevd[4013673]: Could not generate persistent MAC address for veth8860a5b: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 01: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 01: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 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 1 total) == Sep 20 01:13:08 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (9 distinct, 12 total) == Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 [x2] Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.Fv5kj7/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 [x2] Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.Fv5kj7. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 20 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 01:06:43 submit26-b9-f3 setroubleshoot[2066520]: 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 (9 distinct, 9 total) == Sep 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.BSLo5X/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.BSLo5X. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 20 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 01:24:47 submit26-b9-f4 setroubleshoot[1486929]: 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 == tma-0 (1 distinct, 1 total) == Sep 20 01:54:55 tma-0 sshd[7248]: error: PAM: Authentication failure for admin from 107.116.79.34.bc.googleusercontent.com