Agent to server communication fails because maximum number of LDAP connections reached
Last Modified: 2023-08-07 06:51:04 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
Agent to server communication fails because maximum number of LDAP connections reached
Technical Articles ID:
KB93201
Last Modified: 2023-08-07 06:51:04 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10.x, 5.9.x
Problem 1
Agent to server communications fail. The masvc(3360.7164) ahclient.Info: Network library rc = <1008>, Agent handler reports response code <503>. masvc(3360.7164) ahclient.Info: Agent handler reports server busy. response code 503. masvc(3360.7164) ahclient.Info: Spipe connection response received, network return code = 1008, response code 503. masvc(3360.7164) property.Info: Published property collect and send status message masvc(3360.7164) ahclient.Info: Agent communication session closed Problem 2
One of the following errors is logged in the (Conn,OU=DistributionGroups,OU=Domino,DC=us,DC=bank-dns,DC=com))', Error string='Filter Error' OR Cause
Multiple registered Lightweight Directory Access Protocol (LDAP) servers have been configured. The multiple registered LDAP servers cause the maximum number of connections to the Apache service to be reached. One of the following conditions applies:
Solution 1Multiple registered LDAP servers
Remove the redundant LDAP registered servers, and retain only the one registered LDAP server.
Solution 2One registered LDAP server
To reduce the load on LDAP requests from
For more information about Database MIrroring, see KB84683 - Explanation of how the ePolicy Orchestrator database mirroring feature works. Affected ProductsLanguages:This article is available in the following languages: |
|