• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved PHP 7.0.13 - phpinimng failed

Smir

New Pleskian
When using PHP 7.0.13, my WordPress site doesn't like to work, after a little googling I found this error below, but unfortunately not away to fix?

Plesk Error is

Code:
Error: phpinimng failed: Job for plesk-php70-fpm.service failed because the control process exited with error code. See "systemctl status plesk-php70-fpm.service" and "journalctl -xe" for details. Failed to start plesk-php70-fpm service

Code:
root@lon:~# /etc/init.d/plesk-php70-fpm restart
[....] Restarting plesk-php70-fpm (via systemctl): plesk-php70-fpm.serviceJob fo                                        r plesk-php70-fpm.service failed because the control process exited with error c                                        ode. See "systemctl status plesk-php70-fpm.service" and "journalctl -xe" for det                                        ails.
 failed!
root@lon:~# systemctl status plesk-php70-fpm.service
● plesk-php70-fpm.service - The PHP 7.0.13 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/plesk-php70-fpm.service; enabled; vendor
   Active: failed (Result: exit-code) since Tue 2016-11-29 17:17:52 EST; 22s ago
  Process: 9444 ExecStart=/opt/plesk/php/7.0/sbin/php-fpm --nodaemonize (code=ex
 Main PID: 9444 (code=exited, status=78)

Nov 29 17:17:52 lon systemd[1]: Stopped The PHP 7.0.13 FastCGI Process Manager.
Nov 29 17:17:52 lon systemd[1]: Starting The PHP 7.0.13 FastCGI Process Manager.
Nov 29 17:17:52 lon php-fpm[9444]: [29-Nov-2016 17:17:52] ERROR: An another FPM
Nov 29 17:17:52 lon php-fpm[9444]: [29-Nov-2016 17:17:52] ERROR: FPM initializat
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Main process exited, co
Nov 29 17:17:52 lon systemd[1]: Failed to start The PHP 7.0.13 FastCGI Process M
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed sta
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exi
lines 1-14/14 (END)
● plesk-php70-fpm.service - The PHP 7.0.13 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/plesk-php70-fpm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-11-29 17:17:52 EST; 22s ago
  Process: 9444 ExecStart=/opt/plesk/php/7.0/sbin/php-fpm --nodaemonize (code=exited, status=78)
 Main PID: 9444 (code=exited, status=78)

Nov 29 17:17:52 lon systemd[1]: Stopped The PHP 7.0.13 FastCGI Process Manager.
Nov 29 17:17:52 lon systemd[1]: Starting The PHP 7.0.13 FastCGI Process Manager...
Nov 29 17:17:52 lon php-fpm[9444]: [29-Nov-2016 17:17:52] ERROR: An another FPM instance seems to already listen on /var
Nov 29 17:17:52 lon php-fpm[9444]: [29-Nov-2016 17:17:52] ERROR: FPM initialization failed
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Main process exited, code=exited, status=78/n/a
Nov 29 17:17:52 lon systemd[1]: Failed to start The PHP 7.0.13 FastCGI Process Manager.
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:17:52 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
~
~
lines 1-14/14 (END)
 
Hi Smir,

pls, see for examples, explanations and solutions to your described issue: => #4
 
its not an let's encrypt issue :) as other php versions work fine

some more logs;
Code:
root@lon:~#  journalctl -xe
-- The result is failed.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
Nov 29 17:51:23 lon systemd[1]: Starting The PHP 7.0.13 FastCGI Process Manager...
-- Subject: Unit plesk-php70-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php70-fpm.service has begun starting up.
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: An another FPM instance seems to already listen on /va
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: FPM initialization failed
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Main process exited, code=exited, status=78/n/a
Nov 29 17:51:23 lon systemd[1]: Failed to start The PHP 7.0.13 FastCGI Process Manager.
-- Subject: Unit plesk-php70-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php70-fpm.service has failed.
--
-- The result is failed.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
Nov 29 17:51:47 lon plesk_saslauthd[10815]: select timeout, exiting
lines 1882-1904/1904 (END)
-- The result is failed.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
Nov 29 17:51:23 lon systemd[1]: Starting The PHP 7.0.13 FastCGI Process Manager...
-- Subject: Unit plesk-php70-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php70-fpm.service has begun starting up.
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: An another FPM instance seems to already listen on /var/
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: FPM initialization failed
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Main process exited, code=exited, status=78/n/a
Nov 29 17:51:23 lon systemd[1]: Failed to start The PHP 7.0.13 FastCGI Process Manager.
-- Subject: Unit plesk-php70-fpm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit plesk-php70-fpm.service has failed.
--
-- The result is failed.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
Nov 29 17:51:47 lon plesk_saslauthd[10815]: select timeout, exiting
lines 1882-1904/1904 (END)
-- The result is failed.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Unit entered failed state.
Nov 29 17:51:23 lon systemd[1]: plesk-php70-fpm.service: Failed with result 'exit-code'.
Nov 29 17:51:23 lon systemd[1]: Starting The PHP 7.0.13 FastCGI Process Manager...
-- Subject: Unit plesk-php70-fpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--

Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: An another FPM instance seems to already listen on /var/www/vhosts/system/<domain>/php-fpm.sock

I guess this is the main cause.. I'm not sure how to fix this...

aptitude install init init-system-helpers
This doesn't work so can't install the system helpers


seems to be that 7.0.13 won't work while 7.0.8 is on.. weird this is, that on a fresh Plesk install, these are both installed...?

is it possible to force the 7.0.13 to be the OS vendor, instead of the 7.0.8 so that it can be completly removed?
 
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: An another FPM instance seems to already listen on /var/www/vhosts/system/<domain>/php-fpm.sock

can lead to a previous started PHP-FPM - socket for the specific domain/subdomain, which causes a failure, when you try to restart another socket, with another PHP - handler.

Consider to stop for example the Plesk-PHP5.6-FPM and the Plesk-PHP7.0-FPM service manually with the command:

service plesk-php56-fpm stop && service plesk-php70-fpm stop
Pls. check afterwards that there are no more ( orphaned ) sockets at for example:

/var/www/vhosts/system/DOMAIN-OR-SUB-DOMAIN.COM/
and check as well, that you have ONLY ONE domain-subdomain - specific PHP-FPM configuration at for example "/opt/plesk/php/5.6/etc/php-fpm.d/" AND "/opt/plesk/php/7.0/etc/php-fpm.d/" ( use for example "ls -lah /opt/plesk/php/5.6/etc/php-fpm.d" to list the existent configuration files ).

When you checked, that you have ONLY ONE domain-subdomain - specific PHP-FPM configuration file, restart the depending services with:

service plesk-php56-fpm start && service plesk-php70-fpm start

You should remember, if you previously changed a PHP - handler for your domain or subdomain, so pls. consider to adapt the examples with the correct service.



Sorry, Smir, but I'm not sure about your statements right now, because
read through the entire post you linked, logs showed nothing in the Plesk folder.
... and before that, you stated:
Nov 29 17:51:23 lon php-fpm[10867]: [29-Nov-2016 17:51:23] ERROR: An another FPM instance seems to already listen on /var/www/vhosts/system/<domain>/php-fpm.sock
o_O
 
Hi.

I'm facing a similar issue, but the this don't work.

I don't have any.sock files in /var/www/vhosts/system/domain and can't start fpm.

I was trying to fix this error:

"server reached max_children setting (5)" and created a php.ini in /var/www/vhosts/system/domain.

After that I was never able again to start the services.

I've reverted the configuration changes, rebooted the server and no change.

Help very appreciated, I've my servers down.

I'm having this in log:
[06-Sep-2017 00:09:30] ERROR: No pool defined. at least one pool section must be specified in config file
[06-Sep-2017 00:09:30] ERROR: failed to post process the configuration
[06-Sep-2017 00:09:30] ERROR: FPM initialization failed
 
I don't understand this, I've pressed apply in plesk php handler for one domain, and it started to work.

I've then done at all my domains, and all are working now.

If I do the "php_settings -u" all go down...

For your reference, this was the link I was following.
 
Back
Top