Issue Plesk Migration Manager Assigns Disabled PHP-Handlers

[Enverex]

Plesk Migration Manager doesn't obey the currently configured Plesk PHP-Handlers and will assign domains to handlers which are currently disabled. For example, the migration manager shows:

========================
The PHP handler 5.5 mod_php (id=module) is not available on the destination server. Instead, Plesk will use the following PHP handler: 5.5.38 CGI application (id=plesk-php55-cgi).
========================

But I've already disabled all CGI handlers. The output of the current PHP handlers shows:

========================
id: display name: full version: version: type: cgi-bin: php-cli: php.ini: custom: status:
cgi 5.4.16 by OS vendor 5.4.16 5.4 cgi /usr/bin/php-cgi /usr/bin/php /etc/php.ini false disabled
fastcgi 5.4.16 by OS vendor 5.4.16 5.4 fastcgi /usr/bin/php-cgi /usr/bin/php /etc/php.ini false disabled
fpm 5.4.16 by OS vendor 5.4.16 5.4 fpm /usr/sbin/php-fpm /usr/bin/php /etc/php.ini false disabled
module 5.4.16 by OS vendor 5.4.16 5.4 module /usr/bin/php-cgi /usr/bin/php /etc/php.ini false disabled
plesk-php54-cgi 5.4.45 5.4.45 5.4 cgi /opt/plesk/php/5.4/bin/php-cgi /opt/plesk/php/5.4/bin/php /opt/plesk/php/5.4/etc/php.ini true disabled
plesk-php54-fastcgi 5.4.45 5.4.45 5.4 fastcgi /opt/plesk/php/5.4/bin/php-cgi /opt/plesk/php/5.4/bin/php /opt/plesk/php/5.4/etc/php.ini true enabled
plesk-php54-fpm 5.4.45 5.4.45 5.4 fpm /opt/plesk/php/5.4/sbin/php-fpm /opt/plesk/php/5.4/bin/php /opt/plesk/php/5.4/etc/php.ini true enabled
plesk-php55-cgi 5.5.38 5.5.38 5.5 cgi /opt/plesk/php/5.5/bin/php-cgi /opt/plesk/php/5.5/bin/php /opt/plesk/php/5.5/etc/php.ini true disabled
plesk-php55-fastcgi 5.5.38 5.5.38 5.5 fastcgi /opt/plesk/php/5.5/bin/php-cgi /opt/plesk/php/5.5/bin/php /opt/plesk/php/5.5/etc/php.ini true enabled
plesk-php55-fpm 5.5.38 5.5.38 5.5 fpm /opt/plesk/php/5.5/sbin/php-fpm /opt/plesk/php/5.5/bin/php /opt/plesk/php/5.5/etc/php.ini true enabled
plesk-php56-cgi 5.6.34 5.6.34 5.6 cgi /opt/plesk/php/5.6/bin/php-cgi /opt/plesk/php/5.6/bin/php /opt/plesk/php/5.6/etc/php.ini true disabled
plesk-php56-fastcgi 5.6.34 5.6.34 5.6 fastcgi /opt/plesk/php/5.6/bin/php-cgi /opt/plesk/php/5.6/bin/php /opt/plesk/php/5.6/etc/php.ini true enabled
plesk-php56-fpm 5.6.34 5.6.34 5.6 fpm /opt/plesk/php/5.6/sbin/php-fpm /opt/plesk/php/5.6/bin/php /opt/plesk/php/5.6/etc/php.ini true enabled
plesk-php70-cgi 7.0.28 7.0.28 7.0 cgi /opt/plesk/php/7.0/bin/php-cgi /opt/plesk/php/7.0/bin/php /opt/plesk/php/7.0/etc/php.ini true disabled
plesk-php70-fastcgi 7.0.28 7.0.28 7.0 fastcgi /opt/plesk/php/7.0/bin/php-cgi /opt/plesk/php/7.0/bin/php /opt/plesk/php/7.0/etc/php.ini true enabled
plesk-php70-fpm 7.0.28 7.0.28 7.0 fpm /opt/plesk/php/7.0/sbin/php-fpm /opt/plesk/php/7.0/bin/php /opt/plesk/php/7.0/etc/php.ini true enabled
plesk-php71-cgi 7.1.15 7.1.15 7.1 cgi /opt/plesk/php/7.1/bin/php-cgi /opt/plesk/php/7.1/bin/php /opt/plesk/php/7.1/etc/php.ini true disabled
plesk-php71-fastcgi 7.1.15 7.1.15 7.1 fastcgi /opt/plesk/php/7.1/bin/php-cgi /opt/plesk/php/7.1/bin/php /opt/plesk/php/7.1/etc/php.ini true enabled
plesk-php71-fpm 7.1.15 7.1.15 7.1 fpm /opt/plesk/php/7.1/sbin/php-fpm /opt/plesk/php/7.1/bin/php /opt/plesk/php/7.1/etc/php.ini true enabled
plesk-php72-cgi 7.2.3 7.2.3 7.2 cgi /opt/plesk/php/7.2/bin/php-cgi /opt/plesk/php/7.2/bin/php /opt/plesk/php/7.2/etc/php.ini true disabled
plesk-php72-fastcgi 7.2.3 7.2.3 7.2 fastcgi /opt/plesk/php/7.2/bin/php-cgi /opt/plesk/php/7.2/bin/php /opt/plesk/php/7.2/etc/php.ini true enabled
plesk-php72-fpm 7.2.3 7.2.3 7.2 fpm /opt/plesk/php/7.2/sbin/php-fpm /opt/plesk/php/7.2/bin/php /opt/plesk/php/7.2/etc/php.ini true enabled
========================

As you can see all CGI handlers are set to disabled. The migration manager should obviously not be assigning domains to handlers which are disabled.

These handlers can't be removed as they're part of packages which result in the message "Unable to remove the PHP handler: Handler with id = (whatever) is provided by some package" so outright removing them isn't viable either.

 

[ChristophRo]

I do actually like that behavior, as Plesk does some obscure "best-match" here anyway when the exact identical php handler does not exist on the target system and this does often result in a bad choice.
So as it is now, I can easily identify the sites that require manual intervention (cause they have one of the disabled handlers assigned) and change them to the handler that is really the best match for them.

 

[Enverex]

Relying on broken behaviour is never a good idea though.

If you need a list of those sites then the migration manager tells you what they are beforehand.