sirebral
asked on
Really messed up my box... /bin/sh: relocation error: /bin/sh: symbol __memcpy_chk, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference..
I was trying to update some packages on my main linux host box and now about 99% of the programs have stopped running, all showing the same error of /bin/sh: relocation error: /bin/sh: symbol __memcpy_chk, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference
HELP!
I have not the slightest clue how to fix this and I really don't want to reload this box as it has quite a bit of custom config done.
Thanks!
Keith
HELP!
I have not the slightest clue how to fix this and I really don't want to reload this box as it has quite a bit of custom config done.
Thanks!
Keith
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Is there a possibility that YUM backed up the old config/files as I am unable to login to the box from my location and my only access at this point is webmin's file manager. I could potentially go down to the colo tomorrow, yet getthing this box back online ASAP is key.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
YUM rather haven't back Your file up. Sorry. And sorry to say, that it may end in installing new system over it.
You need to do what I and utarn said: You need glibc 2.3.4 at least.
It's just You may find it hard to install/copy binaries, becouse You can't get access to the machine. If the webFM allows You to change system files, try copy glibc libraries from other FC3 or FC4 installation.
You need to do what I and utarn said: You need glibc 2.3.4 at least.
It's just You may find it hard to install/copy binaries, becouse You can't get access to the machine. If the webFM allows You to change system files, try copy glibc libraries from other FC3 or FC4 installation.
You can use webmin's file manager to copy the files to the box...
Before you do reinstall just give it a shot at running yum install glibc
Your glibc is messed up (wrong version or a botched upgrade). My guess is that you "upgraded" a version of glibc not meant fro Fedora Core 3, meaning one not from the FC3 errata. The fix for this is to revert to the original glibc or the one in the FC3 updates.
Unfortunately I don't think you'll be able to do this except from a boot from CD since the tools needed to re-install glibc are linked against glibc and won't work at present.
Unfortunately I don't think you'll be able to do this except from a boot from CD since the tools needed to re-install glibc are linked against glibc and won't work at present.
I think you may want to update your glibc.If so, don't try to use package from another distribution because it's not designed for your linux. The best way is you can use Up2date or you may go to your linux distribution website and download from there only.
ASKER
Nothing seemed to work, I really screwed it up royally, so I wiped the box, installed Fedora 4 and restored my data.. took me about a day to get it all back but we're running again. Have to be more careful with YUM from now on :) - Thanks for the suggestions.
Keith
Keith
Well, yum has worked well so far for me... It normally looks for the correct dependencies and only applies the update if that doesn't kill the rest of the system, or then you will probably have to enter something explicitly. How did you use yum when you updated those packages?
ASKER
Yum -y install <package>, in this case I was trying to do the kernel.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER