yum and ldd stopped working

Issues related to applications and software problems
Post Reply
asimananda
Posts: 2
Joined: 2017/05/02 11:10:41

yum and ldd stopped working

Post by asimananda » 2017/05/02 11:34:11

Hi,

I'm new to CentOS and my centOS version is 6.8.

I tried to install memprof and in doing so, I updated/installed few packages like glib (to 2.14), gconf, atk, libglade, gtk+ etc.

Then I realised that I've broken the yum.

"ldd --version" was showing 2.14 and "rpm -qa | grep glibc" was showing all 2.12 versions apart from 2.14. Then I uninstalled 2.14 completely, which resulted ldd to stop working.

yum shows following error.

/usr/lib64/python2.6/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr

ldd stopped working too.

# ldd --version
-bash: ldd: command not found

# rpm -qa | grep glibc
glibc-common-2.12-1.192.el6.x86_64
glibc-devel-2.12-1.192.el6.x86_64
glibc-2.12-1.192.el6.x86_64
glibc-headers-2.12-1.192.el6.x86_64

How do I fix these issues?

User avatar
TrevorH
Site Admin
Posts: 33215
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: yum and ldd stopped working

Post by TrevorH » 2017/05/02 12:23:46

How did you update those packages? The only way to do so is using yum and the CentOS repos. If you built them from source or used packages from another distro then you've probably broken stuff, maybe beyond repair.

We ship glib2 2.28.8-9.el6 and glib 1.2.10-33.el6. Be aware that glib is not part of glibc despite sounding similar. You're backevel on your current glibc packages but that's probably because you haven't yum updated since 6.9 came out. If rpm -Va glibc\* ends with no output then you probably haven't corrupted any glibc files.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

asimananda
Posts: 2
Joined: 2017/05/02 11:10:41

Re: yum and ldd stopped working

Post by asimananda » 2017/05/05 06:09:26

Thanks for the reply.

Indeed, I used source packages and looks like that caused the breakage.

I'm going for a fresh installation because this is beyond repair as you mentioned.

Thanks again for your comments.

Post Reply