• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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