Skip to content

ERROR ~ Class definition not found: com/amazonaws/AmazonServiceException #1519

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

Open
slives-lab opened this issue Mar 19, 2025 · 5 comments
Open
Labels
bug Something isn't working

Comments

@slives-lab
Copy link

Description of the bug

error when running:

nextflow run nf-core/rnaseq -r 3.18.0 --input samplesheet.csv --outdir nextflow_rna_seq --genome GRCh37 -profile singularity

ERROR ~ Class definition not found: com/amazonaws/AmazonServiceException

Command used and terminal output

nextflow run nf-core/rnaseq -r 3.18.0 --input samplesheet.csv --outdir nextflow_rna_seq --genome GRCh37 -profile singularity

ERROR ~ Class definition not found: com/amazonaws/AmazonServiceException

Relevant files

No response

System information

No response

@slives-lab slives-lab added the bug Something isn't working label Mar 19, 2025
@pinin4fjords
Copy link
Member

Could you provide more detail on your execution environment, Nextflow version and Nextflow installation method please?

@slives-lab
Copy link
Author

The environment is a linux HPC CentOS 7.
nextflow version 23.04.1.5866
I'm not sure if it was installed using:
conda install nf-core
or
conda install bioconda::nf-core
Here is the nextflow version from conda list
nextflow 23.04.1 bioconda

@pinin4fjords
Copy link
Member

I can only think that perhaps something is broken in the nextflow/ java install, I doubt it's anything specific to this workflow.

You could try a fresh Nextflow install, perhaps in a fresh Conda env. It might also be worth asking about on the Nextflow Slack.

@slives-lab
Copy link
Author

I tried to install nextflow in a new conda environment and the error is what I posted above. Is there an option to run without any amazon credentials ( --no-sign-request) ?

@maxulysse
Copy link
Member

you can add this to a custom config file and provide it to the pipeline as you launch:

aws.client.anonymous = true

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

3 participants