Issue When an add-on domain is set to PHP-FPM and removed, PHP-FPM config file is not removed

[Bitpalast]

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Onyx, MU #15, CentOS 7.3, 64-Bit

PROBLEM DESCRIPTION
If a domain is removed from a subscription that was peviously defined as "website" in hosting setting and using PHP-FPM, the corresponding PHP-FPM configuration file is not removed from the fpm configuration directory. This prevents further restarts or starts of PHP-FPM service, because the configuration file is found and parsed, but the corresponding web server directory and web space is now missing.

STEPS TO REPRODUCE
Create subscription, add a domain and set the domain to PHP-FPM 7.0. Then remove the domain.

ACTUAL RESULT
PHP-FPM configuration file remains in PHP FPM configuration directory.

EXPECTED RESULT
Should be removed.

ANY ADDITIONAL INFORMATION
Not tested if reproduceable or "always" the case.

 

[Bitpalast]

ADDITIONAL INFORMATION
Meanwhile I have tested several transactions on a test system, e.g. creating domain, removing, changing hosting type and removing, changing FPM to FastCGI and back and removing etc. I was unable to reproduce the issue on the test system. I assume that the issue occurs as the result of a timing problem, because on the system where it occured, it normally takes a very long while until configuration is updated, because running PHP-FPM processes prevent immediate changes. My guess is that while the one update has not yet finished, the customer has made another one, overwriting the transaction of the first and leading to the remaining .conf file in /opt/plesk/php/7.0/etc/php-fpm.d. Timing seems to be general issue when updates to domains are done. I'd suggest to lock a domain and a customer account to further changes until one change has completed. We had similar issues with the Let's Encrypt certificates that customers where creating, deleting, creating, deleting stuff within seconds, and the scripts did not do it in the right order which caused files and actual live configuration to be out of sync. Customers are playing around a lot, and it would be better to set their panel to "read only" until one update has gone through completely.

 

[IgorG]

Thank you. Created request PPS-135