• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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