• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Question plesk repair "Checking and restoring users" for every domain?

G J Piper

Regular Pleskian
Server operating system version
AlmaLinux 8.9 x86_64
Plesk version and microupdate number
18.0.57.2
I get this result now every time I run plesk repair all -n which I do each morning to check the status:

Code:
plesk repair all -n
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database ...................... [OK]
Checking system users ............................................... [OK]
Checking Linux system files ......................................... [OK]
Checking virtual hosts' file system ................................. [OK]
Checking the status of the required Apache modules .................. [OK]
Checking the configuration of Apache modules ........................ [OK]
Checking web server configuration. Please wait ...................... [OK]
Checking the usage of PHP handlers .................................. [OK]
Checking for obsolete PHP-FPM configuration files ................... [OK]
Repairing the mail server configuration ............................. [OK]
Checking the DNS configuration file ................................. [OK]
Checking the user DNS configuration file ............................ [OK]
Restoring DNS server configuration .................................. [OK]
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]
Checking and restoring users for the domain domain.org ........ [OK]
Checking and restoring users for the domain domain.com ....... [OK]
Checking and restoring users for the domain domain.com ......... [OK]
Checking and restoring users for the domain domain.net ................ [OK]
Checking and restoring users for the domain domain.com ........ [OK]
Checking and restoring users for the domain domain.com ........... [OK]
Checking and restoring users for the domain domain.com ............ [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

It lists Checking and restoring users for the domain domain.org ........ [OK]
for every domain on the entire server now. It never used to do that before 18.0.57
 
Hi @G J Piper , if your question is whether repair is supposed to do something new, then probably yes, it is doing something new. Is there any technical issue with this?
 
Hi @G J Piper , if your question is whether repair is supposed to do something new, then probably yes, it is doing something new. Is there any technical issue with this?
Not so much an issue but it does make the output a bout a mile long when you have dozens of domains hosted. I wondered if it is finding something unusual with my server or if this is now the new normal.
 
Back
Top