[Swift-devel] Failed to start channel GSSCChannel (trunk, coasters, ssh-cl:pbs)

Jonathan Monette jonmon at mcs.anl.gov
Fri Feb 3 13:36:53 CST 2012


What machine are you executing on?  bridled to where?

On Feb 3, 2012, at 1:35 PM, Thomas Uram wrote:

> That doesn't appear to help in my case.
> 
> Should the hostname in the URL here concern me?
> 
>>>> Caused by: org.globus.cog.karajan.workflow.service.channels.ChannelException: Failed to start channel GSSCChannel-https://206.12.24.2:35836(2)[1544213635: {}]
> 
>>> 
> 
> 
> 
> 
> 
> On Feb 3, 2012, at 1:27 PM, Jonathan Monette wrote:
> 
>> So I am not sure if this is a similar problem I ran into, but I had to change the X509_USER_PROXY variable.  Normally this is set to /tmp/x509up_u<uid>.  I had to change it(changed it to $HOME/.globus/<proxy_file>  For some reason when issuing a command over ssh(example: ssh jonmon at login.pads.ci.uchicago.edu ls /tmp/) my proxy file was not there.  But when I would log into the machine before issuing the ls command the proxy file was there.  I assumed(not verified) that the /tmp/ directory is not fully configured/mounted properly when issuing a command over ssh.  Changing the X509_USER_PROXY variable fixed the issue.
>> 
>> On Feb 3, 2012, at 1:20 PM, Thomas Uram wrote:
>> 
>>> 
>>> I'm encountering a problem using coasters with ssh-cl:pbs in trunk. The first error is as follows:
>>> 
>>> 2012-02-03 13:05:29,823-0600 DEBUG vdl:execute2 APPLICATION_EXCEPTION jobid=hostname-k2urbkmk - Application exception: null
>>> Caused by: org.globus.cog.abstraction.impl.common.task.TaskSubmissionException: Could not submit job
>>> Caused by: org.globus.cog.karajan.workflow.service.channels.ChannelException: Failed to start channel GSSCChannel-https://206.12.24.2:35836(2)[1544213635: {}]
>>> Caused by: java.net.NoRouteToHostException: No route to host
>>> 2012-02-03 13:05:29,875-0600 DEBUG vdl:execute2 APPLICATION_EXCEPTION jobid=hostname-j2urbkmk - Application exception: null
>>> Caused by: org.globus.cog.abstraction.impl.common.task.TaskSubmissionException: Could not submit job
>>> Caused by: org.globus.cog.karajan.workflow.service.channels.ChannelException: Failed to start channel GSSCChannel-https://206.12.24.2:35836(3)[1544213635: {}]
>>> Caused by: java.net.NoRouteToHostException: No route to host
>>> 2012-02-03 13:05:32,585-0600 WARN  vdl:transferwrapperlog Failed to transfer wrapper log for job hostname-k2urbkmk
>>> 2012-02-03 13:05:32,586-0600 DEBUG vdl:transferwrapperlog Exception for wrapper log failure from hostname-20120203-1305-3q1m7jg3/info/k on Bugaboo: null
>>> Caused by: org.globus.cog.abstraction.impl.file.IrrecoverableResourceException: Exception in getFile
>>> Caused by: org.globus.cog.abstraction.impl.file.FileResourceException: Failed to retrieve file information about /home/turam/tmp/hostname-20120203-1305-3q1m7jg3/info/k/hostname-k2urbkmk-info
>>> Caused by: org.globus.ftp.exception.ServerException: Server refused performing the request. Custom message: Server refused MLST command (error code 1) [Nested exception message:  Custom message: Unexpected reply: 500-Command failed : System error in stat: No such file or directory
>>> 500-A system call failed: No such file or directory
>>> 500 End.] [Nested exception is org.globus.ftp.exception.UnexpectedReplyCodeException:  Custom message: Unexpected reply: 500-Command failed : System error in stat: No such file or directory
>>> 500-A system call failed: No such file or directory
>>> 500 End.]
>>> 
>>> 
>>> The full log file (with embedded sites and tc files) is here:
>>> 
>>> http://www.mcs.anl.gov/~turam/20120203-1308/hostname-20120203-1305-3q1m7jg3.log
>>> 
>>> This same scenario worked with Swift 0.93, using ssh:pbs instead (ssh-cl is only available in trunk).
>>> 
>>> Any help understanding and working around this problem would be great.
>>> 
>>> Thanks,
>>> Tom Uram
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>> 
> 




More information about the Swift-devel mailing list