• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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