• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Unable to back up APS controller data.

Powie

Regular Pleskian
Any idea? On daily backups this log entry is generated:

Warning: Application "joomla"
Unable to back up APS controller data. Error: resource of type aps.environment with id f878015c-8d3a-4c3b-a90f-613f3ae1c961 not found by brokers

Tryed plesk repair db, but this doesn't help.
 
It is APSC database inconsistency. Try to fi it with the following steps (here is just an example, please use your id f878015c-8d3a-4c3b-a90f-613f3ae1c961):

Login to psa database:

Code:
# plesk db

Change the database to apsc:

Code:
use apsc;
Database changed

Find IDs to be removed using uid from the error:

Code:
select * from aps_registry_object where uid='c283f909-ffa8-4b4a-a67c-58ee924f3ce2';
+------+--------------------------------------+--------------+---------------------+---------+
| id   | uid                                  | type         | creation_time       | enabled |
+------+--------------------------------------+--------------+---------------------+---------+
| 2522 | bb5d51e0-4f09-44f1-a072-2bc3ca959b7c | aps.resource | 2014-05-15 23:52:17 | y       |
+------+--------------------------------------+--------------+---------------------+---------+

select * from aps_resource where registry_object_id=2522;
+------+--------------------+--------------------+------------+---------------+--------+
| id   | registry_object_id | parent_resource_id | service_id | resource_type | app_id |
+------+--------------------+--------------------+------------+---------------+--------+
| 2085 | 2522               | NULL               |            | aps.database  | NULL   |
+------+--------------------+--------------------+------------+---------------+--------+

select * from aps_resource_adjacency_list where base_resource_id=2085;
+------+------------------+-----------------------+----------+------------------+--------+----------------+
| id   | base_resource_id | dependent_resource_id | relation | uniqueness_scope | branch | requirement_id |
+------+------------------+-----------------------+----------+------------------+--------+----------------+
| 1531 | 2085             | 2083                  | e        |                  | NULL   | main           |
+------+------------------+-----------------------+----------+------------------+--------+----------------+

Remove the data using IDs above:

Code:
delete from aps_resource_adjacency_list where base_resource_id=2085;
delete from aps_resource where registry_object_id=2522;
delete from aps_registry_object where id=2522;
 
Thanks for this, It seems that this fixes the issue.
It seems that also the database was linked to the wrong user account.

Error:
Warning: Database "joomla_8"
The database 'joomla_8' belongs to the other subscription 'xxxxxxxxxx' and cannot be backed up. To fix it reassign the database via the command 'plesk bin database --assign-to-subscription joomla_8 -domain xxxxx -server localhost:3306'.

Moved the database, backups state xis green now
 
Back
Top