Dukemaster
Regular Pleskian
Hi,
I just performed an overall test by # plesk repair all -n with the following result:
1. Is there another way to repair it, for the reason that perhaps the 2 rows are needed in future?
2. Or, do you suggest the recommended solution with "Remove unnecessary rows from the table 'ModuleSettings'?" and hitting Y for YES
I just performed an overall test by # plesk repair all -n with the following result:
Code:
Checking the consistency of the Plesk database
Inconsistency in the table 'ModuleSettings' for the column
module_id: No rows in the table 'Modules' with = 13 (2 broken
references) ....................................................... [WARNING]
To see more details, run the command in the verbose mode: plesk repair db -verbose
Checking system users ............................................... [OK]
Code:
root@server:~# plesk repair db -verbose
Checking the Plesk database using the native database server tools
Run query: CHECK TABLE accounts
Run query: CHECK TABLE actions
Run query: CHECK TABLE admin_aliases
Run query: CHECK TABLE admin_aliases_param
Run query: CHECK TABLE anon_ftp
.......
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database
Inconsistency in the table 'ModuleSettings' for the column
module_id: No rows in the table 'Modules' with = 13 (2 broken
references) ....................................................... [WARNING]
Broken references in table 'ModuleSettings':
*************************** 1. row ***************************
module_id: 13
name: eventStatus_activated
value: true
*************************** 2. row ***************************
module_id: 13
name: eventStatus_enabled
value: true
Remove unnecessary rows from the table 'ModuleSettings'? [Y/n]
1. Is there another way to repair it, for the reason that perhaps the 2 rows are needed in future?
2. Or, do you suggest the recommended solution with "Remove unnecessary rows from the table 'ModuleSettings'?" and hitting Y for YES