Upgrading to MySQL 5.0.38 on RHEL and CentOS
March 26, 2007 by Jason · 14 Comments
Well, MySQL has released another Enterprise-only version. Not only are there no binary packages for the community, but they haven't even bothered to post a link to the source on the download page. Why they do this, I don't know, because it would really only take another 15 seconds to update the link to the source package on the community release page. As it stands, in order for someone to find out about this release they'd either have to be crawling the MySQL FTP site or watching the Enterprise edition release logs.
In any case, not to be left behind just because I "can't afford"/"refuse to pay" $600 (minimum) per server, I have once again built packages to provide a community release of the newest stable version of MySQL.
This release was a bit more work than the last few. It seems that MySQL actually fixed a few of the bugs that Red Hat's engineers had been patching so it was necessary to remove a few of the manual patches. However, it also seems that they managed to change a good amount of code but still manage NOT to fix some of the other "bugs" that were being patched. That said, it was necessary to recreate a few of the patches in order to get them to work on the current source tree. Finally, I added a bunch of new files to the mysql-server and mysql-test packages.
With the recent introduction of my yum repository, I will no longer be providing compiled binary packages in my posts. The Source RPM will still be here if you'd like to use it (just to see what I've done or perhaps to compile for some architecture other than i386 or x86_64). If you'd like to download the binary release for either the i386 or x86_64 architectures then I'd suggest adding my yum repository to your system. It'll only take you a few minutes and it should make your life a LOT easier when it comes to keeping up with my system updates.
Update (9/24/2009): Packages deleted, use the yum repository instead.
Thanks!
Thanks - Very much appreciated!
Of course, for us to fix any of the "bugs" that are patched in the RedHat distribution, they need to be filed in our bugs system (along with patch) and go through the proper process.
That is true, although since I don't work for RedHat, and I don't have much spare time to do the research myself, I am really forced to assume that they are actually filing bug reports... If they're not, they've really only got themselves to blame for creating extra work each time they roll out an updated package. 🙂
Thank you, this is sweet.
I found that going from a stock CentOS build to this release of MySQL requires that the stock CentOS version of mysqld be started (and then shut it down) before upgrading. Files are built that are required by 5.0.38, otherwise 5.0.38 won't start.
Interesting, I'll have to take another look at the spec files for the default version and for this release of 5.0.38; maybe there was an init script or something that used to be run that isn't now.
I just had this happen as well...I uninstalled stock mysql that was installed via a fresh centos 4.4 install. I never ran it. Then I installed the packages here for x_86 (thank you!). Then...
[[email protected] ~]# /etc/init.d/mysqld start
Initializing MySQL database: FATAL ERROR: Could not find SQL file '/usr/share/mysql/mysql_system_tables.sql' in
/usr/share/mysql or inside /usr
[FAILED]
slocate couldnt mysql_system_tables.sql either. Just a heads up.
Thanks,
Steve
Interestingly enough, it seems that that file has been packaged in the "mysql-test" package. If it is needed by mysqld then it should be in the "mysql-server" package. I'll look into this today and update the packages if necessary, thanks for providing more info.
The mysql packages in my yum repository have been updated to fix this issue. If you've already got 5.0.38 installed and working then there's no need to update.
Will these rpms work on CentOS 3? Specifically, this system:
> uname -a
Linux localhost 2.4.20-021stab028.19.777-enterprise #1 SMP Wed Oct 19 13:05:01 MSD 2005 i686 i686 i386 GNU/Linux
Or would I have to use the src rpm? If so, how would I go about doing that?
Thanks in advance for any help!
The RPMs that I build will probably not install on EL3 as they are designed for EL4, so you would need to build from the src.rpm and hope that there aren't any dependencies that can't be worked around.
One thing though, the kernel name you've provided is leading me to believe that you are hosted on an Virtuozzo VPS. If that's the case, before you build form the src.rpm you should make sure that the version of Plesk that is installed on your VPS works with MySQL 5 (as some older versions don't).
You're good Jason. 🙂 I am on a VPS plan using Virtuozzo, but I've got cPanel installed instead of Plesk.
When I obtained the VPS (about 18 months ago) Virtuozzo did not have a stable release for CentOS 4, hence I had to be content with CentOS 3.
Do you think it's worth my while to invest in a package that has CentOS 4? From what I've seen there is not as much support for CentOS 3 as there is for CentOS 4.
Full support for RHEL3 has long since ended and Deployment support is about to go as well. Maintenance releases will continue to be pushed as needed until 2010, but for all intents and purposes, RHEL3 is dead.
However, if you're not having problems with your current system then you may want to hold off a bit. RHEL/CentOS 5 was just released and providers should be picking it up soon. If you really need the upgrade then go ahead and look for EL4. Using my repo on top of it will push many of the software packages (such as MySQL) beyond where they're at in EL5 anyway.
dtpj4mdwqja59qec