Command: /usr/local/sbin/syslog-digest.py Time : 0.0522s Status : exited 0 Output : Syslog digest — 2026-09-19 21:05 EDT Processed 2,716 lines, filtered 2,213 (81%). 503 unknown (176 distinct) from 15 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 20:51:23 b0b02.cs.umd.edu rustdesk[3014699]: cannot open display: == bale (5 distinct, 92 total) == Sep 19 20:05:34 bale setroubleshoot[959961]: failed to retrieve rpm info for /dev/nvme0 [x40] Sep 19 20:05:35 bale setroubleshoot[959961]: 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 20:05:37 bale setroubleshoot[959961]: 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 20:05:40 bale setroubleshoot[959961]: 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 20:05:52 bale setroubleshoot[960575]: 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 [x16] == csfw00a (1 distinct, 125 total) == Sep 19 20:03:44 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x125] == idm00 (1 distinct, 1 total) == Sep 19 20:53:59 idm00 named[4166701]: client @0x7f11a9407128 10.73.240.42#55237: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 20:37:57 idmp0 named[1598691]: client @0x7f2d28029f68 10.73.240.43#64411: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 5 total) == Sep 19 20:08:26 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x5] == matrix (10 distinct, 14 total) == Sep 19 20:13:49 matrix sshd[2625570]: error: Refused by certificate options [x4] Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644723, but reception only permitted for main PID 720 Sep 19 20:45:28 matrix networkctl[2644887]: Interface "veth3fcb00b" not found. Sep 19 20:45:28 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644887, but reception only permitted for main PID 720 [x2] Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644967, but reception only permitted for main PID 720 Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2644972, but reception only permitted for main PID 720 Sep 19 20:45:29 matrix networkctl[2644984]: Interface "vethf9567cd" not found. Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645101, but reception only permitted for main PID 720 Sep 19 20:45:29 matrix systemd[1]: networkd-dispatcher.service: Got notification message from PID 2645280, but reception only permitted for main PID 720 Sep 19 20:45:44 matrix kernel: kauditd_printk_skb: 8 callbacks suppressed == newhonors2 (1 distinct, 24 total) == Sep 19 20:13:03 newhonors2 dhcpcd[2873832]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 19 20:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 298) *** Sep 19 20:05:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 6533/6533, ET: 22) *** Sep 19 20:05:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 298, QN: 48/48, ET: 22) *** Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 19 20:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 5692/5692, ET: 0) *** Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 299) *** Sep 19 20:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 299, QN: 54/54, ET: 0) *** Sep 19 20:08:03 ntop00 setroubleshoot[698381]: 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 20:08:03 ntop00 setroubleshoot[698381]: 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 20:08:03 ntop00 setroubleshoot[698381]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 20:08:03 ntop00 setroubleshoot[698381]: 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 20:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 19 20:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 300) *** Sep 19 20:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 5732/5732, ET: 20) *** Sep 19 20:10:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 300, QN: 50/50, ET: 20) *** Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 19 20:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 6174/6174, ET: 0) *** Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 301) *** Sep 19 20:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 301, QN: 54/54, ET: 0) *** Sep 19 20:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 19 20:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 302) *** Sep 19 20:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 5971/5971, ET: 22) *** Sep 19 20:15:23 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 302, QN: 53/53, ET: 22) *** Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 19 20:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 5645/5645, ET: 0) *** Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 303) *** Sep 19 20:18:02 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 303, QN: 39/39, ET: 0) *** Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** Sep 19 20:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 304) *** Sep 19 20:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 304, QN: 41/41, ET: 0) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 20:09:09 outbound00.cs.umd.edu python3[1806558]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 20:13:06 outbound01.cs.umd.edu python3[4065542]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: link_config: could not get ethtool features for vetha660928 Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852951]: Could not set offload features of vetha660928: No such device Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852985]: Could not generate persistent MAC address for veth1ef7a26: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852986]: Could not generate persistent MAC address for veth0531380: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852989]: Could not generate persistent MAC address for vethabe7f2c: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852997]: Could not generate persistent MAC address for vethf512cf0: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3852998]: Could not generate persistent MAC address for vethcaeb6e9: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853009]: Could not generate persistent MAC address for veth2a74ba5: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853015]: Could not generate persistent MAC address for vethee1e149: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853016]: Could not generate persistent MAC address for vethcc2b2cf: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853034]: Could not generate persistent MAC address for vethefe56f4: No such file or directory Sep 19 20:10:38 sentry-docker00.cs.umd.edu systemd-udevd[3853029]: Could not generate persistent MAC address for veth52eca01: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: link_config: could not get ethtool features for vethabe7f2c Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862351]: Could not set offload features of vethabe7f2c: No such device Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862401]: Could not generate persistent MAC address for veth50818d2: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862402]: Could not generate persistent MAC address for vethc951973: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862405]: Could not generate persistent MAC address for veth64b2976: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862406]: Could not generate persistent MAC address for veth8ba369b: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862416]: Could not generate persistent MAC address for vethf07cf1f: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862411]: Could not generate persistent MAC address for vethfe9221a: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862424]: Could not generate persistent MAC address for veth832e528: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862410]: Could not generate persistent MAC address for veth021e78d: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862487]: Could not generate persistent MAC address for vethc6622c9: No such file or directory Sep 19 20:30:46 sentry-docker00.cs.umd.edu systemd-udevd[3862490]: Could not generate persistent MAC address for veth9c6631c: No such file or directory Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: link_config: could not get ethtool features for vethc6622c9 Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871824]: Could not set offload features of vethc6622c9: No such device Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871846]: Could not generate persistent MAC address for vetha964c49: No such file or directory Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871847]: Could not generate persistent MAC address for veth622f661: No such file or directory Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871865]: Could not generate persistent MAC address for veth26f7273: No such file or directory Sep 19 20:50:55 sentry-docker00.cs.umd.edu systemd-udevd[3871852]: Could not generate persistent MAC address for vethd627946: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 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 19 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 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 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 19 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 19 20:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 20:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f3 (1 distinct, 1 total) == Sep 19 20:44:38 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL == submit26-b9-fclone (9 distinct, 9 total) == Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.tVmNgA/repodata/repomd.xml. For complete SELinux messages run: sealert -l 03e2f521-0e7c-481f-8e92-0602c6adeedc Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:57 submit26-b9-fclone setroubleshoot[139273]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.tVmNgA. For complete SELinux messages run: sealert -l 887adbf9-2bb9-4009-b800-36ddf9ba0db5 Sep 19 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:57 submit26-b9-fclone setroubleshoot[139273]: 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 20:21:58 submit26-b9-fclone setroubleshoot[139273]: 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