Search Engine: Elastic

Article ID: 131967, created on Dec 25, 2017, last review on Dec 28, 2017

  • Applies to:
  • Operations Automation 7.1
  • Operations Automation 7.2

Symptoms

  1. Task "Execute operation 'provisionWebsite'" for Provisioning WebHosingPlesk subscription failed with error:

    There are no compatible Plesk nodes for provisioning: Nodes that do not meet the requirements
    

    In log /var/log/shm-dispatcher/dispatcher.log on Plesk Management Node can be found the corresponding message, for example:

    The node 192.0.2.20 does not meet the following hosting service requirements: Array
    (
        [0] => Odin\ShmWebDispatcherBundle\Aps\Resource\StructureProperty Object
            (
                [name] => php.handlerVersion
                [class] => setting
                [type] => enum
                [value] => fpm/plesk-php71-fpm/apache/7.1.9
            )
    
    )
    
  2. WebHosting Plesk Linux Service Template is configured to use particular version of PHP, e.g. 7.1.9.

  3. Plesk nodes were updated recently. New PHP version, e.g. 7.1.12, was installed on the Plesk node.

Cause

By design, system automatically picks PHP version from node only in case the parameter Latest available PHP version is set in PCP > Products > Service Templates > WebHosting Plesk Linux Template > Hosting Parameters > Run PHP as.

In case if the particular version of PHP is specified, WebHosting Plesk module relies on the value, specified in the Template, leading to error, since such version is not available on the node anymore.

Resolution

  1. In PCP > Products > Service Templates > WebHosting Plesk Linux Template > Hosting Parameters change Run PHP as parameter to Latest available PHP version or to new updated version;
  2. In PCP > Products > Service Templates > WebHosting Plesk Linux Template > Synchronize check and synchronize the required subscriptions;
  3. Restart failed task.

31987597efff5a3a9ce779cc203bbe5e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF