Unable to back up APS controller data. Error: resource of type aps.database with id not found by brokers

Symptoms

Unable to create a backup on server:

PLESK_ERROR: Unable to back up APS controller data. Error: resource of type aps.database with id 1c66b3c2-4fe3-4ede-ad4f-c5bf66cd6dc6 not found by brokers

Cause

Configuration leftovers on APSC database

Resolution

• Unable to create a backup on server:

  PLESK_ERROR: Unable to back up APS controller data. Error: resource of type aps.database with id 1c66b3c2-4fe3-4ede-ad4f-c5bf66cd6dc6 not found by brokers

• Error in Plesk GUI grey:
  

  PLESK_INFO: Error or message on white/gray background in Plesk

• Error in logs:
  

  CONFIG_TEXT: logs content

• Plesk Warning:
  

  PLESK_WARN: warning text in Plesk

1. Connect to the Plesk server via SSH.

2. Backup APSC and PSA databases:

   # plesk db dump psa > psa.backup.sql
   # plesk db dump apsc > apsc.backup.sql

3. Find IDs to be removed using uid from the error:
   

   CONFIG_TEXT: MariaDB [psa]> use apsc
   Reading table information for completion of table and column names
   You can turn off this feature to get a quicker startup with -A
   Database changed
   MariaDB [apsc]> select * from aps_registry_object where uid='1c66b3c2-4fe3-4ede-ad4f-c5bf66cd6dc6';
   +----+--------------------------------------+--------------+---------------------+---------+
   | id | uid | type | creation_time | enabled |
   +----+--------------------------------------+--------------+---------------------+---------+
   | 16 | 1c66b3c2-4fe3-4ede-ad4f-c5bf66cd6dc6 | aps.resource | 2018-11-19 12:22:07 | y |
   +----+--------------------------------------+--------------+---------------------+---------+
   1 row in set (0.000 sec)
   MariaDB [apsc]> select * from aps_resource where registry_object_id=16;
   +----+--------------------+--------------------+------------+---------------+--------+
   | id | registry_object_id | parent_resource_id | service_id | resource_type | app_id |
   +----+--------------------+--------------------+------------+---------------+--------+
   | 3 | 16 | NULL | | aps.database | NULL |
   +----+--------------------+--------------------+------------+---------------+--------+
   1 row in set (0.015 sec)
   MariaDB [apsc]> select * from aps_resource_adjacency_list where base_resource_id=3;
   +----+------------------+-----------------------+----------+------------------+--------+----------------+
   | id | base_resource_id | dependent_resource_id | relation | uniqueness_scope | branch | requirement_id |
   +----+------------------+-----------------------+----------+------------------+--------+----------------+
   | 2 | 3 | 1 | e | | NULL | main |
   +----+------------------+-----------------------+----------+------------------+--------+----------------+
   1 row in set (0.025 sec)

4. Delete the orphaned registers, removing IDs using uid from the error:

   CONFIG_TEXT: MariaDB [psa]> use apsc
   Reading table information for completion of table and column names
   You can turn off this feature to get a quicker startup with -A
   Database changed
   MariaDB [apsc]> delete from aps_resource_adjacency_list where base_resource_id=3;
   Query OK, 1 row affected (0.001 sec)
   MariaDB [apsc]> delete from aps_resource where registry_object_id=16;
   Query OK, 1 row affected (0.023 sec)
   MariaDB [apsc]> delete from aps_registry_object where id=16;
   Query OK, 1 row affected (0.074 sec)