airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AIRAVATA-2186) Abaqus experiment on Comet is in EXECUTING. Not moving further and no errors in logs as well
Date Tue, 10 Jan 2017 21:02:58 GMT

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

Eroma closed AIRAVATA-2186.
---------------------------

This issue was a comet file system issue at the time. Currently Jobs are successfully getting
executed and completed in Comet.

> Abaqus experiment on Comet is in EXECUTING. Not moving further and no errors in logs
as well
> --------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2186
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2186
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata System, GFac
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Sudhakar Pamidighantam
>             Fix For: 0.17
>
>         Attachments: Screen Shot 2016-10-24 at 2.11.25 PM.png
>
>
> Launched an Abaqus job on Comet with 1 node and 4 CPUs. Experiment status is displayed
as EXECUTING with no job ID or status.
> In Comet working directory only the input file exits but no job script.
> Experiment Details:
> 1. Exp ID: Ab1_03aa4a2f-e128-4e92-b57b-a4551d113295
> 2.Working Directory: /oasis/scratch/comet/gridchem/temp_project/seagrid_workdirs/PROCESS_c6cb26bf-b9eb-41f1-841d-2c96245fe609
> 3. Issues seem to be when tried to use 4 or 16 CPU in Compute queue.
> 4. In Comet when viewed the queue status for Comet messages in attached image is displayed



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

Mime
View raw message