Open adomingues opened 8 months ago
This error is usually downstream of something else. And indeed when checking your log there is something else:
Feb-14 17:01:20.280 [Task monitor] ERROR nextflow.processor.TaskProcessor - Error executing process > 'NFCORE_FETCHNGS:SRA:ASPERA_CLI (SRX5414348_SRR8615405)'
Caused by:
Essential container in task exited
Command executed:
ascp \
-QT -l 300m -P33001 \
-i $CONDA_PREFIX/etc/aspera/aspera_bypass_dsa.pem \
era-fasp@fasp.sra.ebi.ac.uk:/vol1/fastq/SRR861/005/SRR8615405/SRR8615405_1.fastq.gz \
SRX5414348_SRR8615405_1.fastq.gz
echo "b580a559c8f7139401bad5e4ebf26b0f SRX5414348_SRR8615405_1.fastq.gz" > SRX5414348_SRR8615405_1.fastq.gz.md5
md5sum -c SRX5414348_SRR8615405_1.fastq.gz.md5
ascp \
-QT -l 300m -P33001 \
-i $CONDA_PREFIX/etc/aspera/aspera_bypass_dsa.pem \
era-fasp@fasp.sra.ebi.ac.uk:/vol1/fastq/SRR861/005/SRR8615405/SRR8615405_2.fastq.gz \
SRX5414348_SRR8615405_2.fastq.gz
echo "8b56dd909ddbc900e679ec69afcf9fc6 SRX5414348_SRR8615405_2.fastq.gz" > SRX5414348_SRR8615405_2.fastq.gz.md5
md5sum -c SRX5414348_SRR8615405_2.fastq.gz.md5
cat <<-END_VERSIONS > versions.yml
"NFCORE_FETCHNGS:SRA:ASPERA_CLI":
aspera_cli: $(ascli --version)
END_VERSIONS
Command exit status:
1
Command output:
(empty)
Work dir:
s3://buck-xxx/scratch/2o9s4gXJF3Gx3t/d9/c4c9fc61a46b1c62ee9ef3e762c88a
I would try to investigate why this task failed. Could be something in the work directory or additional logs in your AWS account that can give more insight
Expected behavior and actual behavior
I am running the
fetchngs
pipeline using sequera platform - AWS batch - to retrieve a public datasest of about 1000 samples (~10TB data in total), but there was an error which I believe is related to nexflow / AWS SDK:Steps to reproduce the problem
I can provide a rough outline of what I am did:
AWS batch, working dir the s3 bucket where the output is also going to be stored.
Program output
(Copy and paste here output produced by the failing execution. Please highlight it as a code block. Whenever possible upload the
.nextflow.log
file.)Environment
Additional context
I ran the tasks command on a local terminal - to exclude issues with the files themselves - and it completed successfully.
small subset of the nextflow log:
short-nextflow.log