Why apache creates many processes, which ultimately drops the system?
All kind time of day.
There is a web server zabbix 3.0 on a virtual machine running Debian 3.2.0-4-amd64 (vmware 12 cores 8 GB operatives). On it:
NGINX - frontend, Apache backend, php5. Mysql on another physical machine
The load on the servo is large enough. In Zabbix a huge variety of cards with thousands of elements (I think the main problem is in them). Users can work simultaneously in the region of 100.
The situation is the following. Recently the web server began to slow down. Multiply the process "/usr/sbin/apache-k start". Constantly. Regardless of the time of day and accordingly the load on the server.
They breed to the point until you run out of memory and the server stops responding.
Rabotaem Apache - all works perfectly and smartly. Services begin to multiply, but still quickly and working smartly. After 10 minutes of services is 25 percent loaded 100% (all cores at 100), but still the web responds quite quickly.
It takes 20 minutes of services are already 40 pieces, but we do not care, everything is cool
Is 30 minutes of services are already 60 pieces, we still suffer, memory eats up 5-6 gigs, but start delay.
Is 50 minutes, and services like 80, we're breaking up and feeling the actual brakes sent Apache to reboot.
Then all in a circle. No matter what time in the working or in the dead of night. Within hours the server dies.
In apache2 error.log starts to complain only when memory overflows and serv can't spawn processes. In other logs as well, like pure.
I'm tired of this fight already. Asking for tips in the style of "reinstall Windows" does not give. It will be the most extreme stage, yet it is important to find the root of evil, not to cut down the whole forest.
I want to also add that before was just nginx + php5-fpm and the situation was exactly the same, just plagerise the process php5-fpm. (it was worse, because when you load 100% all cores to work was not possible and in the current situation, the fertility processes at the operating speed has almost no effect, until they devour the entire memory).
I will say the main sentence: "previously, everything worked perfectly for several months. any settings I have not changed and it is itself"
1. the number of processes which is permissible is described in the config of Apache (worker look) same thing applies to php-fpm, can not open the config and specify the maximum number of handlers.
2. sabix update comes with a variety of devices may be worth them less frequently send and look at the configs of sabika and settings collection updates ? corny because it may send too much data which he is unable to process and then the decision or reduce the amount of data, or to scale the server (vertically or horizontally)