Website running on PHP-FPM shows 503 Service Temporarily Unavailable: AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1)

Follow

Comments

4 comments

  • Avatar
    Marco Marsala (Edited )

    Seems that this service is not started at boot. You should start it manually from Tools & Settings > Services Management.

    When I experienced crash of this service today, I restarted the whole server but the service wasn't start at boot.

    In the the log below, for PHP-FPM 5.6 handler, you can see that service never tried to start at boot. Reboot was done after 08:46, time of last status log entry for such service. Starting service manually worked without any issue. The same applies to PHP-FPM 7.1 handler.

    This server is Ubuntu 16.04.3 LTS (upgraded from 14.04 following the KB procedure) with Plesk 17.5.3 Update #28.

    # /etc/init.d/plesk-php56-fpm status
    ● plesk-php56-fpm.service - The PHP 5.6.31 FastCGI Process Manager
    Loaded: loaded (/lib/systemd/system/plesk-php56-fpm.service; enabled; vendor preset: enabled)
    Active: failed (Result: signal) since Thu 2017-11-09 08:46:52 CET; 16min ago
    Process: 1119 ExecStart=/opt/plesk/php/5.6/sbin/php-fpm --nodaemonize (code=killed, signal=KILL)
    Main PID: 1119 (code=killed, signal=KILL)
    Status: "Processes active: 5, idle: 0, Requests: 0, slow: 0, Traffic: 0req/sec"
    CGroup: /system.slice/plesk-php56-fpm.service

    Nov 09 08:43:52 thenetworksolution.it systemd[1]: Starting The PHP 5.6.31 FastCGI Process Manager...
    Nov 09 08:45:22 thenetworksolution.it systemd[1]: plesk-php56-fpm.service: Start operation timed out. Terminating.
    Nov 09 08:46:52 thenetworksolution.it systemd[1]: plesk-php56-fpm.service: State 'stop-final-sigterm' timed out. Killing.
    Nov 09 08:46:52 thenetworksolution.it systemd[1]: plesk-php56-fpm.service: Main process exited, code=killed, status=9/KILL
    Nov 09 08:46:52 thenetworksolution.it systemd[1]: Failed to start The PHP 5.6.31 FastCGI Process Manager.
    Nov 09 08:46:52 thenetworksolution.it systemd[1]: plesk-php56-fpm.service: Unit entered failed state.
    Nov 09 08:46:52 thenetworksolution.it systemd[1]: plesk-php56-fpm.service: Failed with result 'signal'.
  • Avatar
    Denis Bykov (Edited )

    @Marco
    As I can see, the service is enabled, and the only explanation why it won't start at the boot is a failed dependency. plesk-php56-fpm depend on network and syslog:

    # grep After /lib/systemd/system/plesk-php56-fpm.service
    After=syslog.target network.target

    Try to check if syslog works correctly:

    # systemctl status syslog.service
  • Avatar
    Marco Marsala

    @Denis dependencies are ok, otherwise launching the service manually will fail too. As I said, starting the service manually worked.

    Btw I checked the syslog:

    ~# systemctl status syslog.service
    ● rsyslog.service - System Logging Service
    Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2017-11-09 08:43:53 CET; 6 days ago
    Docs: man:rsyslogd(8)
    http://www.rsyslog.com/doc/
    Main PID: 920 (rsyslogd)
    CGroup: /system.slice/rsyslog.service
    └─920 /usr/sbin/rsyslogd -n

     

  • Avatar
    Denis Bykov

    @Marco

    Are there some related errors in '/var/log/plesk-php56-fpm/error.log' and '/var/log/plesk-php71-fpm/error.log' files?

    If not, and the issue can be reproduced, I suggest raising a support ticket regarding this behavior.

Please sign in to leave a comment.

Have more questions? Submit a request