Beta Branch update php-fpm configuration in 123.09beta01

update php-fpm configuration in 123.09beta01

1. update default pm.max_children value from 20 to 30 in PHP-FPM config file /usr/local/etc/php-fpm.conf for fresh installs only. Existing installs not changed as it may override existing install's custom settings users may have made.
2. update nginx.conf add /usr/local/nginx/conf/default_phpupstream.conf in 123.09beta01

add /usr/local/nginx/conf/default_phpupstream.conf include file to /usr/local/nginx/conf/nginx.conf which contains the new default PHP-FPM upstream configuration named dft_php containing

Code (Text):

upstream dft_php {
  zone dftphp_zone 128k;
  server 127.0.0.1:9000;
  keepalive 2;
}

The global php include file at /usr/local/nginx/conf/php.conf in every generated nginx vhost is responsible for serving PHP to visitors. In the /usr/local/nginx/conf/php.conf include file the setting

Code (Text):

fastcgi_pass   127.0.0.1:9000;

is responsible for telling Nginx which PHP-FPM server to communicate with - the default PHP-FPM server is located on 127.0.0.1 port 9000.

with newly added /usr/local/nginx/conf/default_phpupstream.conf include file to /usr/local/nginx/conf/nginx.conf in place, you can edit /usr/local/nginx/conf/php.conf to change the referenced fastcgi_pass setting to talk to a upstream called dft_php

Code (Text):

fastcgi_pass dft_php;
#fastcgi_pass   127.0.0.1:9000;

with old setting commented out with a hash # in front of it. New 123.09beta01 installs only will default to this configuration in /usr/local/nginx/conf/php.conf with added /usr/local/nginx/conf/default_phpupstream.conf include file in /usr/local/nginx/conf/nginx.conf. Existing installs will have added /usr/local/nginx/conf/default_phpupstream.conf include file in /usr/local/nginx/conf/nginx.conf but /usr/local/nginx/conf/php.conf include is not changed as it may override existing install's custom settings.

dft_php upstream references the server that nginx will communicate with which is same default PHP-FPM 127.0.0.1 on port 9000 while upstream has additional settings for keepalive. Switching to such a setup might have slight benefit for PHP-FPM latency response times and performance.

Continue reading...

123.09beta01 branch

• Branch: centminmod/centminmod
• Commit History: centminmod/centminmod

 

unix sockets are disabled by default for TCP port 9000 usage - you can only set one not both at same time so setting that to unix sockets default with TCP 9000 backup = 502 errors for php

 

Just my own private testing for past few years

Of course you can do your own comparison testing of the new configuration versus previous one too

 

indeed true.. my custom setups do have fastcgi_keep_conn set as does experimental wordpress fastcgi_cache routine for centmin.sh menu option 22 that i have been working on. Will add it to the defaults now too

 

yes fastcgi_pass/server upstream is 1 per php-fpm pool. So if you have multiple PHP-FPM pools, you can list each in upstream as a separate server directive entry. But you want to create your own upstream instead of using this default one which will override with 123.09beta01 updates right now

 

no need to do that as you can use existing directory in php-fpm.conf uncomment

Code (Text):

;include=/usr/local/nginx/conf/phpfpmd/*.conf

to become

Code (Text):

include=/usr/local/nginx/conf/phpfpmd/*.conf

then add custom php-fpm pool, php_poolunix.conf into directory /usr/local/nginx/conf/phpfpmd/php_poolunix.conf but this will enable the extra pools Centmin Mod 123.09beta01 has too in /usr/local/nginx/conf/phpfpmd

so if you don't want that then yes do

Code (Text):

include=/usr/local/nginx/conf/php_poolunix.conf

don't edit default /usr/local/nginx/conf/default_phpupstream.conf but create your own i.e. /usr/local/nginx/conf/default_phpunixupstream.conf and include into /usr/local/nginx/conf/nginx.conf

also as per Beta Branch - Centmin Mod .08 beta03+ Multiple PHP-FPM pools support added upstream php-fpm needs to add to /usr/local/nginx/conf/php.conf or create copy of php.conf to include/replace in nginx vhost with

Code (Text):

fastcgi_next_upstream error timeout http_500 http_503;

but setting this will on xenforo forum closures result in alternating 503 and 502 bad gateway errors for visitors as xenforo reports 503 when closed and all php-fpm pools would send 503 to nginx which nginx would see as php-fpm pools all being down

Module ngx_http_fastcgi_module

 

If you don't set it, it has it's defaults for just error and timeout instances where it will move to next upstream i.e. backup.

 

Yeah tricky as Chris stated 503 status is valid for temporarily unavailable for forum closed inactive status. You don't want 200 status as search engines will index the closed state of your forums.

 

Yeah that might work

 

that's because php-fpm unix sockets do not scale - see high concurrency traffic PHP-FPM benchmarks where oneinstack LEMP stack uses php-fpm unix sockets at PHP - PHP 7.x Benchmarks Centmin Mod vs Easyengine vs Webinoly vs VestaCP vs OneInStack