• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Mysql 3.2 to 4.0 upgrade problems

K

KXRM

Guest
I upgraded mysql to 4.0 using the mysql.com rpms. I can't use atomic turtle because yum doesn't work due to some weird problem in the python setup on my particular machine also I am running RH 7.3 which he no longer supports, so that is a no go.

My problem is the upgrade went ok and everything works fine except if I do any auto updates in plesk it reverts mysql back to 3.2

So something about the mysql 4.0 rpms is obviously different from what plesk expects. Could anyone tell me exactly how to get plesk to start using mysql 4.0?
 
Back
Top