I am a relatively new Admin. learning more and more each day. But my past experiences with Ensim trouble me.
I recently paid SW-Soft to upgrade our Plesk 8.0.1 boxes to 8.1.0 and they failed to do the mySQL upgrade that I figured was part of it. They now tell me I figured wrong
You don't want that rpm, you don't even want that channel really. By default Plesk installs whatever version of MySQL ships with the OS you're running. Since your running FC2 that's MySQL 3.23, a Plesk upgrade won't change that.
The old, frozen atomic yum repository at http://3es.atomicrocketturtle.com/ has MySQL 4.1 packages for FC2 that are compatible with Plesk. Follow the installation instructions on that page for the atomic channel and then you can 'yum update mysql' to get ART's MySQL 4.1 packages.
FC2 is no longer supported by ART though and has been EOL for a while now, so you might want to look into migrating to a supported platform.
Thanks for the reply. I visited the old site and don't find mysql anywhere. Sadly, our now gone "crack Admin." chose to install FC 1 and FC 2 on machines as recently as 1 year ago. We're now somewhat stuck. I am getting new boxes deployed with CentOS 4.3 but I am told that the Plesk installation cannot just be moved over. It means a complete migration and customer inconvenience.
If you're running Plesk 8.1 you shouldn't have any problems (other than the downtime associated with rebuilding the box) in moving Plesk to a new distro. Do a complete backup in the command line using Plesk
/usr/local/psa/bin/pleskbackup all /path/to/backup
Save that offsite somewhere and then do your rebuild in CentOS and reinstall Plesk. Then restore from your backup and you should be back in business in as little as 3-4 hours.
If you need some tips on how to get back up and running faster you can check out this thread
We run Plesk on top of a VE so the backup process (I am told) is slightly different. HSP maintains control of both. I'll tell you this: HSP has been more of a hassle than anything else and "support" leaves much to be desired.
Let me ask this: is a yum update of mysql safe onto the current distro?
Virtual servers are always a bit trickier. I have used ART MySQL 4.1 packages on FC2 in the past a lot though. Make sure your /etc/my.cnf has old_passwords=1 before restarting MySQL after the upgrade (the upgrade will probably install an /etc/my.cnf.rpmnew file).
(Sidenode: why are virtual servers somehow always running EOL'd versions of Fedora Core?)
Well, with Ensim as an excellent example -- Ensim failed to, or refused to, integrate mySQL 4.x into its Webppliance. With Ensim mySQL is *tightly* inetgrated. Plesk, on the other hand, installs mySQL x.xx as part of the OS but Plesk still has to integrate to some extent. SW-Soft tells me that 8.1.0 supports mySQL 4.x and 5.x when Plesk 8.0.1 did not. So, if you had Plesk 8.0.1 a lesser OS was used. You knew it worked with many applications and not just mySQL. For maximum compatibility *at the time of install* SysAdmin's like to cut corners and install on EOL'd OS's. And then guys like me that own the business have to play catch-up after the corner-cutter bails.
