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?
