• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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