Closed duxan closed 7 years ago
Dušan;
Sorry about the issue, this particular traceback doesn't have the causative error so it's hard for me to say much other than it died during variant calling. It can often be tricky to debug multi-threaded errors. If you re-run with a single core (-n 1
) does it still error out and provide a more useful traceback? Thanks for the work debugging.
Hi
I am closing this because it seems an old issue. Come back if you find other issues or want to continue with this one.
cheers
Hi,
I have met with the same error. For me it fails at multiple steps: bwa-mem, and I think sambamba or GATK.
I've noticed this error only occurs when I submit a job through the scheduler, and everything works perfectly when run on local machine.
When running on one core to diagnose the issue, my traceback is:
Traceback (most recent call last):
File "/mnt/projects/dlho/tancrc/bcbio_pipeline/bin/bcbio_nextgen.py", line 234, in
I believe that running jobs on scheduler may result in bcbio unable to find some programs. Is there anyway to get past this issue? Thanks!
The error looks like you don't have the installed bcbio tools in your PATH for your job submission script. If you're writing a script to submit the main bcbio_nextgen.py
runner job, you should add
export PATH=/path/to/bcbio/local/bin:$PATH
at the top to ensure that gets passed through to the engines and controllers. Hope this helps.
Hi Brad,
Thank you so much!
Hi,
I ran same pipeline that worked previously with new BCbio version and got "multiprocessing error". Log file is job.err.log.txt and bcbio is run with
-t local
. Any idea why this happened?Thanks!