You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I just tested with -profile test_full myself and it seems fine. The files in question are on an amazon s3 storage, that really should not be a problem.
I found in your log file Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: 90Y1M4SDXCZ2JDQ2; S3 Extended Request ID: i2GFgVAWldXstAxHeLaBjsPGcX+nNzf/w/RjN4mRGrVzwAkW1ebUOQVHU3kJv6KmRIYm4++7nhM=; Proxy: null)
That might be the issue? You seem to have an AWS Access Key Id provided (that isnt needed afaik) that isnt valid. Removing that key may do it. I have no idea of AWS computing/files though, so you might want to look into nf-core slack to get further advice. The problem seems to me not related to this pipeline, so I close it for now.
Please open another issue if you encounter another problem.
Description of the bug
When running the test_full profile, the following error is seen:
ERROR ~ Cannot access file: /ngi-igenomes/test-data/ampliseq/SRR10070130_1.fastq.gz
Command used and terminal output
nextflow run nf-core/ampliseq -latest -resume -profile test_full,docker --outdir ./results/test_2/ --picrust
Relevant files
nextflow.log
System information
nf-core/ampliseq v2.8.0-gf3c97e1
N E X T F L O W ~ version 23.10.1
Intel mac
The text was updated successfully, but these errors were encountered: