• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

[atomic] Mysql 5.1 for Plesk

If one wants to stay with MySQL 5.0 for some time, how do you do that still using the Atomic repo?

Thanks.
 
The package is still available in the repo, you can try specifying the exact version when you invoke yum. I dont know how much longer it will stick around in the repo though.
 
Thanks, it would be great if you could keep the MySQL 5.0 packages in the repo for a few months, I think other users may need them too.
 
I installed MySQL thru Atomic, and `mysql --version` now returns:
Code:
mysql  Ver 14.14 Distrib 5.1.48, for redhat-linux-gnu (i686) using readline 5.1

Plesk (9.5.2) reports 'mysql 5.1.48-1.el4.art' within the 'Server Components' page.

However, phpinfo() still returns:
Code:
mysql
MySQL Support enabled 
Active Persistent Links  0  
Active Links  0  
Client API version  4.1.22  
MYSQL_MODULE_TYPE  external  
MYSQL_SOCKET  /var/lib/mysql/mysql.sock  
MYSQL_INCLUDE  -I/usr/include/mysql  
MYSQL_LIBS  -L/usr/lib/mysql -lmysqlclient

MySQL as returned by mysql_get_server_info() returns the correct version.

What do I need to do to ensure that this is all operating correctly? I'm afraid that the client API might cause problems.

If it matters, I'm running RHEL4.
 
On a few server I have updated, where I know that is no unicode characters, that was in the past an issue. Where I have updated, all is OK. Now I prepapre the rest of the server to upgrade, hope all will be OK.
 
Back
Top