Command: /usr/local/sbin/syslog-digest.py Time : 0.0535s Status : exited 0 Output : Syslog digest — 2026-09-19 18:05 EDT Processed 2,788 lines, filtered 2,268 (81%). 520 unknown (179 distinct) from 17 host(s). == b0b02.cs.umd.edu (1 distinct, 1 total) == Sep 19 17:51:14 b0b02.cs.umd.edu rustdesk[2968958]: cannot open display: == bale (5 distinct, 89 total) == Sep 19 17:06:07 bale setroubleshoot[921607]: failed to retrieve rpm info for /dev/nvme0 [x38] Sep 19 17:06:07 bale setroubleshoot[921607]: 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 [x13] Sep 19 17:06:10 bale setroubleshoot[921607]: SELinux is preventing smartctl from read access on the chr_file nvme0. For complete SELinux messages run: sealert -l fc305ce6-663c-4aa2-8640-0ee0f8dce1a9 [x13] Sep 19 17:06:13 bale setroubleshoot[921607]: 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 [x11] Sep 19 17:06:25 bale setroubleshoot[922223]: 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 [x14] == csfw00a (1 distinct, 133 total) == Sep 19 17:04:08 csfw00a kernel: bnxt_en 0000:09:00.0 eth3: NIC Link is Down [x133] == frozone (1 distinct, 1 total) == Sep 19 17:35:38 frozone systemd-tmpfiles[2107225]: Failed to remove "/var/tmp/test.log", ignoring: Operation not permitted == idm00 (1 distinct, 1 total) == Sep 19 17:53:58 idm00 named[4166701]: client @0x7f11a93cbc38 10.73.240.42#65160: update '73.10.in-addr.arpa/IN' denied == idmp0 (1 distinct, 1 total) == Sep 19 17:37:56 idmp0 named[1598691]: client @0x7f2d24019b88 10.73.240.43#53179: update '73.10.in-addr.arpa/IN' denied == itmon02 (1 distinct, 3 total) == Sep 19 17:38:08 itmon02 sshd[1750555]: error: beginning MaxStartups throttling [x3] == newhonors2 (1 distinct, 24 total) == Sep 19 17:13:03 newhonors2 dhcpcd[2868272]: dhcpcd is not running [x24] == ntop00 (100 distinct, 144 total) == Sep 19 17:05:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 226) *** Sep 19 17:05:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 6001/6001, ET: 20) *** Sep 19 17:05:21 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 226, QN: 73/73, ET: 20) *** Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 19 17:08:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 6109/6109, ET: 0) *** Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 227) *** Sep 19 17:08:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 227, QN: 67/67, ET: 0) *** Sep 19 17:08:02 ntop00 setroubleshoot[674562]: 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 17:08:02 ntop00 setroubleshoot[674562]: 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 17:08:02 ntop00 setroubleshoot[674562]: failed to retrieve rpm info for path '/srv/pmacct/sflow.json': [x12] Sep 19 17:08:02 ntop00 setroubleshoot[674562]: 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 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 19 17:10:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 228) *** Sep 19 17:10:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 65/65, ET: 0) *** Sep 19 17:10:21 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 228, QN: 5973/5973, ET: 20) *** Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 19 17:13:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 6089/6089, ET: 0) *** Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 229) *** Sep 19 17:13:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 229, QN: 60/60, ET: 0) *** Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 19 17:15:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 230) *** Sep 19 17:15:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 49/49, ET: 0) *** Sep 19 17:15:23 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - END (PID: 230, QN: 6390/6390, ET: 22) *** Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - START (PID: 231) *** Sep 19 17:18:01 ntop00 nfacctd[600666]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 57/57, ET: 0) *** Sep 19 17:18:01 ntop00 sfacctd[600603]: INFO ( p1/print ): *** Purging cache - END (PID: 231, QN: 6228/6228, ET: 0) *** Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** Sep 19 17:20:01 ntop00 sfacctd[600603]: INFO ( m1/mysql ): *** Purging cache - START (PID: 232) *** Sep 19 17:20:01 ntop00 nfacctd[600666]: INFO ( m1/mysql ): *** Purging cache - END (PID: 232, QN: 51/51, ET: 0) *** ... 70 more distinct messages not shown == outbound00.cs.umd.edu (1 distinct, 6 total) == Sep 19 17:09:09 outbound00.cs.umd.edu python3[1764603]: ldapdb [x6] == outbound01.cs.umd.edu (1 distinct, 6 total) == Sep 19 17:13:07 outbound01.cs.umd.edu python3[4023465]: ldapdb [x6] == sentry-docker00.cs.umd.edu (36 distinct, 36 total) == Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: link_config: could not get ethtool features for vethbdd6d47 Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767523]: Could not set offload features of vethbdd6d47: No such device Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767569]: Could not generate persistent MAC address for veth7edc101: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767570]: Could not generate persistent MAC address for vethe43aa76: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767573]: Could not generate persistent MAC address for veth93a15e1: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767574]: Could not generate persistent MAC address for veth930beff: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767597]: Could not generate persistent MAC address for veth704f1a2: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767598]: Could not generate persistent MAC address for vethde2c127: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767623]: Could not generate persistent MAC address for vethf756fc7: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767624]: Could not generate persistent MAC address for veth92101ae: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767642]: Could not generate persistent MAC address for veth46ab34f: No such file or directory Sep 19 17:09:23 sentry-docker00.cs.umd.edu systemd-udevd[3767627]: Could not generate persistent MAC address for veth2413952: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: link_config: could not set ethtool features for veth93a15e1 Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777207]: Could not set offload features of veth93a15e1: Operation not permitted Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777236]: Could not generate persistent MAC address for veth882bb97: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777237]: Could not generate persistent MAC address for veth9324a28: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777240]: Could not generate persistent MAC address for veth3ea44f0: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777241]: Could not generate persistent MAC address for vethd2e57e4: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777264]: Could not generate persistent MAC address for vethaaae73e: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777265]: Could not generate persistent MAC address for vethe096ac7: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for veth55cbef3: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth7014535: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777274]: Could not generate persistent MAC address for vethd3f3f7d: No such file or directory Sep 19 17:29:31 sentry-docker00.cs.umd.edu systemd-udevd[3777280]: Could not generate persistent MAC address for veth00e543d: No such file or directory Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: link_config: could not get ethtool features for vethd3f3f7d Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786632]: Could not set offload features of vethd3f3f7d: No such device Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786669]: Could not generate persistent MAC address for vethed42401: No such file or directory Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786670]: Could not generate persistent MAC address for vethc20fa18: No such file or directory Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786695]: Could not generate persistent MAC address for vethf5b5d57: No such file or directory Sep 19 17:49:40 sentry-docker00.cs.umd.edu systemd-udevd[3786696]: Could not generate persistent MAC address for veth9404756: No such file or directory ... 6 more distinct messages not shown == strawberry (7 distinct, 38 total) == Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 206848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda2, logical block 0, async page read [x6] Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [x6] Sep 19 17:07:04 strawberry kernel: I/O error, dev sda, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [x6] Sep 19 17:07:04 strawberry kernel: Buffer I/O error on dev sda1, logical block 0, async page read [x6] Sep 19 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 19 17:06:54 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 19 17:18:07 submit26-b9-f2 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f3 (10 distinct, 14 total) == Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.NmGr6G/repodata/repomd.xml. For complete SELinux messages run: sealert -l 27f29d48-5e7c-4db7-b051-8ac055737d6f Sep 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:42 submit26-b9-f3 setroubleshoot[2019594]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.NmGr6G. For complete SELinux messages run: sealert -l 9638d396-8ce5-4e6a-ae47-45cd3985e1cd Sep 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:06:43 submit26-b9-f3 setroubleshoot[2019594]: 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 19 17:14:33 submit26-b9-f3 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x5] == submit26-b9-f4 (10 distinct, 14 total) == Sep 19 17:11:00 submit26-b9-f4 systemd[1]: user@1001.service: Main process exited, code=killed, status=9/KILL [x3] Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 [x2] Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 [x2] Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from open access on the file /tmp/libdnf.GE5aXs/repodata/repomd.xml. For complete SELinux messages run: sealert -l 9f8f24a0-8fb6-454d-a103-31a8f7a6efa0 Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: SELinux is preventing /usr/bin/python3.9 from read access on the directory libdnf.GE5aXs. For complete SELinux messages run: sealert -l 25f86b49-4ee7-4f60-ad1c-73a70032560c Sep 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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 19 17:24:46 submit26-b9-f4 setroubleshoot[1452752]: 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