Background: I found this warning after a performance issue and I need to increase `pm.max_children` setting in /usr/local/php74/etc/php-fpm.conf from the default of 10 to 120.
Originally, I did this manually in /usr/local/php74/etc/php-fpm.conf direct, unaware that it would be overwritten on update. It did, and the problem returned.
I found this doc that I thought was the answer. https://docs.directadmin.com/webser...l#warning-server-reached-max-children-setting. I tried both options on that doc.
1. `da config-set php_fpm_max_children_default 100` + `systemctl restart directadmin`
2. Admin Level -> Custom Httpd Config -> domain.com: php-fpm74 and adding `|?MAX_CHILDREN=120|` to the CUSTOM1 token area
In both cases, when I run `da build rewrite_confs`, /usr/local/php74/etc/php-fpm.conf simply reverts to 10.
Can anyone see anything obvious I am missing?
server reached max_children setting (10), consider raising it
Originally, I did this manually in /usr/local/php74/etc/php-fpm.conf direct, unaware that it would be overwritten on update. It did, and the problem returned.
I found this doc that I thought was the answer. https://docs.directadmin.com/webser...l#warning-server-reached-max-children-setting. I tried both options on that doc.
1. `da config-set php_fpm_max_children_default 100` + `systemctl restart directadmin`
2. Admin Level -> Custom Httpd Config -> domain.com: php-fpm74 and adding `|?MAX_CHILDREN=120|` to the CUSTOM1 token area
In both cases, when I run `da build rewrite_confs`, /usr/local/php74/etc/php-fpm.conf simply reverts to 10.
Can anyone see anything obvious I am missing?
Last edited: