Command: /usr/local/sbin/syslog-digest.py Time : 0.8293s Status : exited 0 Output : Syslog digest — 2026-09-26 02:05 EDT Processed 26,104 lines, filtered 1,326 (5%). 24,778 unknown (193 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 26 02:00:52 b0b02.cs.umd.edu rustdesk[1170561]: cannot open display: == cheezit.cs.umd.edu (3 distinct, 4 total) == Sep 26 01:43:38 cheezit.cs.umd.edu sshd-session[3199959]: pam_access(sshd:auth): access denied for user `larry' from `71.191.93.172' [x2] Sep 26 01:43:40 cheezit.cs.umd.edu sshd-session[3199959]: Error in Duo login for 'larry' from 71.191.93.172 Sep 26 01:43:40 cheezit.cs.umd.edu sshd-session[3199957]: error: PAM: Authentication failure for larry from 71.191.93.172 == helmsdeep (1 distinct, 1 total) == Sep 26 01:05:47 helmsdeep kernel: clocksource: timekeeping watchdog on CPU0: kvm-clock retried 1 times before success == idm00 (1 distinct, 1 total) == Sep 26 01:54:08 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#62715: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 26 01:39:29 idmp0 named[1598691]: client @0x7f2d200241d8 10.73.240.43#50625: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 6 total) == Sep 26 01:07:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x6] == munin (2 distinct, 4 total) == Sep 26 01:53:22 munin sudo[3700488]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 26 01:53:22 munin sudo[3700488]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == netman.cs.umd.edu (3 distinct, 3 total) == Sep 26 02:00:44 netman.cs.umd.edu setroubleshoot[821850]: Deleting alert 49825fae-e786-4ccd-8ab4-15b21ec01b20, it is allowed in current policy Sep 26 02:00:44 netman.cs.umd.edu setroubleshoot[821850]: Deleting alert 3339e8ec-2a3c-445e-9160-e54349c55e12, it is allowed in current policy Sep 26 02:00:47 netman.cs.umd.edu setroubleshoot[821850]: SELinux is preventing /usr/sbin/vsftpd from name_connect access on the tcp_socket port 49191. For complete SELinux messages run: sealert -l 13cab75a-d208-4d9a-93ef-61c98f995ae3 == newhonors2 (1 distinct, 24 total) == Sep 26 01:13:03 newhonors2 dhcpcd[3163026]: dhcpcd is not running [x24] == ntop00 (115 distinct, 24625 total) == Sep 26 01:05:13 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 418, QN: 6909/6909, ET: 12) *** Sep 26 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 26 01:08:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 7332/7332, ET: 0) *** Sep 26 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 419) *** Sep 26 01:08:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 419, QN: 55/55, ET: 0) *** Sep 26 01:10:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 26 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 420) *** Sep 26 01:10:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 67/67, ET: 0) *** Sep 26 01:10:11 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 420, QN: 6593/6593, ET: 10) *** Sep 26 01:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 26 01:13:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 5698/5698, ET: 0) *** Sep 26 01:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 421) *** Sep 26 01:13:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 421, QN: 53/53, ET: 0) *** Sep 26 01:15:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 26 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 422) *** Sep 26 01:15:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 46/46, ET: 0) *** Sep 26 01:15:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 422, QN: 5629/5629, ET: 8) *** Sep 26 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 26 01:18:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 5671/5671, ET: 0) *** Sep 26 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 423) *** Sep 26 01:18:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 423, QN: 44/44, ET: 0) *** Sep 26 01:20:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 26 01:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - START (PID: 424) *** Sep 26 01:20:01 ntop00 nfacctd[381405]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 42/42, ET: 0) *** Sep 26 01:20:09 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - END (PID: 424, QN: 5771/5771, ET: 8) *** Sep 26 01:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 26 01:23:01 ntop00 sfacctd[381335]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 5401/5401, ET: 0) *** Sep 26 01:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - START (PID: 425) *** Sep 26 01:23:01 ntop00 nfacctd[381405]: INFO ( p1/print ): *** Purging cache - END (PID: 425, QN: 53/53, ET: 0) *** Sep 26 01:25:01 ntop00 sfacctd[381335]: INFO ( m1/mysql ): *** Purging cache - START (PID: 426) *** ... 85 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 26 01:09:09 outbound00.cs.umd.edu python3[3943681]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 26 01:13:07 outbound01.cs.umd.edu python3[2009776]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 26 01:09:42 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892057]: Could not generate persistent MAC address for vethd9029a7: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892058]: Could not generate persistent MAC address for veth8810242: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892061]: Could not generate persistent MAC address for veth6d028b9: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892062]: Could not generate persistent MAC address for vethcc1ad8e: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892082]: Could not generate persistent MAC address for vetha69eeaf: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892070]: Could not generate persistent MAC address for veth1d6271a: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892073]: Could not generate persistent MAC address for veth8adddd7: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892066]: Could not generate persistent MAC address for vethbbc963f: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892070]: Could not generate persistent MAC address for veth9c9fb40: No such file or directory Sep 26 01:12:16 sentry-docker00.cs.umd.edu systemd-udevd[3892073]: Could not generate persistent MAC address for vethb94b71a: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901683]: Could not generate persistent MAC address for veth15b51e9: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901684]: Could not generate persistent MAC address for vethfd7a83c: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901687]: Could not generate persistent MAC address for vetha06c282: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901688]: Could not generate persistent MAC address for veth88bdac0: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901711]: Could not generate persistent MAC address for veth318a7c2: No such file or directory Sep 26 01:32:24 sentry-docker00.cs.umd.edu systemd-udevd[3901712]: Could not generate persistent MAC address for vetha07e683: No such file or directory Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901724]: Could not generate persistent MAC address for vetha6f3888: No such file or directory Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901720]: Could not generate persistent MAC address for vetha4686e0: No such file or directory Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901744]: Could not generate persistent MAC address for veth2b2bcd5: No such file or directory Sep 26 01:32:25 sentry-docker00.cs.umd.edu systemd-udevd[3901740]: Could not generate persistent MAC address for vethbdab5c7: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911103]: link_config: could not get ethtool features for veth15b51e9 Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911103]: Could not set offload features of veth15b51e9: No such device Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911105]: link_config: could not get ethtool features for vetha06c282 Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911105]: Could not set offload features of vetha06c282: No such device Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911142]: Could not generate persistent MAC address for veth3997e0a: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911143]: Could not generate persistent MAC address for veth15b7f76: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911147]: Could not generate persistent MAC address for veth3531c67: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911146]: Could not generate persistent MAC address for veth3920aa7: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911171]: Could not generate persistent MAC address for veth61db956: No such file or directory Sep 26 01:52:33 sentry-docker00.cs.umd.edu systemd-udevd[3911170]: Could not generate persistent MAC address for veth6c50115: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 26 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 26 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 26 01:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 26 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 26 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 26 01:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 26 01:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (10 distinct, 13 total) == Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tbTNn9/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tbTNn9. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 [x2] Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: 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 Sep 26 01:06:45 submit26-b9-f3 setroubleshoot[3499410]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.DSBIbI/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f == submit26-b9-f4 (9 distinct, 9 total) == Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.gj1MMJ/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.gj1MMJ. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 26 01:24:48 submit26-b9-f4 setroubleshoot[2560023]: 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 == wraith (1 distinct, 1 total) == Sep 26 01:31:30 wraith kernel: set_capacity_and_notify: 28 callbacks suppressed