Pabs 0 Posted October 6, 2021 Share Posted October 6, 2021 Hello, I have ESET Server Security installed on my Windows Server 2019 Datacenter VM's in Azure. For all of my VM's, the ERA Agent trace.log file shows repeated (a lot) of errors for failed health checks to a particular endpoint. I'll leave one such message below for reference. I'd like to figure out why this is occurring. Our servers only allow TLS 1.2 server protocols, and TLS 1.0,1.1, and 1.2 client protocols. 2021-10-06 13:14:26 Error: CReplicationModule [Thread 1828]: CAgentReplicationManager: HealthCheck failed with grpc error to (2tjwO_SOMETHINGLIKETHIS.a.ecaserver.eset.com) with error: Request: Era.Common.Services.HealthCheck.ServerHealthcheckRequest on connection: host: "2tjwO_SOMETHINGLIKETHIS.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Endpoint read failed, and error details: Link to comment Share on other sites More sharing options...
Pabs 0 Posted October 6, 2021 Author Share Posted October 6, 2021 additional info: I am investigating issues with my servers which are causing network outages. One line of thinking I am investigating is that somehow over a period of long uptime, the VM's are exhausting all sockets and then can't establish further connections. Either way, if this isn't related to that issue I still want to figure out what the heck this error is. Link to comment Share on other sites More sharing options...
Pabs 0 Posted October 7, 2021 Author Share Posted October 7, 2021 I have verified that the virtual machine can reach the endpoint specified in the error over port 443 via telnet, would appreciate any insight to why we are getting this error! Link to comment Share on other sites More sharing options...
Pabs 0 Posted October 12, 2021 Author Share Posted October 12, 2021 Anybody out there? 😓 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted October 12, 2021 Administrators Share Posted October 12, 2021 I would recommend raising a support ticket with your local ESET support and providing both agent logs trace.log and status.html as well as logs collected with ESET Log Collector from the machine. Link to comment Share on other sites More sharing options...
Pabs 0 Posted October 17, 2021 Author Share Posted October 17, 2021 (edited) Ok I will do that. There seems to be an issue in the era agent which is causing port exhaustion issues with my production VM's @Marcos I had the issue occur again today, was able to establish serial console access to one of my VM's only to see with a netstat command that the ERA agent had established thousands and thousands of connections. The list was endless. Edit: For now I've uninstalled and reinstalled the ESET Server Security and Remote Management Agent products to see if that helps cure the problem. Edited October 17, 2021 by Pabs Link to comment Share on other sites More sharing options...
Recommended Posts