Command: /usr/local/sbin/syslog-digest.py Time : 0.0519s Status : exited 0 Output : Syslog digest — 2026-09-20 21:05 EDT Processed 2,019 lines, filtered 1,470 (72%). 549 unknown (175 distinct) from 19 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 20:52:52 b0b02.cs.umd.edu rustdesk[3382164]: cannot open display: == bale (5 distinct, 84 total) == Sep 20 20:05:57 bale setroubleshoot[1267865]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 20 20:05:57 bale setroubleshoot[1267865]: 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 20 20:06:00 bale setroubleshoot[1267865]: 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 20 20:06:03 bale setroubleshoot[1267865]: 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 20 20:06:15 bale setroubleshoot[1268479]: 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] == cheezit.cs.umd.edu (2 distinct, 2 total) == Sep 20 20:18:54 cheezit.cs.umd.edu sshd-session[1345854]: pam_access(sshd:auth): access denied for user `lin' from `74.96.151.253' Sep 20 21:02:47 cheezit.cs.umd.edu sshd-session[1356825]: pam_access(sshd:auth): access denied for user `asriniv1' from `108.40.120.8' == csfw00a (1 distinct, 149 total) == Sep 20 20:04:04 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x149] == idm00 (1 distinct, 1 total) == Sep 20 20:54:00 idm00 named[4166701]: client @0x7f11a4059f88 10.73.240.42#62494: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 20:37:56 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#58975: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 2 total) == Sep 20 20:43:35 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x2] == munin (2 distinct, 32 total) == Sep 20 20:13:45 munin sudo[964348]: pam_systemd(sudo:session): Failed to stat() runtime directory '/run/user/0': No such file or directory [x16] Sep 20 20:13:45 munin sudo[964348]: pam_systemd(sudo:session): Not setting $XDG_RUNTIME_DIR, as the directory is not in order. [x16] == newhonors2 (1 distinct, 24 total) == Sep 20 20:13:03 newhonors2 dhcpcd[2919213]: dhcpcd is not running [x24] == ntop00 (102 distinct, 146 total) == Sep 20 20:05:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) *** Sep 20 20:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) *** Sep 20 20:05:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 5717/5717, ET: 23) *** Sep 20 20:05:24 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 57/57, ET: 23) *** Sep 20 20:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 20 20:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 5775/5775, ET: 0) *** Sep 20 20:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 20 20:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 54/54, ET: 0) *** Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from append access on the file sflow.json. For complete SELinux messages run: sealert -l aec09a24-8fd6-4c2f-ba24-2e4b38b93f4c [x12] Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from write access on the file sflow.json. For complete SELinux messages run: sealert -l b2869c09-acbd-427c-b7c9-edae08c37a0e [x12] Sep 20 20:08:02 ntop00 setroubleshoot[889408]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 20 20:08:02 ntop00 setroubleshoot[889408]: SELinux is preventing /usr/local/sbin/sfacctd from lock access on the file /srv/pmacct/sflow.json. For complete SELinux messages run: sealert -l dbd70a69-3ee5-4fce-87ea-309297754109 [x12] Sep 20 20:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 20 20:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 20 20:10:25 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 6000/6000, ET: 24) *** Sep 20 20:10:25 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 58/58, ET: 24) *** Sep 20 20:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 20 20:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 5891/5891, ET: 0) *** Sep 20 20:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 20 20:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 69/69, ET: 0) *** Sep 20 20:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 20 20:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 20 20:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 62/62, ET: 0) *** Sep 20 20:15:24 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 5744/5744, ET: 23) *** Sep 20 20:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 20 20:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 5696/5696, ET: 0) *** Sep 20 20:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 20 20:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 58/58, ET: 0) *** Sep 20 20:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** Sep 20 20:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** ... 72 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 20:09:09 outbound00.cs.umd.edu python3[2145387]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 20:13:06 outbound01.cs.umd.edu python3[211448]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343376]: link_config: could not get ethtool features for veth6879fff Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343376]: Could not set offload features of veth6879fff: No such device Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343410]: Could not generate persistent MAC address for vethae3a394: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343411]: Could not generate persistent MAC address for veth8a087b1: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343414]: Could not generate persistent MAC address for vethc832288: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343431]: Could not generate persistent MAC address for veth3fbccc5: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343436]: Could not generate persistent MAC address for veth1b26cb4: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343433]: Could not generate persistent MAC address for veth327eb02: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343427]: Could not generate persistent MAC address for veth1c84c4e: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343425]: Could not generate persistent MAC address for vethf08f76d: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343427]: Could not generate persistent MAC address for vethe26db3e: No such file or directory Sep 20 20:20:37 sentry-docker00.cs.umd.edu systemd-udevd[343431]: Could not generate persistent MAC address for veth74fde09: No such file or directory Sep 20 20:40:45 sentry-docker00.cs.umd.edu systemd-udevd[352732]: link_config: could not get ethtool features for vethc832288 Sep 20 20:40:45 sentry-docker00.cs.umd.edu systemd-udevd[352732]: Could not set offload features of vethc832288: No such device Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352761]: Could not generate persistent MAC address for vethe20f63b: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352762]: Could not generate persistent MAC address for veth0d0bf39: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352765]: Could not generate persistent MAC address for veth95df242: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352766]: Could not generate persistent MAC address for veth94e8c3f: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352789]: Could not generate persistent MAC address for vethcbb4577: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352790]: Could not generate persistent MAC address for veth8038274: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352814]: Could not generate persistent MAC address for veth8ca72c6: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352799]: Could not generate persistent MAC address for veth8d944af: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352800]: Could not generate persistent MAC address for veth171eac8: No such file or directory Sep 20 20:40:46 sentry-docker00.cs.umd.edu systemd-udevd[352799]: Could not generate persistent MAC address for veth49a6517: No such file or directory Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362109]: link_config: could not get ethtool features for vethcbb4577 Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362109]: Could not set offload features of vethcbb4577: No such device Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362142]: Could not generate persistent MAC address for vethf2fb91e: No such file or directory Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362143]: Could not generate persistent MAC address for veth3a8c089: No such file or directory Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362146]: Could not generate persistent MAC address for veth740b9d8: No such file or directory Sep 20 21:00:54 sentry-docker00.cs.umd.edu systemd-udevd[362147]: Could not generate persistent MAC address for vetha7f69a5: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 20 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 20:07:03 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 20 20:07:03 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 20 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 2 total) == Sep 20 20:34:32 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-f2 (1 distinct, 4 total) == Sep 20 20:08:51 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f3 (1 distinct, 4 total) == Sep 20 20:18:05 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f4 (1 distinct, 2 total) == Sep 20 20:33:10 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x2] == submit26-b9-fclone (9 distinct, 9 total) == Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.QimYga/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.QimYga. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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 20 20:21:57 submit26-b9-fclone setroubleshoot[197699]: 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