502 bad gateway and server reached pm.max_children

lobokn 2021-02-26 14:45:31 UTC #1

Hi,
we have Egroupware 20.1.20210125 . Everything works fine, until today. Suddenly got this error when trying to login. Temporarily helps restart of egroupware container. But within 1 or 2 hours error appears again. In egroupware container logs I can see these warnings before it crashes.

[26-Feb-2021 13:33:39] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 9 idle, and 75 total children

[26-Feb-2021 13:33:40] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 8 idle, and 76 total children

[26-Feb-2021 13:33:44] WARNING: [pool www] server reached pm.max_children setting (80), consider raising it

Your help would be much appreciated

Regards

Luboš

RalfBecker 2021-02-26 15:07:09 UTC #2

You can extract the config-files affecting these values and set different ones:

cd /etc/egroupware-docker
docker cp egroupware:/etc/php/7.3/fpm/pool.d/www.conf .
vi www.conf # make your changes
vi docker-compose.override.yml
# add the following (careful to keep the hierarchy and indention with space!) 
services:
  egroupware:
    volumes:
    - ./www.conf:/etc/php/7.3/fpm/pool.d/www.conf
# rebuild the container
docker-compose up -d

That way our automatic updated keep working, and you have your own config.

Ralf

lobokn 2021-02-26 15:30:03 UTC #3

Thanks Ralf for your quick reply. I will try and I will see. I just wonder why this starts heappen right today. I didn’t change anything. I hate this kind of things that happen all of the sudden, you know. And I wonder that nobody complain the same thing in here so far.

Anyway thanks again

Luboš