web hosting

Plesk php service repair - Service Temporarily Unavailable

If you have several Domains with different php versions on a Plesk Server operates it comes there and how.der to problems caused by incorrect file creation by Plesk.

Domain owners will then see, for example, a Error message when calling the website like

Error message of the Web server for failure to provide a service

The cause of the error

The reason for this message in this case is a not started php-fpm Service that cannot restart due to a faulty file in the configuration. These files are managed by the Plesk service. Sometimes they are not deleted or not created properly. In this case you can only independent take action and correct the problem.

Finding and correcting errors

You can use the Error in a case like this. Error logs are written for each service which often show the problem show.

In this example you only have to go to the search for the log files of the php-fpm service. If you know the php version of the user, you can simply look up the log of the service directly. Alternatively, you can also simply check all Services simultaneously query and eliminate errors.

Example under Centos7:

tail -f /var/log/plesk-php56-fpm/error.log

[07-Jun-2019 09:40:15] ERROR: An another FPM instance seems to already listen on /var/www/vhosts/system/ihrefirma.de/php-fpm.sock

[07-Jun-2019 09:40:15] ERROR: FPM initialization failed

This basically means that the Domain yourcompany.com seems to have been loaded in a different php-fpm configuration, i.e. the php version of the domain might have been changed from php5.6 to another one. In this case, Plesk failed to remove the original configuration file. The php-fpm service cannot be restarted.

Solution of the problem

Remove the broken file from the server's php-fpm configuration.

Example for Centos7:

rm -rf /opt/plesk/php/5.6/etc/php-fpm.d/ihrefirma.de.conf

After that you should see the successful restart directly in the error log of the defective service.

tail -f /var/log/plesk-php56-fpm/error.log

[07-Jun-2019 09:42:04] NOTICE: fpm is running, pid 120959

[07-Jun-2019 09:42:04] NOTICE: ready to handle connections

07-Jun-2019 09:42:04] NOTICE: systemd monitor interval set to 10000ms

Please divide the contribution
Share on facebook
Share on twitter
Share on linkedin
Share on pinterest
Share on whatsapp
Share on telegram
Latest posts

Recommended videos from our Youtube Channel