You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2017/04/25 18:35:04 UTC

[jira] [Commented] (AIRAVATA-1904) ARCHIVE did not happen in recovery

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

Eroma commented on AIRAVATA-1904:
---------------------------------

Tested in gw56 with latest airavata 0.17 and still the issue exists.
steps to re-produce:
1. submit a job to resource. e.g: bigred2
2. when the job status = QUEUED in PGA and PD in cluster queue stop gfac server.
3. After job is running in cluster start the GFAC server.
4. All inputs are transferred but ARCHIVE folder does not exists in the storage

> 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
>             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.3.15#6346)