Server is too busy (245 connections) to process request

Technical Articles ID: KB80060
Last Modified: 2023-07-12 10:14:25 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.x

Problem

When Apache reaches 245 simultaneous connections, subsequent McAfee Agents (MAs) that try to reach ePO during their scheduled agent-server communication intermittently fail. The attempts continue until existing connections are released.

The Server.log file records errors when the problem occurs:

Processing epo request, session ID=2577, memory load 15 percent...
E #06460 mod_epo Server is too busy (245 connections) to process request

Cause

ePO uses an Apache server (ePO Server service) to handle communications with MAs installed on endpoints. The Apache server has a limitation of 245 simultaneous connections. This connection limit can be reached depending on the ePO configuration and environment size (node count).

The following scenarios can contribute to the max connections being reached:

Product Deployment tasks configured to run more than once
Using Run Client Task Now on a large group of systems (more than 245)
Configuring a small agent-server communication interval (ASCI) for a larger environment

Agents request files from the server at their scheduled interval, and anytime a scheduled task invokes. This event can cause incoming connections to quickly reach the cap, especially if the environment consists of many systems.

Solution 1

You must configure Product Deployment tasks to run on a set schedule. The set schedule must distribute the workload evenly across the day.

Avoid using Run Client Task Now on a large group of systems (more than 245). This task uses the Data Channel to establish near immediate communication and can lead to max connections.

See the ePolicy Orchestrator 5.9 Product Guide for information about the following:

Best practices when scheduling Product Deployment tasks.
How to add another Distributed Repository in the environment to distribute the incoming download requests. Consider this option if you want to configure Product Deployment client tasks to run more than once a day.

For product documents, go to the Product Documentation portal.

Solution 2

You must increase the ASCI.

The policy defaults to once an hour. If you're managing a larger environment (more than 5000) or using many Trellix products, consider increasing the interval to two or more hours.

See the relevant ePolicy Orchestrator Product Guide for information about the following:

Best practices when configuring the ASCI.
How to add another Agent Handler, which acts as a load balancer in the environment. Consider this option if you want to reduce the ASCI by evenly distributing the incoming connections.

For product documents, go to the Product Documentation portal.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Server is too busy (245 connections) to process request

Environment

Problem

Cause

Solution 1

Solution 2

Affected Products

Languages:

Title

Title

Knowledge Center

Server is too busy (245 connections) to process request

Environment

Problem

Cause

Solution 1

Solution 2

Affected Products

Languages:

Choose your region

Title

Title