.Issue. Received below given error in Red Hat Enterprise Linux 6 Server.relocation error: /usr/lib64/libc.so.6: symbol dlstartingup, version GLIBCPRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference. Not able to run any command on the system, it is giving a relocation error. After reboot, system halts due to a kernel panic.Kernel panic - not syncing: Attempted to kill init!Pid: 1, comm: init Not tainted 2.6.32-504.3.3.el6.x8664 #1Call Trace:? Systemcallfastpath+0x16/0x1bEnvironment.

Thank you very much.Uploader:Date Added:23 October 2012File Size:21.62 MbOperating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/XDownloads:97357Price:Free.Free Regsitration RequiredYou may use these HTML tags and attributes: Borderless printing is available for Letter, 4″x6″, 5″x8″, 5″x7″, A4, A6, 3. Mac air microphone.

Symbol pthreadclocksettime, version GLIBCPRIVATE not defined in file libpthread.so.0 with link time reference (/lib/i686/librt.so.1) I poke around Google and Google Groups, see that it might have something to do.

Red Hat Enterprise Linux 6. glibc.

Closed 2 years ago.when I try to fix the problem /lib64/libc.so.6: version 'GLIBC2.14' not found in CentOS 6 system by install latest glibc version to my home directory, I found my computer crashed. $ conda/public/home/liuxs/anaconda3/bin/python: relocation error: /lib64/librt.so.1: symbol vdsoclockgettime, version GLIBCPRIVATE not defined in file libc.so.6 with link time reference$ pythonpython: relocation error: /lib64/librt.so.1: symbol vdsoclockgettime, version GLIBCPRIVATE not defined in file libc.so.6 with link time referenceI try my best to remove all the thing I have done and google to fix this, I failed. I cannot understand the problem, how it occurs and which part should I focus - libc.so.6 or librt.so.1? Which is the key.I have no root permission, so I cannot change the files for lib, lib64 etc. I found how to fix this, the problem came from -rwxrwxr-x 1 liuxs liuxs 3985000 Jun 21 2017./lib/libc.so.6I change its name fro backup, and the system is okay now.

Even though I don't very understand why it works. But the interesting thing is No matter where the file libc.so.6 is, the system will give an error. Maybe it's not a good answer, I modify its name from./lib/libc.so.6 to./lib/libc.so.6.bk in case I need it latter.Thanks comment from @nos.You are trying to run a program that is fundamentally incompatiblewith the runtime of your CentOS 6 machine. You should find a pre-builtbinary that is suitable for CentOS 6, or if this is an open sourceproject, build it yourself.