You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2014/10/01 16:26:33 UTC

[jira] [Commented] (AIRAVATA-1457) Airavata monitor sometime is not able to identify job for monitoring

    [ https://issues.apache.org/jira/browse/AIRAVATA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154860#comment-14154860 ] 

Lahiru Gunathilake commented on AIRAVATA-1457:
----------------------------------------------

Hi Raman,

Yes it is a good improvement. How do we know by looking at output file that output is produced correctly ? If the output regex parse is failing we can wait ? If that is the case how do we find out application failures ?

Or should the monitor check the output files directly without looking in to standard out/err ?

Lahiru

> Airavata monitor sometime is not able to identify job for monitoring
> --------------------------------------------------------------------
>
>                 Key: AIRAVATA-1457
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1457
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata Job Monitor
>    Affects Versions: 0.14
>            Reporter: Raminderjeet Singh
>
> I submitted 2 jobs on Lonestar and both the jobs were submitted fine but one of the job id was not parsed. Job was submitted fine but job id was empty. Job monitor was not able to identify the job from job name and add it back to monitor. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)