On Dec 19, 2008, at 4:46 AM, Le Trung Kien wrote:
Hi,
Although, in my current shell, the LD_LIBRARY_PATH contains the link
to libimf.so . However, I got the following error:
globusrun-ws -submit -c /bin/true
Submitting job...Done.
Job ID: uuid:c27444fe-cdab-11dd-8bea-0011258c5e4a
Termination time: 12/19/3008 09:02 GMT
Current job state: Failed
Destroying job...Done.
globusrun-ws: Job failed: Error code: 201Script stderr:
/opt/gt4.2.1/libexec/globus-fork-starter: error while loading shared
libraries: libimf.so: cannot open shared object file: No such file
or directory
I faced this error several times when run some GLOBUS shell scripts
and my solution is adding line
source /etc/profile
to the shell scripts, so invoked programs could load lib files.
However, in this case globusrun-ws is a binary file. I don't know
how it calls another programs.
Please help.
--
Le Trung Kien.
This message comes from the container-side of Globus. It might be
sufficient to update your library path prior to starting the
container; otherwise, you could add something like this to the
$GLOBUS_LOCATION/libexec/globus-job-manager-script.pl:
if (exists($ENV{LD_LIBRARY_PATH}))
{
$ENV{LD_LIBRARY_PATH} .= ":PATH-CONTAINING-LIBIMF";
}
else
{
$ENV{LD_LIBRARY_PATH} = "PATH-CONTAINING-LIBIMF";
}
Joe
