Bug 6703 - PBS scheduler adapter assumes that Globus is installed in the same location on the headnode of a cluster and on the work nodes.
: PBS scheduler adapter assumes that Globus is installed in the same location o...
Status: RESOLVED FIXED
: GRAM
gt2 Gatekeeper/Jobmanager
: 4.0.8
: PC Linux
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-03-24 10:57 by
Modified: 2012-09-12 08:38 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-03-24 10:57:23
It seems like the PBS scheduler adapter assumes that the Globus toolkit is
installed in the same location on the headnode of a cluster and on its work
nodes (usually this is the case when a shared filesystem is used).



The PBS script generated by the scheduler adapter contains a line such as:

GLOBUS_LOCATION=<...>
export GLOBUS_LOCATION

The value for the GLOBUS_LOCATION above is set to the value of GLOBUS_LOCATION
on the headnode.  If Globus is installed in a different location on the
headnode than on the work nodes, then this will cause an invalid
GLOBUS_LOCATION value when the job runs on one of the work nodes.
------- Comment #1 From 2012-09-12 08:38:48 -------
I'm cleaning out old bugs. This was addressed with the -target-globus-location
config option in 5.0