Command: /usr/local/sbin/syslog-digest.py Time : 0.0499s Status : exited 0 Output : Syslog digest — 2026-09-20 18:05 EDT Processed 1,962 lines, filtered 1,438 (73%). 524 unknown (181 distinct) from 18 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 20 17:52:41 b0b02.cs.umd.edu rustdesk[3336434]: cannot open display: == bale (5 distinct, 84 total) == Sep 20 17:06:06 bale setroubleshoot[1229553]: failed to retrieve rpm info for /dev/nvme0 [x36] Sep 20 17:06:07 bale setroubleshoot[1229553]: 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 17:06:09 bale setroubleshoot[1229553]: 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 17:06:12 bale setroubleshoot[1229553]: 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 17:06:24 bale setroubleshoot[1230167]: 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] == csfw00a (1 distinct, 140 total) == Sep 20 17:04:35 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x140] == frozone (1 distinct, 1 total) == Sep 20 17:35:39 frozone systemd-tmpfiles[2206449]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == idm00 (1 distinct, 1 total) == Sep 20 17:54:00 idm00 named[4166701]: client @0x7f11a4068068 10.73.240.42#49378: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 20 17:37:56 idmp0 named[1598691]: client @0x7f2d3c07c928 10.73.240.43#50618: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 1 total) == Sep 20 18:03:31 itmon02 sshd[1750555]: error: beginning MaxStartups throttling == newhonors2 (1 distinct, 24 total) == Sep 20 17:13:02 newhonors2 dhcpcd[2913662]: dhcpcd is not running [x24] == ntop00 (101 distinct, 141 total) == Sep 20 17:05:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 226) *** Sep 20 17:05:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 226) *** Sep 20 17:05:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 11927/11927, ET: 51) *** Sep 20 17:05:52 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 74/74, ET: 51) *** Sep 20 17:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 20 17:08:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 12143/12143, ET: 0) *** Sep 20 17:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 20 17:08:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 72/72, ET: 0) *** Sep 20 17:08:02 ntop00 setroubleshoot[865600]: 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 [x11] Sep 20 17:08:02 ntop00 setroubleshoot[865600]: 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 [x11] Sep 20 17:08:02 ntop00 setroubleshoot[865600]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x11] Sep 20 17:08:02 ntop00 setroubleshoot[865600]: 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 [x11] Sep 20 17:10:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 20 17:10:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 20 17:10:49 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 11767/11767, ET: 48) *** Sep 20 17:10:49 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 47/47, ET: 48) *** Sep 20 17:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 20 17:13:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 11757/11757, ET: 0) *** Sep 20 17:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 20 17:13:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 49/49, ET: 0) *** Sep 20 17:15:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 20 17:15:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 20 17:15:52 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 11952/11952, ET: 51) *** Sep 20 17:15:52 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 62/62, ET: 51) *** Sep 20 17:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 20 17:18:01 ntop00 sfacctd[791587]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 12029/12029, ET: 0) *** Sep 20 17:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 20 17:18:01 ntop00 nfacctd[791663]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 62/62, ET: 0) *** Sep 20 17:20:01 ntop00 sfacctd[791587]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** Sep 20 17:20:01 ntop00 nfacctd[791663]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** ... 71 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 20 17:09:09 outbound00.cs.umd.edu python3[2103360]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 20 17:13:06 outbound01.cs.umd.edu python3[169305]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258053]: Could not generate persistent MAC address for veth83289bb: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258054]: Could not generate persistent MAC address for veth0af6606: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258072]: Could not generate persistent MAC address for vethbcdaf39: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258070]: Could not generate persistent MAC address for vethc467ff4: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258108]: Could not generate persistent MAC address for veth766fca5: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258109]: Could not generate persistent MAC address for veth9a1e06c: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258141]: Could not generate persistent MAC address for veth1cfdf82: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258143]: Could not generate persistent MAC address for veth81f0001: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258167]: Could not generate persistent MAC address for vethf656d72: No such file or directory Sep 20 17:19:22 sentry-docker00.cs.umd.edu systemd-udevd[258171]: Could not generate persistent MAC address for vethbe55c8f: No such file or directory Sep 20 17:39:30 sentry-docker00.cs.umd.edu systemd-udevd[267644]: link_config: could not set ethtool features for veth766fca5 Sep 20 17:39:30 sentry-docker00.cs.umd.edu systemd-udevd[267644]: Could not set offload features of veth766fca5: Operation not permitted Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267713]: Could not generate persistent MAC address for veth83cfe9b: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267714]: Could not generate persistent MAC address for vethdc13dbd: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267717]: Could not generate persistent MAC address for veth6fa9d19: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267718]: Could not generate persistent MAC address for veth813b151: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267723]: Could not generate persistent MAC address for veth533af8e: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267737]: Could not generate persistent MAC address for vetha4578e6: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267723]: Could not generate persistent MAC address for veth9010f4f: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267737]: Could not generate persistent MAC address for veth3606fba: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267747]: Could not generate persistent MAC address for vetheea3c8f: No such file or directory Sep 20 17:39:31 sentry-docker00.cs.umd.edu systemd-udevd[267751]: Could not generate persistent MAC address for veth0ad7074: No such file or directory Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277132]: link_config: could not get ethtool features for veth83cfe9b Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277132]: Could not set offload features of veth83cfe9b: No such device Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277134]: link_config: could not get ethtool features for veth9010f4f Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277134]: Could not set offload features of veth9010f4f: No such device Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277164]: Could not generate persistent MAC address for vethf4ccda9: No such file or directory Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277163]: Could not generate persistent MAC address for vetha25fc31: No such file or directory Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277167]: Could not generate persistent MAC address for veth8939bc7: No such file or directory Sep 20 17:59:39 sentry-docker00.cs.umd.edu systemd-udevd[277189]: Could not generate persistent MAC address for veth2cb00ed: No such file or directory ... 6 more distinct messages not shown == soul (1 distinct, 1 total) == Sep 20 17:47:11 soul sshd-session[3807952]: fatal: userauth_pubkey: parse publickey packet: incomplete message [preauth] == strawberry (7 distinct, 38 total) == Sep 20 17: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 17: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 17:07:03 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 20 17: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 17: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 17:07:03 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 20 17:34:42 strawberry smartd[5314]: Device: /dev/sda [SAT], failed to read SMART Attribute Data [x2] == submit26-b9-f1 (1 distinct, 4 total) == Sep 20 17:08:07 submit26-b9-f1 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x4] == submit26-b9-f2 (1 distinct, 5 total) == Sep 20 17:12:44 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (10 distinct, 19 total) == Sep 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 [x2] Sep 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.2Re9mh/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f [x2] Sep 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 [x2] Sep 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.2Re9mh. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 20 17:06:43 submit26-b9-f3 setroubleshoot[2136880]: 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 20 17:09:19 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x7] == submit26-b9-f4 (10 distinct, 15 total) == Sep 20 17:13:12 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 [x2] Sep 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.HQWvAe/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 [x2] Sep 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 [x2] Sep 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.HQWvAe. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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 20 17:24:47 submit26-b9-f4 setroubleshoot[1530652]: 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