Domains on PHP-FPM do not work with error 503 after changing virtual hosts location: the prefix '/var/www/vhosts/system/example.com' does not exist or is not a directory

Follow

Comments

2 comments

  • Avatar
    Christian B.

    Hi George,

    in my case i can't update my plesk version or to a newer PHP version. So i returned to 7.0 and deleted 7.3 and 7.4 to be sure. No I see in the logs while executing systemctl status php7.0-fpm.service following error messages.

    The prefix shows to an old domain which has already be removed time ago. In one of my domain i select the 7.0 and apply, and then i used your update command but the prefix doesn't change. Any tipps?

    ● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
    Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
    Drop-In: /lib/systemd/system/php7.0-fpm.service.d
    └─limit_nofile.conf
    Active: failed (Result: exit-code) since Do 2020-08-20 14:29:38 CEST; 1h 4min ago
    Main PID: 10885 (code=exited, status=78)

    Aug 20 14:29:37 hostname systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
    Aug 20 14:29:38 hostname php-fpm7.0[10885]: [20-Aug-2020 14:29:38] ERROR: [pool deleteddomain] the prefix '/var/www/vhosts/system/deleteddomain' does not exist or is not a directory
    Aug 20 14:29:38 hostname php-fpm7.0[10885]: [20-Aug-2020 14:29:38] ERROR: failed to post process the configuration
    Aug 20 14:29:38 hostname php-fpm7.0[10885]: [20-Aug-2020 14:29:38] ERROR: FPM initialization failed
    Aug 20 14:29:38 hostname systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
    Aug 20 14:29:38 hostname systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
    Aug 20 14:29:38 hostname systemd[1]: php7.0-fpm.service: Unit entered failed state.
    Aug 20 14:29:38 hostname systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Christian B.

    Please, follow the instructions from this article: https://support.plesk.com/hc/en-us/articles/213409669

    The reason for such behavior is some configuration left after domain removal.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request