airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AIRAVATA-1904) ARCHIVE did not happen in recovery
Date Fri, 05 Jan 2018 16:48:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eroma reassigned AIRAVATA-1904:
-------------------------------

    Assignee: Suresh Marru

> ARCHIVE did not happen in recovery
> ----------------------------------
>
>                 Key: AIRAVATA-1904
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1904
>             Project: Airavata
>          Issue Type: Bug
>          Components: GFac, PGA PHP Web Gateway
>    Affects Versions: 0.16
>         Environment: dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Suresh Marru
>            Priority: Critical
>             Fix For: 0.18
>
>
> 1. i submitted an amber job to comet and when it was active in comet i stopped GFAC.

> 2. I started gfac agin while it was in running state. now the experiment is completed
but ARCHIVE did not happen. 
> 3. In storage location also ARCHIVE does not exist gateway-user-data/dev-seagrid/Eroma2016/March_14th_2016/SLM3_AmberSander_Comet1457983469/PROCESS_b4b8f7ce-801d-403b-a286-d7755429eb84
> 4. This is amber_sander application and exp ID is SLM3-AmberSander-Comet_59a5c095-73ba-4dd9-8d13-19709f6fa474



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message