exited with return code 247 on TCGA bam from drs:// url

Post author
Brendan Reardon

Hi Terra,

I have not been able to figure out this issue. I am attempting to run jobs on TCGA bams with the drs:// URLs but they fail with the following error code.

> exited with return code 247 which has not been declared as a valid return code. See 'continueOnReturnCode' runtime attribute for more details.

Any input would be appreciated! 

Comments

7 comments

  • Comment author
    Samantha (she/her)

    Hi Brendan Reardon,

     

    Thanks for reaching out. Can you share the workspace where you are seeing this issue with GROUP_FireCloud-Support@firecloud.org by clicking the Share button in your workspace? The Share option is in the three-dots menu at the top-right.

    1. Add GROUP_FireCloud-Support@firecloud.org to the User email field and press enter on your keyboard.
    2. Click Save.

     

    Let us know the workspace name, as well as the relevant submission and workflow IDs. We’ll be happy to take a closer look as soon as we can.

     

    Best,

    Samantha

    0
  • Comment author
    Brendan Reardon
    • Edited

    Hi Samantha,

    Oops, thank you - I had forgotten to do that. The workspace is vanallen-firecloud-nih/TCGA-KIRP-MOAlmanac and relevant submission ids are 7fefd0ed-049a-4bfb-9f00-529ccbec8891 and 96435592-7eb3-4606-bc86-2e2d10b253b8

     

    0
  • Comment author
    Brendan Reardon

    Just following up on this. Thank you! 

    0
  • Comment author
    Samantha (she/her)

    Hi Brendan Reardon,

     

    Sorry for the delay. We are still investigating issue and will get back to you as soon as we can.

     

    Best,

    Samantha

    0
  • Comment author
    Samantha (she/her)

    Hi Brendan Reardon,

     

    We think the issue here may be that you are not providing enough memory to the SamToFastq task, which is why it's failing. This value should be at least as much as the memory being allocated to the command (150GB), but it looks like you only have it set to 16GB. Can you try resubmitting the workflow with increased memory?

     

    Best,

    Samantha

    0
  • Comment author
    Brendan Reardon

    And that is why using WDLs written by other people can be dangerous. Thank you, Samantha! Shouldn't this have returned a PAPI error code 9 though, since the issue was memory? Why was this error code returned? 

    0
  • Comment author
    Samantha (she/her)

    Hi Brendan Reardon,

     

    Most likely, the command itself failed to allocate proper memory inside the VM and exited by itself instead of PAPI terminating the job.

     

    Best,

    Samantha

    0

Please sign in to leave a comment.