Search Engine: Elastic

Article ID: 115637, created on Mar 4, 2013, last review on May 10, 2014

  • Applies to:
  • Plesk Automation


Parallels Plesk Automation cannot provision subscriptions with database resources to Parallels Plesk Panel 10.x service nodes, assimilated to Parallels Plesk Automation infrastructure:

The node pp10.vendor.tld (3) selected for allocating the database service does not provide the support for ppa_mysql.


Plesk 10.x servers, assimilated into Parallels Plesk Automation infrastructure as service nodes do not have required database service package installed, despite actual service being up and running and hosting databases for existing subscriptions.

Previously, provisioning process did not check for presence of database service package on the server. However, this check has been introduced in the update #6 (Parallels Plesk Automation 11.1 MU #6). Now, provisioning task may fail, if subscription includes "Database Service" resource type but target service node has no package representing database service installed.


Newly assimilated Parallels Plesk Panel service nodes will have proper set of packages, corresponding to provided services, installed.

To fix provisioning for nodes that are already present in Parallels Plesk Automation:

  1. Find the node in InfrastructureService Nodes.

  2. Find out required database service type (MySQL, MSSQL or PostgreSQL) for this server on InfrastructureDatabase servers screen.

  3. On InfrastructureService Nodesservice node Packages tab press Install Package button and find required package, corresponding to the type of database server already installed on the node:

    • ppa_mysql for MySQL
    • ppa_pgsql for PostgreSQL
    • ppa_mssql for MSSQL
  4. Click on the Install icon (), then on Properties ( ) and enter database server's administrator username and password.

    Important: valid database administrator credentials are required. If you do not remember login/password, change them with database management tools and then update login/password on Infrastructure Database servers.

  5. Press Submit and then Finish to start installation.

  6. Go to SystemTask Manager and find failed task "Register the remote 'mysql' DB server". Message "A database server with this combination of host address and port number is already registered."  will be in the output. This is expected result, since database server is already registered in Parallels Plesk Automation.

  7. Cancel failed task and its dependencies with Cancel Task Tree button.

  8. Go back to InfrastructureService Nodes and verify, that package is installed on the node (Packages tab of service node properties).

  9. Assign necessary provisioning attribute (MySQL, Microsoft SQL or PostgreSQL) to the node at InfrastructureService NodesChange attributes

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF