Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just tried to do an upgrade from mysql 3.23 to 4.1.x using Yum on a very minimal RH Fedora Core 2 system. Yum barfed on a few of the steps, but then said "transaction complete."
Now every mysql command (including mysql --version) returns the following error:
mysql: relocation error: /usr/lib/mysql/libmysqlclient.so.14: symbol __memmove_chk, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference
How do I go about fixing this problem?
(unfortunately the exact yum errors are not available, they scrolled past my buffer).
I thought I'd move on and address this issue later, so I went on to do an install of Subversion. So I did `yum install subversion`. Everything went okay. No worrisome output. Transaction complete. Guess what? NOW YUM IS BROKEN!!
I now get this error when I run YUM:
/usr/bin/python: relocation error: /usr/lib/libpython2.4.so.1.0: symbol __vsnprintf_chk, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference
WTF is going on? This was a fresh install. I know yum uses python, and my install of subversion updated python ... but ISN"T THE WHOLE FRICKIN POINT OF YUM TO MANAGE THIS SHITE?
Because all these upgraded RPM's you downloaded to upgrade with were compiled against a newer version of GLIBC, like the error states. You need to upgrade GLIBC to the version they were compiled against. But be very careful in upgrading, if you do one thing wrong, your whole system can be trashed. I'd say start by searching for past examples of upgrading it, etc, before proceeding. Usually another easy way to upgrade would be to use yum but since you barfed it, that won't do you any good unless you remove the RPM you upgraded with and revert/downgrade back to the pre-existing version you had installed.
Thanks for the info. I'm confused though ... if the new packages depend on a newer glibc, then shouldn't yum notified me of that? I thought its purpose in life was to help users with this dependency hell.
Originally posted by belorion Thanks for the info. I'm confused though ... if the new packages depend on a newer glibc, then shouldn't yum notified me of that? I thought its purpose in life was to help users with this dependency hell.
So when you say it barfed on a few of the steps and then said transaction complete, an exact error message is probably helpful to anyone trying to help..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.