Articles in this section

See more

Plesk PHP FPM 7.0 service is down after switching to it from another FPM handler

Avatar
Miguel Monteiro
Updated
Follow
Plesk for Linux kb: bug ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • Plesk PHP FPM 7.0 service is down after switching website from another FPM handler to Plesk PHP FPM 7.0

  • The following error is shown in /var/log/plesk-php70-fpm/error.log 

    ERROR: An another FPM instance seems to already listen on /var/www/vhosts/system/example.com/php-fpm.sock
    ERROR: FPM initialization failed

  • File /var/www/vhosts/system/example.com/php-fpm.sock does not exist:

    # ls -la /var/www/vhosts/system/example.com/php-fpm.sock
    ls: cannot access /var/www/vhosts/system/example.com/php-fpm.sock: No such file or directory

  • Systemd is installed and enabled.

  • Error in Plesk UI:

    phpinimng failed: invoke-rc.d: initscript plesk-php70-fpm, action "status" failed. invoke-rc.d: initscript plesk-php70-fpm, action "status" failed. Service plesk-php70-fpm is down after attempt to start it

Cause

This is a software issue with internal ID #PPPM-4004 which is planned to be fixed in future Plesk updates.

Resolution

Until the fix becomes available, use the following workaround:

  1. Connect to the server via SSH;

  2. Create a custom systemd unit file with 3 sec timeout on restart using any text editor:

    For Debian-based systems:

    # cat /etc/systemd/system/plesk-php70-fpm.service
    .include /lib/systemd/system/plesk-php70-fpm.service
    [Service]
    Restart= on-failure
    RestartSec= 3

    For RHEL-based systems:

    # cat /etc/systemd/system/plesk-php70-fpm.service
    .include /usr/lib/systemd/system/plesk-php70-fpm.service
    [Service]
    Restart= on-failure
    RestartSec= 3

Comments

2 comments

Sort by Date Votes
  • Avatar
    Cagri Cayir

    Is this still the valid solution for php 7.2 on Plesk Obsidian 18.0.27 please?

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hi Cagri Cayir, 

    If you are experiencing the same symptoms described in this guide, then I'd suggest applying the solution provided. In case the issue persists, I suggest opening a ticket with our support team so we can investigate the issue further.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles