This document explains the following information about the PHP FastCGI Process Manager (PHP-FPM) daemon:
- The PHP-FPM filesystem layout.
- How the system implements PHP-FPM on your system.
PHP-FPM provides an alternative FastCGI daemon for PHP that allows a website to handle significant loads. It allows a host to set specific amounts of resources to process a domain's requests via workers available to respond to PHP requests (pools). These pools allow a website to process more requests.
PHP-FPM functions more quickly than traditional CGI-based methods, such as SUPHP, for multi-user PHP environments. It does not overload a system's memory with PHP from Apache processes, such as the
ruid2+php-dso process. PHP-FPM only executes PHP requests, which enables it to service content quicker than other methods.
Cpanel/PHPFPM.pm) module provides the basis of EasyApache support with PHP-FPM. The module's built-in defaults generate configuration files that provide fully functional PHP-FPM pools for a domain.
The system uses the following configuration files:
Each file contains different directives from the built-in values.
- The system does not require these files to run because the built-in defaults enable the PHP-FPM to run sufficiently.
- Only include the differences in directives within these files.
The following example displays the
system.yaml file's contents:
- This example only uses a different value than the built-in default for the
system-pool-defaults.yamlfile applies the value to each pool that you create.
- Each domain in the system requires that you create one pool.
- Replace any unacceptable characters such as "
.()" with an underscore (
The table below contains examples of unacceptable value names.
|Old Name||New Name|
If you prepend any PHP settings with the with the
disable_classes flag, the system will append the new
php.ini value to the previous one in the user's
.htaccess files. For more information, read securephp.net's FastCGI Process Manager (FPM) documentation.
The filesystem configuration files
The system stores the configuration files that control PHP-FPM in the following files:
|This file contains the system configurations of PHP-FPM.|
|This file changes your domain to the domain setting of the website that you use. For example, the |
.yaml files within the
/var/cpanel directories generate these two files.
- Do not edit these configuration files manually.
- The system duplicates these configuration files for each version that you select.
php54as its version.
- You must change
ea-php54to the version on which your system currently runs. For example, if your system runs on PHP version 5.5 or 5.6, change
Use the following required files only if you wish to run PHP-FPM:
This file controls a specific domain's pool. The system uses the built-in default values and
Use the following optional files only if you wish to to change the default parameters:
This file contains system level settings.
The system also uses this file to generate the
The system uses this file to generate each domain's pool and configure each user's pool.
If you edit a user's pool in WHM's MultiPHP Manager interface (WHM >> Home >> Software >> MultiPHP Manager), the system no longer applies the system default settings to that user.
All domain pools use these defaults unless a
.yaml file overrides them.
Restore PHP to your system
The system cannot remove configurations or other related files when you manually remove RPMs. If you manually remove RPMs, you could remove dependencies that your hosted websites require.
We do not recommend that you perform
yum remove operations with any
ea-php RPMs. If you remove PHP from your system while any of your hosted websites still use it, those websites will display errors. In addition, Apache could fail to display the website entirely. Before you perform a
yum remove operation, confirm that none of your hosted websites use the PHP version that you wish to remove with WHM's MultiPHP Manager interface (Home >> Software >> MultiPHP Manager).
To restore PHP versions to your system, run the following commands:
If the above commands fail, contact your system administrator.