New domain - Error 503

    Server: Ubuntu 16.04 Xenial Xerus


    i-MSCP 1.4.3 Build: 20170417 Codename: Zimmer
    PHP-Switcher Version 3.0.4 (Build 2017041701)
    Apache 2.4.18 (Ubuntu)
    Server API FPM/FastCGI


    After a problem upgrading from 1.4.2 to 1.4.3 which was fixed by Nuxwin (thanks to you again!) I set up the first domain using PHP 5.3.29. The site is running php and cgi without any problem.
    Now I tried to set up another domain with exactly the same Software, using PHP5.3.29 also and run into Error 503 trying to call the site. The apache error-log for the new domain says:


    Code
    1. [proxy:error] [pid: ...] AH00959: ap_proxy_connect_backend disabeling worker for (example.com) for 0s
    2. [proxy_fcgi:error] [pid ...] [client ...] AH0179: failed to make connection to backend: httpd-UDS
    3. [proxy:error] [pid ...] (2)Nosuch file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/phpswicher/psw5.3-fpm-example.com.sock (example.com) failed


    What's the problem and how to solve it? Why the first installation is running, the second not at all?


    Greets, Symphosius

    @symphosius


    I can say nothing without accessing the server and the panel ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    @symphosius


    When switching a PHP version, the plugin do a reload. It seem that a reload is not sufficient. I'll investigate further and fix the issue. A restart of the FPM instance solve the problem but I don't really like that because this affect pools of all other customers.


    The best would be to implement the "per customer master FPM process" feature. Here, each customer would have it own master FPM process (better isolation). This would avoid to restart pool of all customers each time a customer is changing its PHP version. I'm also thinking about chroot option for PHP FPM ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    @symphosius


    I cannot confirm the problem on my test server. I need to investigate further on your server. Data are still OK?

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support