Skip to content
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

test_full Cannot access file fastq #698

Closed
jambler24 opened this issue Feb 1, 2024 · 1 comment
Closed

test_full Cannot access file fastq #698

jambler24 opened this issue Feb 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@jambler24
Copy link

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

@jambler24 jambler24 added the bug Something isn't working label Feb 1, 2024
@d4straub
Copy link
Collaborator

d4straub commented Feb 2, 2024

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.

@d4straub d4straub closed this as completed Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants