[
https://issues.apache.org/jira/browse/AIRAVATA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153727#comment-14153727
]
Raminderjeet Singh commented on AIRAVATA-1457:
----------------------------------------------
Yes job never came out of unknown state. Actual job on resource ran fine and
produced results. Can we add a check in monitor to look for working folder for
actual job id in stdout file or some other log file of job scheduler? We have
job working folder and other details about the job to confirm job status.
Updating the experiment status of experiment:
US3-AIRA_166e1745-7d59-48ae-b70f-7fb6097f26b7 to UNKNOWN
> 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)
