Command: /usr/local/sbin/syslog-digest.py Time : 0.0413s Status : exited 0 Output : Syslog digest — 2026-09-27 22:05 EDT Processed 1,668 lines, filtered 1,421 (85%). 247 unknown (177 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 27 22:03:36 b0b02.cs.umd.edu rustdesk[1844750]: cannot open display: == cheezit.cs.umd.edu (1 distinct, 1 total) == Sep 27 21:27:47 cheezit.cs.umd.edu sshd-session[3812736]: pam_access(sshd:auth): access denied for user `leonidas' from `71.163.104.121' == galax (1 distinct, 1 total) == Sep 27 21:37:01 galax kernel: workqueue: dm_irq_work_func [amdgpu] hogged CPU for >10000us 16387 times, consider switching to WQ_UNBOUND == gle-dind04 (1 distinct, 1 total) == Sep 27 21:45:24 gle-dind04 lldpd[1171]: unable to send packet on real device for veth0c17c13: No such device or address == idm00 (1 distinct, 1 total) == Sep 27 21:54:09 idm00 named[4166701]: client @0x7f11a945b458 10.73.240.42#49879: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 27 21:39:27 idmp0 named[1598691]: client @0x7f2d38010098 10.73.240.43#60695: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 27 21:22:58 itmon02 sshd[1483508]: error: beginning MaxStartups throttling == krispykreme.cs.umd.edu (1 distinct, 1 total) == Sep 27 21:29:57 krispykreme.cs.umd.edu sshd-session[3387472]: pam_access(sshd:auth): access denied for user `leonidas' from `71.163.104.121' == munin (2 distinct, 8 total) == Sep 27 21:38:41 munin sudo[459236]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x4] Sep 27 21:38:41 munin sudo[459236]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x4] == newhonors2 (1 distinct, 24 total) == Sep 27 21:13:03 newhonors2 dhcpcd[3246724]: dhcpcd is not running [x24] == ntop00 (99 distinct, 99 total) == Sep 27 21:05:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 24) *** Sep 27 21:05:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 25) *** Sep 27 21:05:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 24, QN: 3954/3954, ET: 0) *** Sep 27 21:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 24) *** Sep 27 21:05:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 24, QN: 49/49, ET: 0) *** Sep 27 21:05:08 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 25, QN: 3954/3954, ET: 7) *** Sep 27 21:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 25) *** Sep 27 21:06:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 25, QN: 46/46, ET: 0) *** Sep 27 21:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 26) *** Sep 27 21:10:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 27) *** Sep 27 21:10:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 26, QN: 4186/4186, ET: 0) *** Sep 27 21:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 26) *** Sep 27 21:10:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 26, QN: 45/45, ET: 0) *** Sep 27 21:10:07 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 27, QN: 4186/4186, ET: 6) *** Sep 27 21:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 27) *** Sep 27 21:11:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 27, QN: 51/51, ET: 0) *** Sep 27 21:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 28) *** Sep 27 21:15:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 29) *** Sep 27 21:15:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 28, QN: 3691/3691, ET: 0) *** Sep 27 21:15:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 28) *** Sep 27 21:15:02 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 28, QN: 44/44, ET: 1) *** Sep 27 21:15:06 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 29, QN: 3691/3691, ET: 5) *** Sep 27 21:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - START (PID: 29) *** Sep 27 21:16:01 ntop00 nfacctd[776711]: INFO ( p1/print ): *** Purging cache - END (PID: 29, QN: 47/47, ET: 0) *** Sep 27 21:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - START (PID: 30) *** Sep 27 21:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - START (PID: 30) *** Sep 27 21:20:01 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - START (PID: 31) *** Sep 27 21:20:01 ntop00 sfacctd[776291]: INFO ( p1/print ): *** Purging cache - END (PID: 30, QN: 4601/4601, ET: 0) *** Sep 27 21:20:01 ntop00 nfacctd[776711]: INFO ( m1/mysql ): *** Purging cache - END (PID: 30, QN: 73/73, ET: 0) *** Sep 27 21:20:08 ntop00 sfacctd[776291]: INFO ( m1/mysql ): *** Purging cache - END (PID: 31, QN: 4601/4601, ET: 7) *** ... 69 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 27 21:09:09 outbound00.cs.umd.edu python3[370658]: ldapdb [x6] == outbound01.cs.umd.edu (2 distinct, 7 total) == Sep 27 21:09:03 outbound01.cs.umd.edu krb5_child[2635866]: Client 'admin@UMD.EDU' not found in Kerberos database Sep 27 21:13:06 outbound01.cs.umd.edu python3[2636786]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 27 21:13:44 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (38 distinct, 38 total) == Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942648]: link_config: could not get ethtool features for veth2484ba8 Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942648]: Could not set offload features of veth2484ba8: No such device Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942654]: link_config: could not get ethtool features for vetha5161c6 Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942654]: Could not set offload features of vetha5161c6: No such device Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942687]: Could not generate persistent MAC address for veth98e093d: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942688]: Could not generate persistent MAC address for vethba003a1: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942713]: Could not generate persistent MAC address for veth1d05d18: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942714]: Could not generate persistent MAC address for veth1642a6e: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942732]: Could not generate persistent MAC address for veth23b18d8: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942729]: Could not generate persistent MAC address for vethcb870ec: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942736]: Could not generate persistent MAC address for veth5c49a4c: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942727]: Could not generate persistent MAC address for veth583d493: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942752]: Could not generate persistent MAC address for veth4399420: No such file or directory Sep 27 21:10:26 sentry-docker00.cs.umd.edu systemd-udevd[942755]: Could not generate persistent MAC address for vethc98a0ba: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952573]: link_config: could not get ethtool features for veth1d05d18 Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952573]: Could not set offload features of veth1d05d18: No such device Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952608]: Could not generate persistent MAC address for vethe12ffc2: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952609]: Could not generate persistent MAC address for veth9bb0cdb: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952612]: Could not generate persistent MAC address for veth199e2df: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952613]: Could not generate persistent MAC address for veth71b531c: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952624]: Could not generate persistent MAC address for veth7b75593: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952628]: Could not generate persistent MAC address for vetha572474: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952625]: Could not generate persistent MAC address for veth2d8b3bd: No such file or directory Sep 27 21:30:34 sentry-docker00.cs.umd.edu systemd-udevd[952623]: Could not generate persistent MAC address for vethba19cba: No such file or directory Sep 27 21:30:35 sentry-docker00.cs.umd.edu systemd-udevd[952727]: Could not generate persistent MAC address for veth19f1e55: No such file or directory Sep 27 21:30:35 sentry-docker00.cs.umd.edu systemd-udevd[952722]: Could not generate persistent MAC address for vethbd8393e: No such file or directory Sep 27 21:50:43 sentry-docker00.cs.umd.edu systemd-udevd[961999]: link_config: could not get ethtool features for vethbd8393e Sep 27 21:50:43 sentry-docker00.cs.umd.edu systemd-udevd[961999]: Could not set offload features of vethbd8393e: No such device Sep 27 21:50:43 sentry-docker00.cs.umd.edu systemd-udevd[962031]: Could not generate persistent MAC address for vethcb9ae85: No such file or directory Sep 27 21:50:43 sentry-docker00.cs.umd.edu systemd-udevd[962032]: Could not generate persistent MAC address for vethfd0156f: No such file or directory ... 8 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 27 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 27 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 27 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 27 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 27 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 27 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 27 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (9 distinct, 9 total) == Sep 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.cbEuVN/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.cbEuVN. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:06:45 submit26-b9-f3 setroubleshoot[3822090]: 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 27 21:24:49 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.j4i2nx/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.j4i2nx. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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 27 21:24:50 submit26-b9-f4 setroubleshoot[2783059]: 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