[Swift-devel] OSG hang

Jonathan Monette jonmon at utexas.edu
Thu Jul 14 15:30:31 CDT 2011


I set GLOBUS_HOSTNAME to 50.16.138.64
PING ec2-50-16-138-64.compute-1.amazonaws.com (50.16.138.64): 56 data bytes
Request timeout for icmp_seq 0

jonmon at ip-10-111-45-63:~/sleep$ export GLOBUS_HOSTNAME=50.16.138.64
jonmon at ip-10-111-45-63:~/sleep$ echo $GLOBUS_HOSTNAME
50.16.138.64

I then ran Swift.  I checked the site with:
[jonmon at communicado: ~]$ globus-job-run tuscany.med.harvard.edu /bin/sh -c '/bin/ps -g engage'
  PID TTY          TIME CMD
 3934 ?        00:00:00 globus-job-mana
 4195 ?        00:00:00 perl
 4197 ?        00:00:01 perl
12881 ?        00:00:00 globus-job-mana
13032 ?        00:00:00 perl
17440 ?        00:00:00 condor_shadow
18982 ?        00:00:00 globus-gridftp-
19118 ?        00:00:00 globus-job-mana
19213 ?        00:00:00 bash
19227 ?        00:00:00 sleep
22107 ?        00:00:00 globus-job-mana
22243 ?        00:00:00 ps

sleep did execute on the head node.  sleep finished executing but Swift is still running on the VM.

On Jul 14, 2011, at 2:07 PM, Mihael Hategan wrote:

> On Thu, 2011-07-14 at 14:02 -0500, Jonathan Monette wrote:
> 
>> 
>> So it does seem like the job get run on the head node.  When the job
>> is finished on the head node(I checked several times with
>> globus-job-run) Swift continues to execute(well it just prints the
>> Submitted: 1 line over and over again).
>> 
>> So the next step is to set those environment variables Mike mentioned and try again?  
> 
> Yes. Swift won't work properly if those are not set properly. On most
> system it guesses them, but not on weird systems.
> 
> Setting GLOBUS_HOSTNAME is probably enough though.
> 
> 




More information about the Swift-devel mailing list