Apache started to stop and then I can’t log in to the server via ssh the first time - it hangs terribly. Only reboot helps. I went to whm to see the apache status and this is what I saw there: enter image description here

Workflows are really a couple of pieces, but there are 60-70 pieces of such "Waiting for Connection" and they do not go away. Requests are sent by Ajax, and on the page I see that the answer has turned and everything is fine, but why do not they leave Apache’s tasks? Please help in which direction to look?

  • If the question is in the number of Apache processes, then this is normal behavior. If you don’t like the number of Apache processes and want to reduce it, look towards the StartServers, MinSpareServers, MaxSpareServers directives. But in order to rule them - you need to really understand why and how. And not the fact that the server "hangs" because of this. On your screenshot it is not visible to the Apache loaded system. - de_frag
  • And that is, that the processes hang for a long time while waiting for the connection is this normal? It’s just that some of these processes have the SS indicator reaching 1960-2000 - although again, if you look at the Chrome console, then the ajax request has long returned with the status 200. That is what confuses me .. - Igor
  • Apache working through prefork always has a certain number of processes waiting to be connected. The regulation of the “generation” and “destruction” of these processes is handled by the internal mechanism of Apache, and is based on the values ​​of the Apache config directives. Therefore, so far I do not see anything criminal. - de_frag

0