• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Plesk repair -all error

rmannkoko

New Pleskian
Server operating system version
Ubuntu 22.04 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.55.0
Plesk worked when i wanted to install docker akeneo on my Ubuntu VPS and then, i have some problems with plesk . Please Help me .
That is results of plesk repair -all :
....................
Checking the consistency of the Plesk database

Inconsistency in the table 'smb_users' for the column roleId: No
rows in the table 'smb_roles' with id = 1 ......................... [ERROR]

Inconsistency in the table 'IP_Addresses' for the column
ssl_certificate_id: No rows in the table 'certificates' with id = 0
(3 broken references) ............................................. [ERROR]
Assign the default SSL/TLS certificate to the IP address? [Y/n] Y
Creating a database dump ........................................ [OK]
A dump of the database was created before an attempt to repair the database: /var/lib/psa/dumps/mysql.preresolve.20230902-012026.dump.gz
Assigning the default SSL/TLS certificate to the IP address ..... [FAILED]
- Unable to find row with id 0 in certificates table.

Wrong APS database configuration .................................. [ERROR]

Inconsistency in the table 'misc' for the parameter
'default_certificate_id': No rows in the table 'certificates' with
id = 0 ............................................................ [ERROR]

Checking system users

The system user 'zacharia.com_u5znuc9rdq' belongs to the Plesk group
or is associated with a home directory at a virtual host but is
absent in Plesk ................................................... [WARNING]
Remove the system user 'zacharia.com_u5znuc9rdq'? Note that the user's home directory /var/www/vhosts/zacharia.fr will be preserved. [Y/n] Y
Removing the system user 'zacharia.com_u5znuc9rdq' .............. [FIXED]

Checking Linux system files ......................................... [OK]

Checking virtual hosts' file system ................................. [OK]

Checking Plesk version .............................................. [OK]

Checking Apache configuration ....................................... [OK]

Checking for custom configuration templates ......................... [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object
................................................................... [OK]

Checking the status of the required Apache modules .................. [OK]

Checking the configuration of Apache modules ........................ [OK]

Checking web server configuration

Reinstall SSL/TLS certificates and set the default certificate for all IP addresses? [Y/n] Y
Reinstalling SSL/TLS certificates ............................... [OK]
Applying the default SSL/TLS certificate to all IP addresses .... [OK]

Repair web server configuration for all domains? [Y/n] Y
Repairing web server configuration for all domains. This aspect
can be used with individual domains ("plesk repair web
example.com"), and on the server level ("plesk repair web") ..... [OK]

Repair server-wide configuration parameters for web servers? [Y/n] Y
Repairing server-wide configuration parameters for web servers .. [OK]

Checking the usage of PHP handlers .................................. [OK]

Checking for obsolete PHP-FPM configuration files ................... [OK]

Repairing the mail server configuration

Reconfigure all domains and mailboxes? [Y/n] Y
Reconfiguring all domains and mailboxes ......................... [2023-09-02 01:21:06.415] 1336591:64f28def86d15 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/mchk'] with exit code [1]
[FAILED]
- mchk failed: ==> Checking for: mailsrv_conf_init... ok
==> Checking for: mail_handlers_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... fail
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... not found, skipped
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_imap_restore... ok
==> Checking for: mail_add_from_restore... ok
==> Checking for: mail_spam_restore... ok
==> Checking for: mail_grey_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_dmarc_restore... ok
==> Checking for: mail_drweb_restore... ok
==> Checking for: mail_outgoing_restore... fail
==> Checking for: mail_transport_restore... ok
Errors occured in mail restore procedure
Some utilities have exited with errors:
/usr/lib/plesk-9.0/mail_admin_aliases
Admin e-mail address is not defined in Plesk database yet
System error 11: Resource temporarily
unavailable/usr/lib/plesk-9.0/remote_mail_restore/mail_outgoing_restore
[2023-09-02 01:21:05.910] 1344604:64f28e01ddced ERR
[util_exec] proc_close() failed
['/opt/psa/admin/bin/mail_outgoing_restore.worker' '--start'
'--finish'] with exit code [1]
Error: START httpd_modules_ctl --disable sysenv
ERROR: Module sysenv does not exist!
resource(s) deleted
Command '['/opt/psa/admin/sbin/httpd_modules_ctl',
'--disable', 'sysenv']' returned non-zero exit status 1.

Checking the DNS configuration file ................................. [OK]

Checking the user DNS configuration file

Restore the user DNS configuration file from the template? [Y/n] Y
Restoring the user DNS configuration file ....................... [FIXED]

Restoring DNS server configuration

Synchronize DNS zones with the DNS server? [Y/n] Y
Synchronizing DNS zones with the DNS server ..................... [OK]

Checking MySQL database servers ..................................... [OK]

Repair databases on available servers ............................... [OK]

Repair database users on available servers .......................... [OK]

Error messages: 4; Warnings: 1; Errors resolved: 2



exit status 1
 
The number of errors could mean that either a user account was incompletely removed during an ordinary removal process or that something interfered with user accounts or the psa database externally. Could yo please check if there are any entries in the "certificates" table at all?
plesk db -e 'select id, name from certificates;'
should output at least one row. What is the result?
 
The number of errors could mean that either a user account was incompletely removed during an ordinary removal process or that something interfered with user accounts or the psa database externally. Could yo please check if there are any entries in the "certificates" table at all?
plesk db -e 'select id, name from certificates;'
should output at least one row. What is the result?
Thanks for the answer !
plesk db -e 'select id, name from certificates;' is nothing shows nothing . it's empty .
 
That's a bad situation, because we cannot just copy a valid entry to use as a temporary certificate. You can try at least two things here:

1) If you can still login to Plesk you can try to create a Let's Encrypt SSL certificate for any domain. If that works, you can then copy the dataset in the table `psa`.`certificates`and change the id of the copy to "0". Then run repair again.

2) You can replace the existing psa database content with a previous daily dump from the /dumps directory (e.g. find dumps directory: grep DUMP_D /etc/psa/psa.conf, then import a mysql.daily.dump.?.gz from the /dumps directory as described in https://support.plesk.com/hc/en-us/articles/12376967822231 . Then run repair again.

3) The other issue with the missing user seems odd to me. So maybe it is best to neither try (1), nor (2) but to instead hand it over to support so that they can check and fix the issue directly on your server. https://support.plesk.com, and in case you bought your license form a reseller: https://support.plesk.com/hc/en-us/articles/12388090147095
 
Back
Top