Instead of building only credential store module, could you build from airavata source root. Credential store module depends on airavata-server-configuration and other jars. That should resolve your issue..
Thanks. Chathuri On Sun, Dec 20, 2015 at 7:45 PM, Heejoon Chae <[email protected]> wrote: > Hi, Chathuri, > > Thank you for the explanation. > > I cloned the git and tried to compile credential-store with 'mvn clean > install -Dmaven.test.skip=true' with mvn 3.0 and java 8 but got following > errors. > > > > ############################################################################################################### > Downloaded: > http://repo1.maven.org/maven2/org/apache/derby/derbyclient/10.11.1.1/derbyclient-10.11.1.1.jar > (571 KB at 2.8 KB/sec) > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 3:53.576s > [INFO] Finished at: Mon Dec 21 09:38:34 KST 2015 > [INFO] Final Memory: 11M/1931M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project airavata-credential-store: Could > not resolve dependencies for project > org.apache.airavata:airavata-credential-store:jar:0.16-SNAPSHOT: The > following artifacts could not be resolved: > org.apache.airavata:airavata-credential-store-stubs:jar:0.16-SNAPSHOT, > org.apache.airavata:airavata-server-configuration:jar:0.16-SNAPSHOT, > org.apache.airavata:airavata-commons:jar:0.16-SNAPSHOT: Could not find > artifact > org.apache.airavata:airavata-credential-store-stubs:jar:0.16-SNAPSHOT in > apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > > ############################################################################################################### > > Any suggestion? > > Thanks, > Heejoon. > > On Fri, Dec 18, 2015 at 9:29 PM, Chathuri Wimalasena <[email protected] > > wrote: > >> Hi Heejoon, >> >> You need to set up a valid credential store token in the credential store >> (experiment-catalog database has tables related to credential store). Same >> credential store token needs to be set in gateway profiles. This token is >> used when airavata ssh to resource, input staging and all the remote >> connections with the resource. Credential store token is the identifier for >> SSH credential object which contains valid SSH keys. Refer this code >> https://github.com/apache/airavata/blob/master/modules/credential-store/credential-store-service/src/test/java/org/apache/airavata/credential/store/store/impl/db/SSHCredentialTest.java. >> There are API methods to generate SSH keys as well. You can use any of the >> two methods. >> >> Thanks.. >> Chathuri >> >> >> >> On Fri, Dec 18, 2015 at 12:02 AM, Heejoon Chae <[email protected]> >> wrote: >> >>> Hi, Suresh, >>> >>> Thank you for the help. It correctly parses the email. >>> >>> Now I have another error caused by 'credential token' as below, >>> >>> ERROR] expId: ttt_d0a8ca90-46b3-4225-add7-c29207130fc8, processId: >>> PROCESS_273f058f-a0bc-400b-9a82-5d71246c8fa8, taskId: >>> TASK_fc9dd43b-f0ea-4e6c-bd92-c5daa698257b type: DATA_STAGING,:- output >>> staging failed, reason: Provided credential store token is not valid. >>> Please provide the correct credential store token >>> [INFO] expId: ttt_d0a8ca90-46b3-4225-add7-c29207130fc8, processId: >>> PROCESS_273f058f-a0bc-400b-9a82-5d71246c8fa8 :- Process status changed >>> FAILED -> FAILED >>> [INFO] Publishing status to rabbitmq... >>> [ERROR] GFac Worker throws an exception >>> org.apache.airavata.gfac.core.GFacException: Error while staging output >>> data >>> at >>> org.apache.airavata.gfac.impl.GFacEngineImpl.outputDataStaging(GFacEngineImpl.java:478) >>> at >>> org.apache.airavata.gfac.impl.GFacEngineImpl.runProcessOutflow(GFacEngineImpl.java:393) >>> at >>> org.apache.airavata.gfac.impl.GFacWorker.runProcessOutflow(GFacWorker.java:172) >>> at org.apache.airavata.gfac.impl.GFacWorker.run(GFacWorker.java:105) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> at java.lang.Thread.run(Thread.java:745) >>> >>> I actually set 'false' for storing credential in the >>> 'airavata-server.properties' file as bellow >>> >>> start.credential.store=false >>> >>> but it seems still they are active. >>> >>> Thank you, >>> Heejoon. >>> >>> On Fri, Dec 18, 2015 at 12:42 AM, Suresh Marru <[email protected]> >>> wrote: >>> >>>> Hi Heejoon, >>>> >>>> You will need to configure your email within gfac-config.yaml (you will >>>> find it in the bin directory). >>>> >>>> If you can add your email to: >>>> >>>> - jobManagerType: SLURM >>>> commandOutputParser: >>>> org.apache.airavata.gfac.impl.job.SlurmOutputParser >>>> emailParser: >>>> org.apache.airavata.gfac.monitor.email.parser.SLURMEmailParser >>>> resourceEmailAddresses: >>>> - SDSC Admin <[email protected]> # comet >>>> - [email protected] # stampede >>>> - [email protected] >>>> >>>> >>>> Thanks, >>>> Suresh >>>> >>>> > On Dec 16, 2015, at 6:33 PM, Heejoon Chae <[email protected]> >>>> wrote: >>>> > >>>> > Hi, Suresh, >>>> > >>>> > I am using one month old version of PGA and Airavata server. Both >>>> were recent version at that time. >>>> > >>>> > apache-airavata-server-0.16-SNAPSHOT >>>> > >>>> > Thank you, >>>> > Heejoon. >>>> > >>>> > >>>> > >>>> > On Thu, Dec 17, 2015 at 8:28 AM, Suresh Marru <[email protected]> >>>> wrote: >>>> > Hi Heejoon, >>>> > >>>> > Are you using Airavata 0.15 or 0.16 for this purpose? >>>> > >>>> > Suresh >>>> > >>>> >> On Dec 16, 2015, at 5:38 PM, Heejoon Chae <[email protected]> >>>> wrote: >>>> >> >>>> >> Hi, >>>> >> >>>> >> I have succeeded run job with SLURM. >>>> >> >>>> >> Now, the job monitoring through email causes some errors as bellow. >>>> >> >>>> >> It seems the Airavata server correctly log in the email account and >>>> bring email list, but it could not parse it correctly. >>>> >> >>>> >> >>>> ################################################################################# >>>> >> [ERROR] [EJM]: Error parsing email message >>>> =====================================> >>>> >> org.apache.airavata.common.exception.AiravataException: [EJM]: >>>> Couldn't identify Resource job manager type from address >>>> [email protected] >>>> >> at >>>> org.apache.airavata.gfac.monitor.email.EmailBasedMonitor.getJobMonitorType(EmailBasedMonitor.java:160) >>>> >> at >>>> org.apache.airavata.gfac.monitor.email.EmailBasedMonitor.parse(EmailBasedMonitor.java:144) >>>> >> at >>>> org.apache.airavata.gfac.monitor.email.EmailBasedMonitor.processMessages(EmailBasedMonitor.java:239) >>>> >> at >>>> org.apache.airavata.gfac.monitor.email.EmailBasedMonitor.run(EmailBasedMonitor.java:208) >>>> >> at java.lang.Thread.run(Thread.java:745) >>>> >> [ERROR] FROM: [email protected] >>>> >> [ERROR] TO: [email protected] >>>> >> [ERROR] SUBJECT: SLURM Job_id=116 Name=A1514598207 Ended, Run time >>>> 00:00:01, COMPLETED, ExitCode 0 >>>> >> >>>> ################################################################################# >>>> >> >>>> >> Thank you, >>>> >> Heejoon. >>>> > >>>> > >>>> >>>> >>> >> >
