Applicable to:
- Plesk for Linux
Symptoms
-
Full server backup in Plesk is created with the following warning:
PLESK_WARN: Warning: Application "WordPress"
Unable to back up database #25. Error: Unable to find row with id in data_bases table. -
The following fragment can be found in
/var/log/plesk/PMM/backup-<timestamp>/backup.log:CONFIG_TEXT: [2022-03-02 16:38:52.252|22889] DEBUG [panel] Finish: Domain: example.com
[2022-03-02 16:38:52.269|22889] DEBUG [panel] Start: Application: WordPress
...
[2022-03-02 16:38:52.300|22889] DEBUG [panel] Requested existing resource, ID: ebf59913-084f-4321-b816-279307946427
Cause
Database inconsistency. An application has been removed from a subscription, but records related to this application were left over in the apsc and/or psa database.
MYSQL_LIN: select * from apsResources where pleskId=25;
+----+--------------------------------------+------------+---------+
| id | registryId | pleskType | pleskId |
+----+--------------------------------------+------------+---------+
| 11 | ebf59913-084f-4321-b816-279307946427 | db | 25 |
| 12 | ebf59913-084f-4321-b816-279307946427 | db-user | 25 |
MYSQL_LIN: MariaDB [apsc]> select aps_registry_object.uid from aps_registry_object join aps_application on aps_application.registry_object_id=aps_registry_object.id where aps_application.id=(select aps_resource.app_id from aps_resource join aps_resource_adjacency_list on aps_resource.id=aps_resource_adjacency_list.dependent_resource_id where aps_resource_adjacency_list.base_resource_id=(select aps_resource_adjacency_list.base_resource_id from aps_resource_adjacency_list join aps_resource on aps_resource.id=aps_resource_adjacency_list.base_resource_id join aps_registry_object on aps_resource.registry_object_id=aps_registry_object.id where aps_registry_object.uid='ebf59913-084f-4321-b816-279307946427'));
+--------------------------------------+
| uid |
+--------------------------------------+
| 7c05f8de-a84a-44f9-b616-2efca1143908 |
+--------------------------------------+
1 row in set (0.003 sec)
MYSQL_LIN: MariaDB [psa]> select * from apsResources where registryId='7c05f8de-a84a-44f9-b616-2efca1143908';
Empty set (0.001 sec)
Note: there can be empty output in the query above or some records with this registryId may be present in the psa database.
Resolution
-
Connect to the server via SSH.
-
Execute the command below to fix inconsistencies:
# plesk repair db
-
Connect to the server via SSH.
-
Back up the apsc and psa databases:
# plesk db dump apsc > apsc_backup.$(date +%F_%R).sql
# plesk db dump psa > psa_backup.$(date +%F_%R).sql
-
Access plesk db:
# plesk db
-
Switch to the apsc database:
# use apsc;
-
Check the lines that should be removed:
MYSQL_LIN: MariaDB [apsc]> select * from aps_registry_object where uid='ebf59913-084f-4321-b816-279307946427';
+----+--------------------------------------+--------------+---------------------+---------+
| id | uid | type | creation_time | enabled |
+----+--------------------------------------+--------------+---------------------+---------+
| **63 **| ebf59913-084f-4321-b816-279307946427 | aps.resource | 2018-05-02 23:22:15 | y |
+----+--------------------------------------+--------------+---------------------+---------+
1 row in set (0.001 sec)
MariaDB [apsc]> select * from aps_resource where registry_object_id=63;
+----+--------------------+--------------------+------------+---------------+--------+
| id | registry_object_id | parent_resource_id | service_id | resource_type | app_id |
+----+--------------------+--------------------+------------+---------------+--------+
| 27 | 63 | NULL | | aps.database | NULL |
+----+--------------------+--------------------+------------+---------------+--------+
1 row in set (0.001 sec)
MariaDB [apsc]> select * from aps_resource_adjacency_list where base_resource_id=27;
+----+------------------+-----------------------+----------+------------------+--------+----------------+
| id | base_resource_id | dependent_resource_id | relation | uniqueness_scope | branch | requirement_id |
+----+------------------+-----------------------+----------+------------------+--------+----------------+
| 18 | 27 | 25 | e | | NULL | main |
+----+------------------+-----------------------+----------+------------------+--------+----------------+ -
Remove the lines:
MYSQL_LIN: delete from aps_resource_adjacency_list where base_resource_id=27;
delete from aps_resource where registry_object_id=63;
and
delete from aps_registry_object where uid='ebf59913-084f-4321-b816-279307946427'; -
If there were some records in
psadatabase remove them:MYSQL_LIN: use psa;
MYSQL_LIN: delete from apsResources where registryId='ebf59913-084f-4321-b816-279307946427';
-
Run the repair again:
# plesk repair db
Comments
1 comment
We have this problem. Does it mean that the database has not backed up at all (as it seems to say)?
Running # plesk repair DB gave us: ~
Inconsistency in the table 'ServiceNodeConfiguration' for theparameter 'outgoing_email_mode_explicit_ip_v4': No rows in the table'IP_Addresses' with id = 1 ........................................ [ERROR]Switch Outgoing mail mode to send from domain IP addresses? [Y/n] nSo we have switched ougoing mail mode to send from domain IP addresses (as it made no difference to us) and run # plesk database repair. Now the repair gives us no errors but still the backup gives us this peculilarly uninformative error:
Unable to back up database #. Error: Unable to find row with id in data_bases table.
Any help from those more versed in plesk and database backup would be highly appreciated.
Please sign in to leave a comment.