Setting GLOBUS_HOSTNAME will get the client to advertise whatever
hostname is in the environment variable, rather than what it thinks
its hostname/IP is.
Charles
On Apr 1, 2008, at 4:45 PM, Ian Stokes-Rees wrote:
Hi,
I'm trying to execute:
globusrun-ws -dbg -submit -F neuroinformatics.harvard.edu:9443 -s -
c /bin/hostname
between two machines where other globus commands and authentication
works without problems. This command, however, hangs apparently due
to the streaming. The debug output shows:
debug: response from gsiftp://neuroinformatics.harvard.edu:2811/osg/storage/home/sbgrid/8e1e2a5c-0034-11dd-9b09-0030487dd5da.0.stdout
:
200 PBSZ=1048576
debug: sending command:
PORT 10,0,10,39,166,101
debug: response from gsiftp://neuroinformatics.harvard.edu:2811/osg/storage/home/sbgrid/8e1e2a5c-0034-11dd-9b09-0030487dd5da.0.stdout
:
200 PORT Command successful.
shortly before it hangs (indefinitely). Note the 10,0,10,39 which
is the local IP address of the client where the command is
executed. "neuroinformatics" is the target machine where the job is
run. How do I tell the client that it should be using its public IP
address (134.174.140.14) instead?
Cheers,
Ian
--
Ian Stokes-Rees W: http://sbgrid.org
[EMAIL PROTECTED] T: +1 617 418-4168
SBGrid, Harvard Medical School F: +1 617 432-5600
