Command: /usr/local/sbin/syslog-digest.py Time : 0.0505s Status : exited 0 Output : Syslog digest — 2026-09-21 22:05 EDT Processed 1,896 lines, filtered 1,368 (72%). 528 unknown (194 distinct) from 21 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 21 21:54:28 b0b02.cs.umd.edu rustdesk[3764865]: cannot open display: == bale (5 distinct, 90 total) == Sep 21 21:05:45 bale setroubleshoot[1588368]: failed to retrieve rpm info for /dev/nvme0 [x39] Sep 21 21:05:45 bale setroubleshoot[1588368]: 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 21 21:05:48 bale setroubleshoot[1588368]: 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 21 21:05:51 bale setroubleshoot[1588368]: 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 21 21:06:03 bale setroubleshoot[1588983]: 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 [x15] == csfw00a (1 distinct, 115 total) == Sep 21 21:04:41 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x115] == gle-dind04 (1 distinct, 1 total) == Sep 21 21:27:09 gle-dind04 lldpd[1171]: unable to send packet on real device for veth66e027c: No such device or address == idm00 (1 distinct, 1 total) == Sep 21 21:54:03 idm00 named[4166701]: client @0x7f11a00732a8 10.73.240.42#63661: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 21 21:37:55 idmp0 named[1598691]: client @0x7f2d44011478 10.73.240.43#60837: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 21 21:48:23 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == krispykreme.cs.umd.edu (4 distinct, 4 total) == Sep 21 21:14:21 krispykreme.cs.umd.edu sshd-session[861565]: pam_access(sshd:auth): access denied for user `nobody' from `193.187.110.214' Sep 21 21:14:23 krispykreme.cs.umd.edu sshd-session[861563]: error: PAM: User not known to the underlying authentication module for nobody from 193.187.110.214 Sep 21 21:56:53 krispykreme.cs.umd.edu sshd-session[873797]: pam_access(sshd:auth): access denied for user `root' from `193.187.110.214' Sep 21 21:56:55 krispykreme.cs.umd.edu sshd-session[873794]: error: PAM: Authentication failure for root from 193.187.110.214 == matrix (2 distinct, 2 total) == Sep 21 21:23:33 matrix sshd[135522]: error: PAM: Authentication failure for nobody from 193.187.110.214 Sep 21 21:59:20 matrix sshd[155631]: error: PAM: Authentication failure for root from 193.187.110.214 == munin (2 distinct, 20 total) == Sep 21 21:23:35 munin sudo[1513382]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x10] Sep 21 21:23:35 munin sudo[1513382]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x10] == newhonors2 (1 distinct, 24 total) == Sep 21 21:13:03 newhonors2 dhcpcd[2966496]: dhcpcd is not running [x24] == ntop00 (102 distinct, 146 total) == Sep 21 21:05:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 21 21:05:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 21 21:05:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 6159/6159, ET: 31) *** Sep 21 21:05:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 52/52, ET: 31) *** Sep 21 21:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 21 21:08:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 6446/6446, ET: 0) *** Sep 21 21:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 21 21:08:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 45/45, ET: 0) *** Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l 3969d577-4cb5-4e27-801d-194ae9d63921 [x12] Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l 1748ca57-ea8d-4066-949f-ecf1a327c86e [x12] Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 21 21:08:02 ntop00 setroubleshoot[1088496]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l 046d980a-63cc-4e76-9e37-ec6be0967e9a [x12] Sep 21 21:10:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 21 21:10:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 21 21:10:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 6252/6252, ET: 31) *** Sep 21 21:10:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 57/57, ET: 31) *** Sep 21 21:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 21 21:13:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 6179/6179, ET: 0) *** Sep 21 21:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 21 21:13:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 52/52, ET: 0) *** Sep 21 21:15:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 21 21:15:02 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 21 21:15:32 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 6211/6211, ET: 31) *** Sep 21 21:15:32 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 41/41, ET: 30) *** Sep 21 21:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 21 21:18:01 ntop00 nfacctd[982893]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 46/46, ET: 0) *** Sep 21 21:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 21 21:18:01 ntop00 sfacctd[982817]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 6407/6407, ET: 0) *** Sep 21 21:20:01 ntop00 sfacctd[982817]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 21 21:20:01 ntop00 nfacctd[982893]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** ... 72 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 21 21:09:09 outbound00.cs.umd.edu python3[2498580]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 21 21:13:06 outbound01.cs.umd.edu python3[565714]: ldapdb [x6] == sebatinsky.cs.umd.edu (1 distinct, 1 total) == Sep 21 21:13:59 sebatinsky.cs.umd.edu kernel: hpet1: lost 1 rtc interrupts == sentry-docker00.cs.umd.edu (40 distinct, 40 total) == Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045693]: link_config: could not get ethtool features for veth1093b24 Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045693]: Could not set offload features of veth1093b24: No such device Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045737]: link_config: could not set ethtool features for veth69d3675 Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045737]: Could not set offload features of veth69d3675: Operation not permitted Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045771]: Could not generate persistent MAC address for veth3bb02cb: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045772]: Could not generate persistent MAC address for veth8170379: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045775]: Could not generate persistent MAC address for veth7772a67: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045776]: Could not generate persistent MAC address for veth2393a8d: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045799]: Could not generate persistent MAC address for veth750bc4f: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045800]: Could not generate persistent MAC address for vethb0cd3e5: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045818]: Could not generate persistent MAC address for veth061570d: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045821]: Could not generate persistent MAC address for vethf297150: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045838]: Could not generate persistent MAC address for vetha3396ef: No such file or directory Sep 21 21:10:53 sentry-docker00.cs.umd.edu systemd-udevd[1045841]: Could not generate persistent MAC address for veth9dac3db: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055338]: link_config: could not get ethtool features for veth7772a67 Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055338]: Could not set offload features of veth7772a67: No such device Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055426]: link_config: could not get ethtool features for veth750bc4f Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055426]: Could not set offload features of veth750bc4f: No such device Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055450]: Could not generate persistent MAC address for vethd3e061e: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055451]: Could not generate persistent MAC address for veth88c5e91: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055456]: Could not generate persistent MAC address for veth34ba79e: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055469]: Could not generate persistent MAC address for vethd6f29f8: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055479]: Could not generate persistent MAC address for veth860ce71: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055480]: Could not generate persistent MAC address for vethd7deeae: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055516]: Could not generate persistent MAC address for veth91c308b: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055513]: Could not generate persistent MAC address for veth3a61427: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055514]: Could not generate persistent MAC address for veth938f3e5: No such file or directory Sep 21 21:31:01 sentry-docker00.cs.umd.edu systemd-udevd[1055524]: Could not generate persistent MAC address for vethfa0293d: No such file or directory Sep 21 21:51:09 sentry-docker00.cs.umd.edu systemd-udevd[1064818]: link_config: could not get ethtool features for veth34ba79e Sep 21 21:51:09 sentry-docker00.cs.umd.edu systemd-udevd[1064818]: Could not set offload features of veth34ba79e: No such device ... 10 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 21:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 21 21:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 21 21:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 21 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 3 total) == Sep 21 21:09:51 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f2 (1 distinct, 1 total) == Sep 21 22:03:06 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-f3 (10 distinct, 14 total) == Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 [x2] Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 [x2] Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qRyYjg/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qRyYjg. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:06:43 submit26-b9-f3 setroubleshoot[2381190]: 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 21 21:22:00 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] == submit26-b9-f4 (10 distinct, 12 total) == Sep 21 21:18:11 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.qNTrBE/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.qNTrBE. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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 21 21:24:49 submit26-b9-f4 setroubleshoot[1727673]: 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