airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raminderjeet Singh (JIRA)" <>
Subject [jira] [Created] (AIRAVATA-888) SSHProvider not working in trunk
Date Thu, 18 Jul 2013 13:52:49 GMT
Raminderjeet Singh created AIRAVATA-888:

             Summary: SSHProvider not working in trunk
                 Key: AIRAVATA-888
             Project: Airavata
          Issue Type: Bug
          Components: GFac, Workflow Interpreter
    Affects Versions: 0.9
            Reporter: Raminderjeet Singh

SSHProvider in current trunk is failing with NullPointerException. I configured the ssh properties
but EmbeddedGFacInvoker is not setting security context to GFAC. 

org.apache.airavata.gfac.GFacException: Error Executing a OutFlow Handler
        at org.apache.airavata.gfac.GFacAPI.invokeOutFlowHandlers(
        at org.apache.airavata.gfac.GFacAPI.schedule(
        at org.apache.airavata.gfac.GFacAPI.submitJob(
        at org.apache.airavata.xbaya.invoker.EmbeddedGFacInvoker.invoke(
        at org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.handleWSComponent(
        at org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.executeDynamically(
        at org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.access$000(
        at org.apache.airavata.xbaya.interpretor.WorkflowInterpreter$
Caused by: java.lang.NullPointerException
        at net.schmizz.sshj.transport.TransportImpl.write(
        at net.schmizz.sshj.SSHClient.startSession(
        at net.schmizz.sshj.xfer.scp.SCPEngine.execSCPWith(
        at net.schmizz.sshj.xfer.scp.SCPDownloadClient.startCopy(
        at net.schmizz.sshj.xfer.scp.SCPDownloadClient.copy(
        at org.apache.airavata.gfac.handler.SCPOutputHandler.invoke(
        at org.apache.airavata.gfac.GFacAPI.invokeOutFlowHandlers(
        ... 7 more
[ERROR] Error execution workflow Node : pegasus_submit_invoke
[ERROR] No provider available for OpenSSH key file

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message