Closed SamMod1 closed 1 year ago
Update: I have found an error message in the junction_annotation.log file in the work process directory. It says the following:
Reading reference bed file: fixed_new_annotation.bed ... Done Load BAM file ... Done
===================================================================
Total splicing Events: 11244137
Known Splicing Events: 10461617
Partial Novel Splicing Events: 226475
Novel Splicing Events: 543000
Filtered Splicing Events: 13045
Traceback (most recent call last):
File "/usr/local/bin/junction_annotation.py", line 171, in
Issue fixed. junction_annotation.py errors if there are colons ':' in the sequence id field of a gff. I fixed the issue by replacing all of the ':' in the sequence id column with underscores.
Description of the bug
I am trying to run rnaseq but it keeps failing at the same step: NFCORE_RNASEQ:RNASEQ:RSEQC:RSEQC_JUNCTIONANNOTATION It fails giving an exit status of 1, but no error message seems to be detailing anything wrong in the main log file besides the warning: WARNING: Skipping mount /var/apptainer/mnt/session/etc/resolv.conf [files]: /etc/resolv.conf doesn't exist in container
I'm running this on our cluster using slurm. I've also been using the singularity profile.
Command used and terminal output
Relevant files
slurm-1729803.txt nextflow.log
System information
Nextflow: nextflow/22.10.4
rmaseq: nf-core/rnaseq v3.12.0-g3bec233
Hardware: Slurm Cluster
Profile: Singularity
OS: "CentOS Linux" VERSION="7 (Core)"