In <list-13711501@2rosenthals.com>, on 07/29/25
    at 10:15 AM, "Peter Moylan" <ecs-isp@2rosenthals.com> said:

Hi all,

Just because Apache was the one to report the problem, that doesn't mean
that Apache caused the socket starvation. You have to use Lewis's
approach of closing one application at a time, to see which "close"
fixed the problem.

Agreed.

Another useful took for tracking down the source of this kind of issue is

   netstat -s

There's often enough information in the port numbers to track down the
offending application.

Steven