Resolved PHP 8.1 Another FPM instance seems to already listen on [...] php-fpm.sock

[Ankebut]

Server operating system version

Obsidian

Plesk version and microupdate number

Version 18.0.49 Update #2

hello,

my websites not available after update today to Version 18.0.49 Update #2,

when i wi try to start receive error like this:

root@srv1 / # service plesk-php81-fpm restart


Job for plesk-php81-fpm.service failed because the control process exited with error code.


See "systemctl status plesk-php81-fpm.service" and "journalctl -xe" for details.


root@srv1 / # service plesk-php80-fpm restart


Job for plesk-php80-fpm.service failed because the control process exited with error code.


See "systemctl status plesk-php80-fpm.service" and "journalctl -xe" for details.


root@srv1 / #

Unable to manage service by phpinimng ('start', 'plesk-php81-fpm'): Job for plesk-php81-fpm.service failed because the control process exited with error code. See "systemctl status plesk-php81-fpm.service" and "journalctl -xe" for details. Failed to start plesk-php81-fpm service

and i got this errors:

-- Logs begin at Thu 2023-01-12 16:39:11 CET, end at Thu 2023-01-12 17:22:40 CET. --


Jan 12 16:39:11 srv1.doitauto.de systemd[783731]: run-user-10000.mount: Succeeded.


Jan 12 16:39:11 srv1.doitauto.de systemd[783729]: run-user-10000.mount: Succeeded.


Jan 12 16:49:12 srv1.doitauto.de systemd[783729]: run-user-10000.mount: Succeeded.


Jan 12 16:49:12 srv1.doitauto.de systemd[783731]: run-user-10000.mount: Succeeded.


Jan 12 16:59:12 srv1.doitauto.de systemd[783729]: run-user-10000.mount: Succeeded.


Jan 12 16:59:12 srv1.doitauto.de systemd[783731]: run-user-10000.mount: Succeeded.


Jan 12 17:00:12 srv1.doitauto.de systemd[783729]: run-user-10000.mount: Succeeded.


Jan 12 17:00:12 srv1.doitauto.de systemd[783731]: run-user-10000.mount: Succeeded.


Jan 12 17:01:26 srv1.doitauto.de plesk_saslauthd[2442804]: privileges set to (109:116) (effective 109:116)


Jan 12 17:01:26 srv1.doitauto.de plesk_saslauthd[2442804]: failed mail authentication attempt for user 'abuse' (password len=12)


Jan 12 17:01:26 srv1.doitauto.de postfix/smtpd[2442803]: warning: unknown[141.98.11.83]: SASL LOGIN authentication failed: authentication failure


Jan 12 17:01:26 srv1.doitauto.de postfix/smtpd[2442803]: disconnect from unknown[141.98.11.83] ehlo=2 starttls=1 auth=0/1 quit=1 commands=4/5


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Scheduled restart job, restart counter is at 11677.


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: Stopped The PHP 8.1.14 FastCGI Process Manager.


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: Starting The PHP 8.1.14 FastCGI Process Manager...


Jan 12 17:01:29 srv1.doitauto.de php-fpm[2442810]: [12-Jan-2023 17:01:29] ERROR: Another FPM instance seems to already listen on /var/www/vhosts/system/do-it-auto.de/php-fpm.sock


Jan 12 17:01:29 srv1.doitauto.de php-fpm[2442810]: [12-Jan-2023 17:01:29] ERROR: FPM initialization failed


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Main process exited, code=exited, status=78/CONFIG


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Failed with result 'exit-code'.


Jan 12 17:01:29 srv1.doitauto.de systemd[1]: Failed to start The PHP 8.1.14 FastCGI Process Manager.


Jan 12 17:01:30 srv1.doitauto.de postfix/smtpd[2442803]: warning: hostname 110.getpocket.com does not resolve to address 91.224.92.110


Jan 12 17:01:30 srv1.doitauto.de postfix/smtpd[2442803]: connect from unknown[91.224.92.110]


Jan 12 17:01:33 srv1.doitauto.de plesk_saslauthd[2442804]: failed mail authentication attempt for user 'recruit' (password len=10)


Jan 12 17:01:33 srv1.doitauto.de postfix/smtpd[2442803]: warning: unknown[91.224.92.110]: SASL LOGIN authentication failed: authentication failure


Jan 12 17:01:33 srv1.doitauto.de postfix/smtpd[2442803]: disconnect from unknown[91.224.92.110] ehlo=2 starttls=1 auth=0/1 quit=1 commands=4/5


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Scheduled restart job, restart counter is at 11678.


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: Stopped The PHP 8.1.14 FastCGI Process Manager.


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: Starting The PHP 8.1.14 FastCGI Process Manager...


Jan 12 17:01:34 srv1.doitauto.de php-fpm[2442831]: [12-Jan-2023 17:01:34] ERROR: Another FPM instance seems to already listen on /var/www/vhosts/system/do-it-auto.de/php-fpm.sock


Jan 12 17:01:34 srv1.doitauto.de php-fpm[2442831]: [12-Jan-2023 17:01:34] ERROR: FPM initialization failed


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Main process exited, code=exited, status=78/CONFIG


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Failed with result 'exit-code'.


Jan 12 17:01:34 srv1.doitauto.de systemd[1]: Failed to start The PHP 8.1.14 FastCGI Process Manager.


Jan 12 17:01:39 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Scheduled restart job, restart counter is at 11679.


Jan 12 17:01:39 srv1.doitauto.de systemd[1]: Stopped The PHP 8.1.14 FastCGI Process Manager.


Jan 12 17:01:39 srv1.doitauto.de systemd[1]: Starting The PHP 8.1.14 FastCGI Process Manager...


Jan 12 17:01:39 srv1.doitauto.de php-fpm[2442843]: [12-Jan-2023 17:01:39] ERROR: Another FPM instance seems to already listen on /var/www/vhosts/system/do-it-auto.de/php-fpm.sock

 

[Peter Debik]

Have you checked the mentioned
# journalctl -xe
# systemctl status plesk-php81-fpm.service
for details?

 

[Ankebut]

root@srv1 / # systemctl status pleskphp81-fpm.service

Unit pleskphp81-fpm.service could not be found.

# journalctl -xe

- A stop job for unit plesk-php81-fpm.service has finished.
--
-- The job identifier is 13127958 and the job result is done.
Jan 12 17:33:20 srv1.doitauto.de systemd[1]: Starting The PHP 8.1.14 FastCGI Process Manager...
-- Subject: A start job for unit plesk-php81-fpm.service has begun execution
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- A start job for unit plesk-php81-fpm.service has begun execution.
--
-- The job identifier is 13127958.
Jan 12 17:33:20 srv1.doitauto.de php-fpm[2524981]: [12-Jan-2023 17:33:20] ERROR: Another FPM instance seems to already listen on /var/www/vhosts/system/do-it-auto.de/php-fpm.sock
Jan 12 17:33:20 srv1.doitauto.de php-fpm[2524981]: [12-Jan-2023 17:33:20] ERROR: FPM initialization failed
Jan 12 17:33:20 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Main process exited, code=exited, status=78/CONFIG
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- An ExecStart= process belonging to unit plesk-php81-fpm.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 78.
Jan 12 17:33:20 srv1.doitauto.de systemd[1]: plesk-php81-fpm.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- The unit plesk-php81-fpm.service has entered the 'failed' state with result 'exit-code'.
Jan 12 17:33:20 srv1.doitauto.de systemd[1]: Failed to start The PHP 8.1.14 FastCGI Process Manager.
-- Subject: A start job for unit plesk-php81-fpm.service has failed
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- A start job for unit plesk-php81-fpm.service has finished with a failure.
--
-- The job identifier is 13127958 and the job result is failed.

 

[Peter Debik]

Please make sure that the upgrade process was completed without errors. For that, please see /var/log/plesk/install/autoinstaller3.log. Did the upgrade finish with a success message? Only then continue:

# service plesk-php81-fpm stop
--> Must stop running 8.1

# ps aux | grep 8.1/etc/php-fpm | grep -v grep
--> Must not show any result afterwards.

If there is still a line like
root 1234 0.0 0.0 581960 20884 ? Ss 16:30 0:01 php-fpm: master process (/opt/plesk/php/8.1/etc/php-fpm.conf)
it will be safe to remove with
# kill -p 1234
(instead of 1234 use the real process id).

# service plesk-php81-fpm status
must now return that the service is not running (e.g. "inactive (dead)").

# service plesk-php81-fpm start
should now start it without issues (or at least give a good reason why it does not want to start).

 

[Ankebut]

root@srv1 / # service plesk-php81-fpm stop
root@srv1 / # ps aux | grep 8.1/etc/php-fpm | grep -v grep
root@srv1 / # service plesk-php81-fpm status
● plesk-php81-fpm.service - The PHP 8.1.14 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/plesk-php81-fpm.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/plesk-php81-fpm.service.d
└─add-preload-plesk-resctrl-lib.conf, limit_nofile.conf, respawn.conf
Active: inactive (dead) (Result: exit-code) since Thu 2023-01-12 17:54:51 CET; 1min 34s ago
Process: 2596832 ExecStart=/opt/plesk/php/8.1/sbin/php-fpm --nodaemonize (code=exited, status=78)
Main PID: 2596832 (code=exited, status=78)

Jan 12 17:54:51 srv1.doitauto.de systemd[1]: Stopped The PHP 8.1.14 FastCGI Process Manager.
root@srv1 / # service plesk-php81-fpm start
Job for plesk-php81-fpm.service failed because the control process exited with error code.
See "systemctl status plesk-php81-fpm.service" and "journalctl -xe" for details.
root@srv1 / #

 

[Ankebut]

also is not working

 

[scsa20]

Hi @Ankebut,

Without log files to help pin point the issue, the only thing I can suggest is to try one of the following:

1. Remove and reinstall PHP 8.1 from Plesk updater
2. Go to Tools & Settings > Assistance and Troubleshooting > Diagnose & Repair, under the section Web & FTP Servers, click the "Change..." button and change it to "Only the PHP Handlers" option, and hit "Check Selected" to see what that says
   • If it comes back with issues, choose to run the repair.

 

[Ankebut]

that say no issues

 

[Ankebut]

ssh say same all ok but fpm is not running :-(

root@srv1 ~ # plesk repair web -php-handlers -php-fpm-configuration





Checking the usage of PHP handlers .................................. [OK]





Checking for obsolete PHP-FPM configuration files ................... [OK]





Error messages: 0; Warnings: 0; Errors resolved: 0

 

[scsa20]

You manually ran the check? Or you just looking at the last scan (which was probably before this issue)?

And did you try to remove and reinstall the PHP version?

 

[Ankebut]

yes i have remove much time all php version and install agin but nothing :-(

 

[Peter Debik]

I do not get why
"Jan 12 17:01:29 srv1.doitauto.de php-fpm[2442810]: [12-Jan-2023 17:01:29] ERROR: Another FPM instance seems to already listen on /var/www/vhosts/system/do-it-auto.de/php-fpm.sock"
is possible when there is no PHP-FPM remaining on the server. That does not seem plausible. Maybe it would make sense to change the PHP version that is set for the domain to a different one, then try to start 8.1 again, then change it back?

 

[Ankebut]

i have got now purge all php version from ssh terminal after i have run
"plesk repair web -php-handlers" i have set one of my domain to the new installed php 8.1 but nothing

 

[Ankebut]

i have again remove all php version after i have install only php8.1 i have use for a domain FastCGI application served by Apache and now the domain work after i set the domain to FPM application served by nginx that is no more run and kill php 8.1 that is working anything then i must remove all php and install again, real bad thing.

 

[Ankebut]

Error: phpinimng failed: WARNING:__main__:Removal of configuration file failed: [Errno 2] No such file or directory: '/opt/plesk/php/8.1/etc/php-fpm.d/forum.doitauto.de.conf'
Job for plesk-php81-fpm.service failed because the control process exited with error code.
See "systemctl status plesk-php81-fpm.service" and "journalctl -xe" for details.
ERRORhp_fpm:Failed to start plesk-php81-fpm service, pause before retry
Job for plesk-php81-fpm.service failed because the control process exited with error code.
See "systemctl status plesk-php81-fpm.service" and "journalctl -xe" for details.
Failed to start plesk-php81-fpm service

 

[Ankebut]

what its mean that is realy very confused :-( now 10 hours not working, that is realy from last update the problem.

 

[Peter Debik]

I suggest to open a ticket with Plesk support so that they can check and repair this directly on your server. It is an abnormal behavior and technically does not make much sense. Normally this all works like a charm, and our common goal must be to get it working for your installation, too. Support is highly qualified, they will very likely find the reason and fix it:

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com

 

[Ankebut]

dont have access to support that say i have it from my provider the license :-(
fxxxxx ****

 

[Ankebut]

also it is working only FastCGI Apache Mode after when i switch to FPM that kill all my configuration and nothing work after i must deinstall all php version and install again.

 

[Peter Debik]

dont have access to support that say i have it from my provider the license :-(

You can use the free trial period of the support subscription as offered in the above link "how to get ...".