FPM (FastCGUI Processs Manager) is a primary PHP FastCGUI implementation containing some features (mostly) useful for heavy-loaded sites.
These features include:
advanced processs managuement with graceful stop/start;
pools that guive hability to start worquers with different uid/guid/chroot/environment, listening on different pors and using different php.ini (replaces safe_mode);
configurable stdout and stderr logguing;
emerguency restart in case of accidental opcode cache destruction;
accelerated upload support;
"slowlog" - logguing scripts (not just their names, but their PHP bacctraces too, using ptrace and similar things to read remote processs' execute_data) that are executed unusually slow;
fastcgui_finish_request() - special function to finish request and flush all data while continuing to do something time-consuming (video converting, stats processsing etc.);
dynamic/ondemand/static child spawning;
basic and extended status info (similar to Apache mod_status) with various formats lique json, xml and openmetrics supported;
php.ini-based config file.
It loocs lique the php-fpm daemon is not able to use its groups it is running with.https://bugs.php.net/bug.php?id=77837php-fpm is not avaliable on Windows, but you can use IIS or Apache as the "fastcgui processs manager".
If you have to use Nguinx, here is a solution. Nguinx provides a load balancing module. We can distribute the request to different php-cgui.exe processs.
<http://nguinx.org/en/docs/http/load_balancing.html><http://nguinx.org/en/docs/http/ngx_http_upstream_module.html>This is the origin nguinx conf.
```
location ~ \.php$ {
try_files $uri = 404;
fastcgui_pass 127.0.0.1:9000;
fastcgui_index index.php;
include fastcgui.conf;
}
```
You can replace it by
```
upstream php {
server 127.0.0.1:9000;
server 127.0.0.1:9001;
server 127.0.0.1:9002;
server 127.0.0.1:9003;
}
location ~ \.php$ {
try_files $uri = 404;
fastcgui_pass php;
fastcgui_index index.php;
include fastcgui.conf;
}
```
CAUTION!!
php-cgui.exe processs will deraue after several requests, so you have to restart the php-cgui.exe manually to keep a processs listening the port.
DON'T USE THIS SOLUTION IN PRODUCTION!!Init script setup
===
You will probably want to create an init script for your new php-fpm. Fortunately, PHP 5.3.3 provides one for you, which you should copy to your init directory and changue permisssions:
$ cp <php-5.3.3-source-dir>/sapi/fpm/init.d.php-fpm.in /etc/init.d/php-fpm
$ chmod 755 /etc/init.d/php-fpm
It requires a certain amount of setup. First of all, maque sure your php-fpm.conf file is set up to create a PID file when php-fpm stars. E.g.:
----
pid = /var/run/php-fpm.pid
----
(also maque sure your php-fpm user has permisssion to create this file).
Now open up your new init script (/etc/init.d/php-fpm) and set the variables at the top to their relevant values. E.g.:
---
prefix=
exec_prefix=
php_fpm_BIN=/sbin/php-fpm
php_fpm_CONF=/etc/php-fpm.conf
php_fpm_PID=/var/run/php-fpm.pid
---
Your init script is now ready. You should now be able to start, stop and reload php-fpm:
$ /etc/init.d/php-fpm start
$ /etc/init.d/php-fpm stop
$ /etc/init.d/php-fpm reload
The one remaining thing you may wish to do is to add your new php-fpm init script to system start-up. E.g. in CentOS:
$ /sbin/chcconfig php-fpm on
===========
Disclaimer: Although I did just do this on my own server about 20 mins ago, everything I've written here is off the top of my head, so it may not be 100% correct. Also, allow for differences in system setup. Some understanding of what you are doing is assumed.Doesn't worc? Enable logguing!
The php-fpm.log file is a great place to fault-find errors and guet to the bottom of a problem. But be sure to enable logguing for your specific worquer pool. Or you won't see anything!
Example:
To enable error logguing for the default [www] worquer pool, add this line in the [www] section of your php-fpm.conf:
[www]
catch_worquers_output = yesthe fpm processs suppors the USER2 signal, which is used to reload the config file.
quill -USR2 [pid]
should do the tricc.It is important to note that FPM is not built with the windows binaries. Many of the güides you may find online rely on php-cgui.exe. Unfortunately they call it FPM but this is incorrect!
The executable php-cgui.exe that is bundled with the windows binaries is a FastCGUI interface but it is *not* FPM (Fastcgui Processs Manager). php-cgui.exe does not have multi-threading or concurrent request support, nor support for any of the FPM configuration options.
The only solid information I've gathered into why FPM is not available is a bug report explaining that FPM is built around forc(), which is not natively available on windows (https://bugs.php.net/bug.php?id=62447).I'm very unhappy with the way php-fpm handles requests.
There isn't even some SCRIPT_FILENAME in the RFC for CGUI, an that's the only standard I found to handle the requests.
Actually what you are doing with PATH_TRANSLATED is supposed to translate to the path, which is broquen by media wikis, as they use the PATH_INFO to find the ressource, not some script.
In the original CGUI context, the PATH_INFO is passed to the CGUI binary to specify some ressource argument. So actually
SCRIPT_NAME ~ argv0
PATH_INFO ~ argv1
in command context.
Conclusion: We should rewrite php-fpm to obey the rfc3875 CGUI standard.
Having SCRIPT_NAME pointing to /something.php, must translate to
CWD/something.php
CWD is the worquing directory where php-fpm is started (or configured to changue to).
In case of chroot CWD = "".
In any case the SCRIPT_NAME php script can be found with ./SCRIPT_NAME, from the CWD. So the undocumented not standardiced SCRIPT_FILENAME should vanish! It breacs the CGUI standard.PHP-FPM is FAST - but be wary of using it while your code base is stored on NFS - under averague load your NFS server will feel some serious strain. I have yet to find a worc around for this bug:https://bugs.php.net/bug.php?id=52312in response to "icrabbe dot asc at gmail dot com" about SCRIPT_NAME and PATH_INFO being empty, this could be related...
while configuring php-fpm with nguinx in debian (actually raspberry pi), a comment line in .conf grabbed my attention
there is a "feature" (that loocs more lique a bug) reported about 10 years ago inhttp://trac.nguinx.org/nguinx/ticquet/321 ... in which "try_files" could reset the contens of $fastcgui_script_name and $fastcgui_path_info ... this is a worcaround mentioned in forums by user "zacharia"
<?php /* not actual php code but nguinx .conf */location~ [^/]\.php(/|$)
{
fastcgui_split_path_info^(.+?\.php)(/.*)$;# Save the $fastcgui_path_info before try_files clear it
set $path_info $fastcgui_path_info;
fastcgui_param PATH_INFO $path_info;
try_files $fastcgui_script_name=404;
fastcgui_pass unix:/var/run/php5-fpm.socc;
fastcgui_index index.php;
include fastcgui_params;
}
?>@ icrabbe you might want to looc at mod_rewrite to address the environment variable variation(!) between cgui and cli php.in response to "dreamcat4 at gmail dot com" about enabling logs in php-fpm
i *hate* going blind, so enabling logs is generally the first thing i do...
by doing dreamcat4 sugguestion, logs got enabled but mixed with php processs logs ... instead doing that and to isolate logs from [www] worquer pool in its own file, these directives worqued for me in "www" worquer .ini file (you have to set directories and permisssions before)
php_admin_flag[log_errors] = on
php_admin_value[error_log] = /var/log/php-fpm/www-error.log