Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipeline completes with unknown error #80

Open
raagagrawal opened this issue Dec 22, 2022 · 3 comments
Open

Pipeline completes with unknown error #80

raagagrawal opened this issue Dec 22, 2022 · 3 comments

Comments

@raagagrawal
Copy link

Describe the issue
Pipeline completes create_input_csv_metapipeli... and create_config_json steps but fails at call_metapipeline_DNA after 30 minutes. Log file does not show error message - just a failed task.

  • Pipeline release version: 4.0.0
  • Cluster you are using (SGE/Slurm-Dev/Slurm-Test): Slurm
  • Node type (F2s (lowmem) / F72s (midmem) / M64s (execute)): F72
  • Submission method (interactive/submission script): script
  • Actual submission script (python submission script, "nextflow run ...", etc.): /hot/project/disease/ProstateTumor/PRAD-000095-ColibactinDHTDNARNA/scripts/pipelines/metapipeline-dna/submit.sh
  • Sbatch or qsub command and logs if applicable
  • Config files: /hot/user/ragrawal/Liss-Agrawal-PRAD-COLB/metapipeline-dna/config/LAPRCOLB000001.config
  • Path to the working directory: /hot/user/ragrawal/Liss-Agrawal-PRAD-COLB/metapipeline-dna/output
  • Any logs produced by the pipeline: /hot/project/disease/ProstateTumor/PRAD-000095-ColibactinDHTDNARNA/scripts/pipelines/metapipeline-dna/LAPRCOLB000001.log
@yashpatel6
Copy link
Collaborator

To find the logs for the specific error, you'll want to look at the .command.log file in the common working dir (The specific one can be found by looking at the main log in front of the process; you'll see [48/b348b2], which tells you the directory. The relevant one here: /hot/user/ragrawal/Liss-Agrawal-PRAD-COLB/metapipeline-dna/output/48/b348b27906d06896669ff5847e5215/.command.log

The issue seems to be with /scratch, which is something we've been seeing recently. Can you open a ServiceNOW ticket with the job ID if you have it? You can include the error message in the .command.log file above along with the job ID and the node the job ran on.

@raagagrawal
Copy link
Author

I'll open a ticket now. I'm havint the same issue with /scratch on other pipelines too. Thank you for the help!

@raagagrawal
Copy link
Author

Ticket opened. Ticket number: [TIX03798282]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants