Command: /usr/local/sbin/syslog-digest.py Time : 0.0532s Status : exited 0 Output : Syslog digest — 2026-09-22 22:05 EDT Processed 2,389 lines, filtered 1,885 (78%). 504 unknown (192 distinct) from 20 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 22 21:56:01 b0b02.cs.umd.edu rustdesk[4886]: cannot open display: == bale (6 distinct, 85 total) == Sep 22 21:05:51 bale setroubleshoot[1924253]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 22 21:05:52 bale setroubleshoot[1924253]: 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 22 21:05:54 bale setroubleshoot[1924253]: 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 22 21:05:57 bale setroubleshoot[1924253]: 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 22 21:06:09 bale setroubleshoot[1924869]: 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 [x12] Sep 22 21:51:07 bale kernel: ata7: limiting SATA link speed to 1.5 Gbps == galax (2 distinct, 5 total) == Sep 22 21:30:00 galax systemd[1]: sysstat-collect.service: Condition check process exited, code=dumped, status=11/SEGV [x4] Sep 22 21:46:29 galax systemd[1]: motd-news.service: Main process exited, code=dumped, status=11/SEGV == idm00 (1 distinct, 1 total) == Sep 22 21:54:25 idm00 named[4166701]: client @0x7f11a0057bb8 10.73.240.42#64698: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 22 21:37:54 idmp0 named[1598691]: client @0x7f2d3001d0e8 10.73.240.43#54840: update '73.10.in-addr.arpa/IN' denied == irb2156 (2 distinct, 2 total) == Sep 22 21:06:37 irb2156 systemd-resolved[3402]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.73.244.10. Sep 22 21:06:53 irb2156 systemd-resolved[3402]: Using degraded feature set TCP instead of UDP for DNS server 10.73.244.10. == itmon02 (1 distinct, 2 total) == Sep 22 21:48:43 itmon02 sshd[1483508]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 38 total) == Sep 22 21:38:04 munin sudo[2039705]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x19] Sep 22 21:38:04 munin sudo[2039705]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x19] == netman.cs.umd.edu (3 distinct, 50 total) == Sep 22 21:15:04 netman.cs.umd.edu krb5_child[3734757]: Preauthentication failed [x28] Sep 22 21:18:42 netman.cs.umd.edu krb5_child[3736152]: Client 'admin@UMD.EDU' not found in Kerberos database [x20] Sep 22 21:24:41 netman.cs.umd.edu krb5_child[3737393]: Client 'gitlab@UMD.EDU' not found in Kerberos database [x2] == newhonors2 (1 distinct, 24 total) == Sep 22 21:13:03 newhonors2 dhcpcd[3012399]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 22 21:05:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 22 21:05:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 322) *** Sep 22 21:05:28 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 4672/4672, ET: 27) *** Sep 22 21:05:28 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 322, QN: 55/55, ET: 27) *** Sep 22 21:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 22 21:08:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 5260/5260, ET: 0) *** Sep 22 21:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 323) *** Sep 22 21:08:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 323, QN: 46/46, ET: 0) *** Sep 22 21:08:02 ntop00 setroubleshoot[1279567]: 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 22 21:08:02 ntop00 setroubleshoot[1279567]: 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 22 21:08:02 ntop00 setroubleshoot[1279567]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 22 21:08:02 ntop00 setroubleshoot[1279567]: 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 22 21:10:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 22 21:10:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 324) *** Sep 22 21:10:30 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 5281/5281, ET: 29) *** Sep 22 21:10:30 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 324, QN: 49/49, ET: 29) *** Sep 22 21:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 22 21:13:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 4713/4713, ET: 0) *** Sep 22 21:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 325) *** Sep 22 21:13:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 325, QN: 50/50, ET: 0) *** Sep 22 21:15:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 22 21:15:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 326) *** Sep 22 21:15:25 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 4411/4411, ET: 24) *** Sep 22 21:15:25 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - END (PID: 326, QN: 52/52, ET: 24) *** Sep 22 21:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 22 21:18:01 ntop00 sfacctd[1173903]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 4659/4659, ET: 0) *** Sep 22 21:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - START (PID: 327) *** Sep 22 21:18:01 ntop00 nfacctd[1173965]: INFO ( p1/print ): *** Purging cache - END (PID: 327, QN: 64/64, ET: 0) *** Sep 22 21:20:01 ntop00 sfacctd[1173903]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** Sep 22 21:20:01 ntop00 nfacctd[1173965]: INFO ( m1/mysql ): *** Purging cache - START (PID: 328) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (3 distinct, 17 total) == Sep 22 21:09:10 outbound00.cs.umd.edu python3[2838411]: ldapdb [x6] Sep 22 21:36:57 outbound00.cs.umd.edu krb5_child[2844957]: Preauthentication failed [x9] Sep 22 21:40:29 outbound00.cs.umd.edu krb5_child[2846021]: Client 'admin@UMD.EDU' not found in Kerberos database [x2] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 22 21:13:07 outbound01.cs.umd.edu python3[934131]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746929]: Could not generate persistent MAC address for veth768d8de: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746930]: Could not generate persistent MAC address for veth0d94faf: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746948]: Could not generate persistent MAC address for veth8b0e1d0: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746934]: Could not generate persistent MAC address for veth94b4ea0: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746957]: Could not generate persistent MAC address for veth147d726: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746958]: Could not generate persistent MAC address for vethb655f96: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746983]: Could not generate persistent MAC address for veth24fe5ae: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1746984]: Could not generate persistent MAC address for veth9fa228d: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1747013]: Could not generate persistent MAC address for vethd8862bd: No such file or directory Sep 22 21:20:52 sentry-docker00.cs.umd.edu systemd-udevd[1747017]: Could not generate persistent MAC address for vethc0d1f42: No such file or directory Sep 22 21:41:00 sentry-docker00.cs.umd.edu systemd-udevd[1756529]: link_config: could not get ethtool features for veth147d726 Sep 22 21:41:00 sentry-docker00.cs.umd.edu systemd-udevd[1756529]: Could not set offload features of veth147d726: No such device Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756565]: Could not generate persistent MAC address for veth05ff771: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756566]: Could not generate persistent MAC address for veth1460b78: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756569]: Could not generate persistent MAC address for vethfaedeb5: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756570]: Could not generate persistent MAC address for veth037d964: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756566]: Could not generate persistent MAC address for vethbc33a54: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756585]: Could not generate persistent MAC address for veth2fb13e3: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756595]: Could not generate persistent MAC address for veth4fbb92b: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756596]: Could not generate persistent MAC address for veth29aa4bb: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756606]: Could not generate persistent MAC address for veth3532b96: No such file or directory Sep 22 21:41:01 sentry-docker00.cs.umd.edu systemd-udevd[1756613]: Could not generate persistent MAC address for veth6e36501: No such file or directory Sep 22 22:01:08 sentry-docker00.cs.umd.edu systemd-udevd[1765920]: link_config: could not get ethtool features for vethfaedeb5 Sep 22 22:01:08 sentry-docker00.cs.umd.edu systemd-udevd[1765920]: Could not set offload features of vethfaedeb5: No such device Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1765995]: Could not generate persistent MAC address for veth33eef6d: No such file or directory Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1765996]: Could not generate persistent MAC address for veth89d4caa: No such file or directory Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1765999]: Could not generate persistent MAC address for veth6412e8c: No such file or directory Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1766000]: Could not generate persistent MAC address for veth3e7e416: No such file or directory Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1766023]: Could not generate persistent MAC address for veth28898c7: No such file or directory Sep 22 22:01:09 sentry-docker00.cs.umd.edu systemd-udevd[1766024]: Could not generate persistent MAC address for veth39456f3: No such file or directory ... 4 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 22 21:43:07 soul krb5_child[128121]: Client 'admin@UMD.EDU' not found in Kerberos database == strawberry (7 distinct, 38 total) == Sep 22 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 22 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 22 21:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 22 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 22 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 22 21:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 22 21:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 9 total) == Sep 22 21:05:09 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x9] == submit26-b9-f2 (1 distinct, 10 total) == Sep 22 21:05:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x10] == submit26-b9-f3 (13 distinct, 20 total) == Sep 22 21:05:06 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] Sep 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QTwS7c/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QTwS7c. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:06:44 submit26-b9-f3 setroubleshoot[2588372]: 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 22 21:15:04 submit26-b9-f3 kernel: show_signal_msg: 7 callbacks suppressed Sep 22 21:15:04 submit26-b9-f3 systemd-coredump[2589749]: Process 2589746 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2589746:#012#0 0x00000000004019b6 calculateNumericScore (grades + 0x19b6)#012#1 0x00000000004013d9 main (grades + 0x13d9)#012#2 0x00007f661de2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007f661de2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (grades + 0x10a5)#012ELF object binary architecture: AMD x86-64 Sep 22 21:35:07 submit26-b9-f3 systemd-coredump[2593108]: Process 2593105 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2593105:#012#0 0x00000000004019b6 calculateNumericScore (grades + 0x19b6)#012#1 0x00000000004013d9 main (grades + 0x13d9)#012#2 0x00007ff2bb02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007ff2bb02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (grades + 0x10a5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (11 distinct, 16 total) == Sep 22 21:15:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x6] Sep 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.hMhhyH/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.hMhhyH. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 22 21:24:48 submit26-b9-f4 setroubleshoot[1903132]: 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 Sep 22 21:55:12 submit26-b9-f4 systemd-coredump[1908398]: Process 1908395 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1908395:#012#0 0x00000000004019b6 calculateNumericScore (grades + 0x19b6)#012#1 0x00000000004013d9 main (grades + 0x13d9)#012#2 0x00007fbb8682a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#3 0x00007fbb8682a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#4 0x00000000004010a5 _start (grades + 0x10a5)#012ELF object binary architecture: AMD x86-64