• 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.

Side-effect of update to Plesk 11: mysqlcheck won't run using admin user

SacAutos

Regular Pleskian
I have a VM at a hosting provider that unfortunately freezes now and then. When I does, I log into their server admin panel, reboot the VM and log in via the command line and use mysqlcheck to repair the database tables of a couple of touchy customer sites.

However, since the upgrade to Plesk 11, I can't do that any more using a command like this:

mysqlcheck -uadmin -p customer_db --auto_repair

where my password was the admin panel password. Now I have to use the specific database username and password. Not a large deal but I hate having to create a shell command file and leave it someplace where it could be found.

Does this have anything to do with that security question after the 10 to 11 upgrade? I went for that...
 
It was "enhanced security mode"

That was the irrevocable question that I answered. Does anyone know if this "enhanced security mode" might have anything to do with my question?
 
Use direcctly the cat /etc/psa/.psa.shadow password encrypted, not in clear and will work.
 
Back
Top