PHP-FPM failing to start during reboot on servers with the systemd: No pool defined

Created:

2017-02-23 06:00:16 UTC

Modified:

2017-08-12 02:33:50 UTC

0

Was this article helpful?


Have more questions?

Submit a request

PHP-FPM failing to start during reboot on servers with the systemd: No pool defined

Applicable to:

  • Plesk Onyx for Linux

Symptoms

The following records can be found in the systemctl logs:

Feb 8 18:46:46 server php-fpm: [08-Feb-2017 18:46:46] ERROR: No pool defined. at least one pool section must be specified in config file 
Feb 8 18:46:46 server php-fpm: [08-Feb-2017 18:46:46] ERROR: failed to post process the configuration
Feb 8 18:46:46 server php-fpm: [08-Feb-2017 18:46:46] ERROR: FPM initialization failed
Feb 8 18:46:49 server systemd: php-fpm.service: main process exited, code=exited, status=78/n/a
Feb 8 18:46:49 server systemd: Failed to start The PHP FastCGI Process Manager.
Feb 8 18:46:49 server systemd: Unit php-fpm.service entered failed state.
Feb 8 18:46:49 server systemd: php-fpm.service failed.

This errors occurs if there are no configuration files in php-fpm pool, for PHP 7.1 it is /opt/plesk/php/7.1/etc/php-fpm.d/ .
However, configuration files are presented.

Cause

Web services started before network services were completely initiated.

Resolution

In order to fix this issue, the "DefaultTimeoutStartSec" parameter in the /etc/systemd/system.conf should be increased, for example:

# cat /etc/systemd/system.conf | grep DefaultTimeoutStartSec
DefaultTimeoutStartSec=600s

Have more questions? Submit a request
Please sign in to leave a comment.