Command: /usr/local/sbin/syslog-digest.py Time : 0.0546s Status : exited 0 Output : Syslog digest — 2026-09-19 13:05 EDT Processed 2,967 lines, filtered 2,462 (82%). 505 unknown (178 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 12:50:57 b0b02.cs.umd.edu rustdesk[2892906]: cannot open display: == bale (5 distinct, 86 total) == Sep 19 12:05:14 bale setroubleshoot[857763]: failed to retrieve rpm info for /dev/nvme0 [x37] Sep 19 12:05:15 bale setroubleshoot[857763]: 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 19 12:05:17 bale setroubleshoot[857763]: 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 19 12:05:20 bale setroubleshoot[857763]: 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 19 12:05:32 bale setroubleshoot[858379]: 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] == csfw00a (1 distinct, 111 total) == Sep 19 12:05:01 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x111] == helmsdeep (1 distinct, 1 total) == Sep 19 12:27:07 helmsdeep kernel: clocksource: timekeeping watchdog on CPU1: kvm-clock retried 1 times before success == idm00 (1 distinct, 1 total) == Sep 19 12:53:59 idm00 named[4166701]: client @0x7f11a4068068 10.73.240.42#62981: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 12:37:56 idmp0 named[1598691]: client @0x7f2d1c04b088 10.73.240.43#51505: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 4 total) == Sep 19 12:44:02 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x4] == munin (2 distinct, 4 total) == Sep 19 12:23:47 munin sudo[273009]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x2] Sep 19 12:23:47 munin sudo[273009]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x2] == newhonors2 (1 distinct, 24 total) == Sep 19 12:13:02 newhonors2 dhcpcd[2858466]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 19 12:05:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 106) *** Sep 19 12:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 106, QN: 62/62, ET: 0) *** Sep 19 12:05:20 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 106, QN: 5950/5950, ET: 19) *** Sep 19 12:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 107) *** Sep 19 12:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 107, QN: 52/52, ET: 0) *** Sep 19 12:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 107) *** Sep 19 12:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 107, QN: 6125/6125, ET: 0) *** Sep 19 12:08:02 ntop00 setroubleshoot[635011]: 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 19 12:08:02 ntop00 setroubleshoot[635011]: 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 19 12:08:02 ntop00 setroubleshoot[635011]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 12:08:02 ntop00 setroubleshoot[635011]: 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 19 12:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 108) *** Sep 19 12:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 108) *** Sep 19 12:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 108, QN: 61/61, ET: 0) *** Sep 19 12:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 108, QN: 6189/6189, ET: 20) *** Sep 19 12:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 109) *** Sep 19 12:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 109) *** Sep 19 12:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 109, QN: 55/55, ET: 0) *** Sep 19 12:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 109, QN: 6309/6309, ET: 0) *** Sep 19 12:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 110) *** Sep 19 12:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 110) *** Sep 19 12:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 6431/6431, ET: 22) *** Sep 19 12:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 110, QN: 50/50, ET: 22) *** Sep 19 12:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 111) *** Sep 19 12:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 6052/6052, ET: 0) *** Sep 19 12:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 111) *** Sep 19 12:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 111, QN: 62/62, ET: 0) *** Sep 19 12:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) *** Sep 19 12:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 112) *** Sep 19 12:20:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 112, QN: 6050/6050, ET: 20) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 12:09:09 outbound00.cs.umd.edu python3[1694598]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 12:13:06 outbound01.cs.umd.edu python3[3953247]: ldapdb [x6] == sentry-docker00.cs.umd.edu (34 distinct, 34 total) == Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625069]: Could not generate persistent MAC address for vethdc50ac0: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625070]: Could not generate persistent MAC address for vethe22bfd8: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625073]: Could not generate persistent MAC address for veth47bb496: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625074]: Could not generate persistent MAC address for veth598fc62: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625096]: Could not generate persistent MAC address for veth61bcfaf: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625093]: Could not generate persistent MAC address for veth0a59f16: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625084]: Could not generate persistent MAC address for vethabcf1b5: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625081]: Could not generate persistent MAC address for vetha87b282: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625164]: Could not generate persistent MAC address for veth4ca2589: No such file or directory Sep 19 12:07:19 sentry-docker00.cs.umd.edu systemd-udevd[3625167]: Could not generate persistent MAC address for veth8dea1b1: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634474]: link_config: could not get ethtool features for veth47bb496 Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634474]: Could not set offload features of veth47bb496: No such device Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634500]: Could not generate persistent MAC address for veth0c46389: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634499]: Could not generate persistent MAC address for vethe166aa3: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634509]: Could not generate persistent MAC address for vethafadc7d: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634500]: Could not generate persistent MAC address for veth930544e: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634517]: Could not generate persistent MAC address for veth139fd86: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634507]: Could not generate persistent MAC address for veth81d1920: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634530]: Could not generate persistent MAC address for veth4a44d2b: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634529]: Could not generate persistent MAC address for vethc1981ec: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634551]: Could not generate persistent MAC address for vethe09b565: No such file or directory Sep 19 12:27:27 sentry-docker00.cs.umd.edu systemd-udevd[3634559]: Could not generate persistent MAC address for veth388bd54: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643893]: link_config: could not get ethtool features for vethe09b565 Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643893]: Could not set offload features of vethe09b565: No such device Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643983]: Could not generate persistent MAC address for vethc366af0: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643984]: Could not generate persistent MAC address for veth6cde0cb: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643987]: Could not generate persistent MAC address for veth9acd0aa: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643983]: Could not generate persistent MAC address for veth6b92325: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3644000]: Could not generate persistent MAC address for veth75a1e1c: No such file or directory Sep 19 12:47:35 sentry-docker00.cs.umd.edu systemd-udevd[3643984]: Could not generate persistent MAC address for vethcebed5b: No such file or directory ... 4 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 12:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 12:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 12:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 12:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (4 distinct, 12 total) == Sep 19 12:12:42 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x9] Sep 19 12:15:07 submit26-b9-f1 kernel: show_signal_msg: 3 callbacks suppressed Sep 19 12:15:07 submit26-b9-f1 systemd-coredump[2491867]: Process 2491864 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2491864:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007fb2e0c2a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fb2e0c2a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 Sep 19 12:15:07 submit26-b9-f1 systemd-coredump[2491877]: Process 2491874 (grades) of user 1001 dumped core.#012#012Stack trace of thread 2491874:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007ff17702a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007ff17702a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f2 (4 distinct, 8 total) == Sep 19 12:05:05 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] Sep 19 12:55:09 submit26-b9-f2 kernel: show_signal_msg: 3 callbacks suppressed Sep 19 12:55:09 submit26-b9-f2 systemd-coredump[1611972]: Process 1611969 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1611969:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007fee2022a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007fee2022a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 Sep 19 12:55:09 submit26-b9-f2 systemd-coredump[1611983]: Process 1611979 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1611979:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f20db02a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f20db02a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f3 (3 distinct, 10 total) == Sep 19 12:10:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x8] Sep 19 12:35:08 submit26-b9-f3 systemd-coredump[1989943]: Process 1989940 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1989940:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f0fa042a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f0fa042a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 Sep 19 12:35:08 submit26-b9-f3 systemd-coredump[1989953]: Process 1989950 (grades) of user 1001 dumped core.#012#012Stack trace of thread 1989950:#012#0 0x0000000000401499 main (grades + 0x1499)#012#1 0x00007f34c922a610 __libc_start_call_main (libc.so.6 + 0x2a610)#012#2 0x00007f34c922a6c0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a6c0)#012#3 0x00000000004010b5 _start (grades + 0x10b5)#012ELF object binary architecture: AMD x86-64 == submit26-b9-f4 (1 distinct, 5 total) == Sep 19 12:20:43 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-fclone (9 distinct, 9 total) == Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from create access on the directory /(null). For complete SELinux messages run: sealert -l 9355d9d9-a311-48d2-bd37-6c0f6947dfff Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from add_name access on the directory /(null). For complete SELinux messages run: sealert -l cc4658d7-9db1-405d-9eee-de0ccee5857f Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from create access on the file /(null). For complete SELinux messages run: sealert -l 568a2429-0b1b-49df-af41-49b5cd298ae8 Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.cLjshq/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from setattr access on the file repomd.xml. For complete SELinux messages run: sealert -l 0d6b7b1f-ebe3-4beb-915a-b06b63bf2566 Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.cLjshq. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from remove_name access on the directory repomd.xml. For complete SELinux messages run: sealert -l 092e0644-8373-4017-b77f-1afa6c6da4ac Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from unlink access on the file repomd.xml. For complete SELinux messages run: sealert -l ce429a92-56de-4de1-b859-cbfb69ae123c Sep 19 12:21:56 submit26-b9-fclone setroubleshoot[119844]: SELinux is preventing /usr/bin/python3.9 from rmdir access on the directory repodata. For complete SELinux messages run: sealert -l 99b886eb-497b-406d-8206-afe76a1086b4