Mohsen Ghaffari 0 Posted February 24, 2022 Share Posted February 24, 2022 Dear ESET Support, We have been getting the Error "Can't connect to ESET Inspect Server" sporadically a couple times sofar on a number of clients. The issue would be resolved with a restart. However sometimes the number of clients exceed 600Pcs and any manual restart attempt would not be feasible. We have checked our ESET Apache proxies in terms of resources and they are well below 50% usage. Also apache threadlimits are tweaked to accomodate the number of clients we have (8000 limit for 2500 clients). Any help is appreciated. updating to 1.6.1766.0 has not helped sofar. Thank you. Link to comment Share on other sites More sharing options...
Mohsen Ghaffari 0 Posted February 24, 2022 Author Share Posted February 24, 2022 Following log entry on an affected client: Events cannot be sent to x.x.x.x:8093. Server responded with 503 status code in 0s033ms. Link to comment Share on other sites More sharing options...
Mitchell 13 Posted February 24, 2022 Share Posted February 24, 2022 When these errors occur, do you see a spike in "event packet queue" in the EEI Server status dashboard? If it is constantly maxing out at 500+ EEI Server is most likely not able to handle the incomming events fast enough. (Database related or disk performance not sufficient) Link to comment Share on other sites More sharing options...
Mohsen Ghaffari 0 Posted February 24, 2022 Author Share Posted February 24, 2022 Thanks for the hint. It's maxing out at 500+. I'll investigate the issue and reach back to you. The SQL server sizing has been confirmed and validated during the POC by ESET. Link to comment Share on other sites More sharing options...
Recommended Posts