Il 29/07/2025 08:43, Steven Levine ha scritto:

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

Hi all,

i'm sorry for the copy and paste, i know that i will be troublesome
there are a lot of this stuff (hundreds of sockets) in this state,
maybe it's a sort of DDOS attack

      0 STREAM           42164        http..80 217.182.195.225  FIN_WAIT_2
      0 STREAM           56842      https..443    103.42.4.140  FIN_WAIT_2
      0 STREAM           18331        http..80   51.68.111.239  FIN_WAIT_2
      0 STREAM           62505        http..80  91.225.160.193  FIN_WAIT_2


massimo