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. > > > > > >
