-
Notifications
You must be signed in to change notification settings - Fork 45
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
snpeff fails with segfault #164
Comments
@trum994 It looks as though you are requesting a 48 GB of memory for the snpEff annotation step, which cannot be allocated. The workflow tries to send sensible defaults for all processes and additional memory for snpEff beyond the default has not brought much benefit in our testing. You should reduce (or remove) the directive that overrides the memory for snpeff in your |
Thanks for your quick response. I will remove snpeff mem override in myconfig.txt and resume. However our cluster did not have any issues allocating 48GB. |
Unfortunately same issue:
And here is the script with now 6GB.
|
That is unfortunate! I assume the
This will force the SnpEff steps to run in serial which will mitigate this error (if that is the issue). |
With maxForks =1 added my snpeff hasn't crashed yet! This would also explain why the job had no issues when I manually kicked off .command.run. Of course as expected I only see 1 job running right now so this will take a while. |
Thanks, let me know how you get on! |
[41/5fd95a] process > annotate_snp_vcf (24) [100%] 25 of 25 ✔ |
Operating System
Other Linux (please specify below)
Other Linux
Ubuntu
Workflow Version
2.0.0
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
#!/bin/bash
ml nextflow
export NXF_OFFLINE="false"
nextflow run epi2me-labs/wf-human-variation
-latest
-resume
--bam '.../test_epi2me_hv/bam/R8967_800_v2.count.bam'
--basecaller_cfg 'dna_r10.4.1_e8.2_400bps_hac_prom'
--mod
--ref '.../test_epi2me_hv/refs/Homo_sapiens.GRCh38.dna.primary_assembly.fa'
--sample_name 'R8967'
--snp
--sv
--bam_min_coverage 0
-profile singularity
-c myconfig.txt
Workflow Execution - CLI Execution Profile
singularity
What happened?
We're running on our cluster via singularity. annotate snpeff step fails for me with a java sigbus error. In the execution directory .command.log and .command.err only have this:
Picked up JAVA_TOOL_OPTIONS: -Xlog:disable -Xlog:all=warning:stderr
But there's also a hs_err_pid201.log file which I pasted in the "Application activity log entry".
During a resume it will fail within seconds. However if I cd into the execution directory and simply do a
sbatch .command.run
this step will run to completion with no issues.Relevant log output
Application activity log entry
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
The text was updated successfully, but these errors were encountered: