Results 1 to 2 of 2
ohh, I thinh I have done something wrong.
I did make a update from glibc-2.5-18 to ver glibc-2.5-34 but still got database restarting so I decided to remove glibc-2.5-34 for ...
- 02-16-2009 #1Just Joined!
- Join Date
- Feb 2009
- Posts
- 1
Problems after removing glibc-* RedHat EL5
ohh, I thinh I have done something wrong.
I did make a update from glibc-2.5-18 to ver glibc-2.5-34 but still got database restarting so I decided to remove glibc-2.5-34 for installing glibc-2.5-24.
I execute command:
root@DB1 ~# rpm -e --nodeps --allmatches glibc-2.5-34
warning: /etc/localtime saved as /etc/localtime.rpmsave
Invalid link from "ld-linux.so.2" to "/lib/ld-lsb.so.3": No such file or directory
error: %postun(glibc-2.5-34.x86_64) scriptlet failed, exit status 255
Now I can not do anything! I totally messed up in server
root@DB1 ~# yum install glibc-*
bash: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory
Somebody can me to fix that?
- 02-17-2009 #2Just Joined!
- Join Date
- Sep 2007
- Location
- Lafayette, IN
- Posts
- 83
Yuck. That's always a painful mistake to make. Your best bet would probably be to boot the system off a live CD. See Accidently removed glibc, now what? - FedoraForum.org


Reply With Quote