SystemAdmin 0 Posted August 2, 2023 Share Posted August 2, 2023 This is happening on a lot of CentOS hosts. Aug 1 01:20:13 hostname kernel: eset_rtp: wait for scanner reply timeout, path: /run/crond.pid, event: CLOSE, id: 6716447 pid: 29742 Aug 1 01:20:13 hostname kernel: eset_rtp: wait for scanner reply timeout, path: /run/crond.pid, event: CLOSE, id: 6716447 pid: 29742 Aug 1 01:20:13 hostname kernel: eset_rtp: wait for scanner reply timeout, path: /run/crond.pid, event: CLOSE, id: 6716447 pid: 29742 There is no correlation with these events and any high resource usage on our system. When these are visible on the console, we can not ssh into the system and are forced to reboot the node. Is there anyone else that has seen this type of event on their systems? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,081 Posted August 3, 2023 Administrators Share Posted August 3, 2023 Please raise a support ticket and provide logs collected as per https://help.eset.com/essl/10.0/en-US/collect_logs.html. Link to comment Share on other sites More sharing options...
Recommended Posts