Closed Josephinedh closed 6 months ago
Hi @Josephinedh
It's possible that this a an intermittent filesystem problem, but I'm not sure. Could you try running again, and if you get the same issue, could you also post the .nextflow.log please
Hi Neil I've tried to rerun it, also using your suggestion in issue #47 as I previously got an error similar to that. However, I still get the error above, I've attached the .nextflow.log here as well. Thanks, Josephine nextflow.log.txt
Hi @Josephinedh
Is it possible you are using an incorrect container?
Is there an entry for common_sha
in /home/projects/cu_10027/data/projects/gbm/data/data_processed/rigshospitalet/rna/ont/wf-single-cell.config
, and if so what is it?
Also try using the latest version v0.2.9
Actually I can see in the logs you are using the correct container: wf-single-cell:sha8e7d91013029ea8721743bd087583e5205cdc1dc
Please do try v0.2.9 though, and I will get straight back to you if this does not work
Thanks for the help on this.
I tried now with v0.2.9 and still get the same error, unfortunately. And no, there's no entry for common_sha
in the config file.
Hi @Josephinedh. Could you post the log from the last run you did with v0.2.9 please
Sure it's here:
Hi @Josephinedh
Apologies for the late response. I'm looking into this now
Hi @Josephinedh
Again sorry for the late response. This is a puzzle, as we know samtools is installed in the container and we haven't come across this issue before.
Could you try the following please? 1: delete the image /home/projects/cu_10027/data/projects/gbm/data/data_processed/rigshospitalet/rna/ont/cache/ontresearch-wf-single-cell-sha8e7d91013029ea8721743bd087583e5205cdc1dc.img
2: try running the workflow again, but use the latest 1.0.1 with -r v1.0.1
@Josephinedh Did you try my suggestion?
Hi @nrhorner sorry about the very late response. I've tried with your newest version now, and for the first sample it worked. However, when I tried with a second sample the pipeline failed but at one of the last output steps, so most output files are already generated.
I've attached the log file here. nextflow_v1.1.0.log
The relevant part of you log is:
Caused by:
Process `output (4)` terminated with an error exit status (255)
Command executed:
echo "Writing output files"
Command exit status:
255
Command output:
(empty)
Command error:
INFO: Mounting image with FUSE.
WARNING: underlay of /etc/localtime required more than 50 (78) bind mounts
/usr/bin/fusermount3: entry for /tmp/rootfs-3060645730/root not found in /etc/mtab
FATAL: While running host post start tasks: while unmounting fuse directory: /tmp/rootfs-3060645730/root: exit status 1
/bin/bash: line 1: /bin/bash: No such file or directory
FATAL: host post start process failed: host post start tasks failed
Work dir:
I'm not entirely sure what has happened here but it appears to be a issue with singularity.
By the way, today we released version 2.0.0, though it does not contain anything that would naturally fix the issue observed above.
Closing this issue as the original issues has been solved. Please open a new issue if you encounter further problems.
Operating System
CentOS 7
Other Linux
No response
Workflow Version
23.04.2
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
${nf} run ${base_dir}/wf-single-cell \ -w ${base_dir}/output_GBM001_full/workspace \ -profile singularity \ --fastq /home/projects/cu_10027/data/projects/gbm/data/data_processed/rigshospitalet/rna/ont/samples/GBM001/PAQ11402_pass_f182e1fc_ddede2b4.fastq.gz \ --kit_name 3prime \ --kit_version v3 \ --expected_cells 10000 \ --ref_genome_dir /home/projects/cu_10027/data/genomes/cellranger/refdata-gex-GRCh38-2020-A \ --out_dir ${base_dir}/output_GBM001_full \ --plot_umaps \ -resume \ -c ${cfg}
Workflow Execution - CLI Execution Profile
singularity
What happened?
The pipeline failed during the minimap step.
Relevant log output
Application activity log entry
No response