AWK (could be JVM?) Error - libdl.so.2/libc.so.6

revof11 · 10-05-2005, 02:20 PM

I am receiving the following error attempting to run a shell script on (an InstallAnywhere launcher to be precise) that seems to lead me to believe that I am missing some installed resource on my FC4 x86_64 installation or have something set up improperly (the following is identical to that which occurs on another FC4 x86_64 machine):

Code:

[root@mace PROJECT_main_2005-10-04]# ./PROJECT
awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/jdks/64/jdk1.5.0_05/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

I have run a check to see where things are, and it all seems to be in place... I even ran an ldconfig to be sure that my /etc/ld.so.conf was populated. The following output illustrates the output of this data:

Code:

[root@mace ~]# locate libdl.so.2
/lib64/libdl.so.2
/lib/libdl.so.2

[root@mace ~]# cat /etc/ld.so.conf
include ld.so.conf.d/*.conf
/lib64

[root@mace ~]# rpm -q --whatprovides libdl.so.2
glibc-2.3.5-10
glibc-2.3.5-10.3

[root@mace ~]# rpm -q --whatprovides libc.so.6
glibc-2.3.5-10
glibc-2.3.5-10.3

[root@mace ~]# rpm -q --whatprovides libpthread.so.0
glibc-2.3.5-10
glibc-2.3.5-10.3

[root@mace ~]# rpm -qa | grep glibc
glibc-common-2.3.5-10.3
glibc-headers-2.3.5-10.3
glibc-debuginfo-2.3.5-10.3
glibc-utils-2.3.5-10.3
glibc-devel-2.3.5-10
glibc-2.3.5-10
glibc-devel-2.3.5-10
glibc-profile-2.3.5-10.3
glibc-2.3.5-10.3
glibc-devel-2.3.5-10.3
glibc-2.3.5-10
glibc-kernheaders-2.4-9.1.94
glibc-common-2.3.5-10
glibc-headers-2.3.5-10
glibc-2.3.5-10.3
glibc-devel-2.3.5-10.3

An additional piece of information is that when running on an FC4 x86 (non-64) install, everything seems to be working just fine. Could it be the JVM (Sun Java 1.5.0_05)? The problem with that is everything else I run using command-line (non-InstallAnywhere scripted) Java commands, things seem to work fine

Does anyone have any ideas of what I need to do in order to get this working?

zeitounator · 10-27-2005, 11:40 AM

I've been bumping into the exact same problem for a couple months... I get the same errors with other installAnywhere scripts (ZendStudio installer, Gallery2 remote....).

I did not have time to investigate the problem deeper but it looks to me as if the install anywhere script is looking for 32bit versions of library... in the 64bit path.

More on this later if I make any findings... and any suggestion/comment/solution appreciated

zeitounator · 11-29-2005, 06:52 AM

OK !!! After months I think I finally got the solution to this installAnywhere bug on x86_64.

The solution is not trivial but here it goes (tested successfully on the installAnywhere scripts for ZendStudioClient-5.0.0 and GalleryRemote).

Open the bin installer file in an hexadecimal editor (such as hexedit).

Look for the line

Code:

export LD_ASSUME_KERNEL=2.2.5

and replace it with

Code:

#xport LD_ASSUME_KERNEL=2.2.5

Save the file and lauch. It should work

zeitounator · 11-29-2005, 06:56 AM

Forgot to mention you have to apply the same hack on the resulting LaunchAnywhere script once installed...

zeitounator · 05-22-2006, 06:21 AM

Assuming the install anywhere script is called Install.bin

Code:

cp Install.bin Install.bak
cat Install.bak | sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" > Install.bin
rm Install.bak

Reference: http://www.zend.com/support/knowledg...84&view_only=1

revof11 · 05-22-2006, 08:29 AM

PERFECT!
You are, indeed, my hero, sir.

zhaosj · 07-04-2006, 03:13 AM

thanks all. I can do it right too.

mohan.kgs · 07-25-2006, 03:47 AM

Awesome solution. Thanks a lot.

norcon · 02-06-2007, 01:26 PM

Having had similar difficulties loading an application on x86_64, I followed your advice and succeeded having changed the "export LD_ASSUME_KERNEL=2.2.5" line. However you mention that I also need to apply the same hack to the resulting LaunchAnywhere script, but I am unable to find a similar line in any .lax file. Please could you point me in the right direction to find the right script and what needs changing in it.

Thanks

revof11 · 02-06-2007, 04:07 PM

It's not the LAX file.
It's the shell script it outputs.

When you do a "Create Launcher"... it's the file that it creates.

norcon · 02-07-2007, 01:18 PM

Thanks for your advice.....apologies for my lack of knowledge....I'm learning all the time!

I have found two shell scripts with seemingly identical content which have two lines that I am looking for. These are:

# the call will hang, if it -is- vulnerable!
export LD_ASSUME_KERNEL=2.2.5

if [ $linux_LD_ASSUME_KERNEL_hack -eq 1 ]; then
LD_ASSUME_KERNEL=2.2.5
export LD_ASSUME_KERNEL

I have changed the "export" to "#xport" in each case but the application dill not run. Maybe there is some other problem with the application??

appacoet · 04-19-2007, 06:44 PM

Awsome Solution!!! Thank you sir!!

rv99 · 09-12-2008, 04:04 PM

Thanks dude - you are a true scholar and gentleman.