Hello,

System:

Debian Buster with Froxlor 0.10.12, PHP7.3 and activated php-fpm

Settings php-fpm:

Process manager control (pm): dynamic

The number of child processes: 1 

The number of child processes created on startup: 20

The desired minimum number of idle server processes: 5

The desired maximum number of idle server processes: 35

Requests per child before respawning: 0

Idle Timeout: 30

 

Now rebuild config for domains and the files in /etc/php/7.3/fpm/pool.d contains following php-fpm settings:

pm = dynamic
pm.max_children = 1
pm.start_servers = 1
pm.min_spare_servers = 1
pm.max_spare_servers = 1
pm.max_requests = 0
request_terminate_timeout = 60s
request_slowlog_timeout = 5s
 

so the values are not the configured ones. Did i do something wrong? Php-fpm values are not overriden in custom php-config for domains.

 

Did you adjust these values in "PHP-FPM Versions" or in "PHP Configuration"? If the latter, then I bet you forgot to check "Override FPM-daemon settings (pm, max_children, etc.)"

Hello,

PHP-FPM versions: System default -> default froxlor as described above (No overide deamon settings possible)

PHP-CONFIGURATIONS: PHP-FPM config: System default

Add "-pass-header Authorization" / "CGIPassAuth On" to vhosts: is deactivated

Override FPM-daemon settings (pm, max_children, etc.): is activated

Process manager control (pm): dynamic

The number of child processes: 1 

The number of child processes created on startup: 20

The desired minimum number of idle server processes: 5

The desired maximum number of idle server processes: 35

Requests per child before respawning: 0

Idle Timeout: 30

Ah okay, this is due to "wrong" settings, for example, if pm is set to dynamic and number of child processes is smaller then child processes at startup, the latter is set to the value of number of child processes etc. This is a failsafe to keep the settings sane or else fpm will not work. See https://github.com/Froxlor/Froxlor/blob/master/lib/Froxlor/Cron/Http/Php/Fpm.php#L148

Point taken: the interface should check and explain this and not even make the saving of such values possible, you can open an issue on github if you like