Wrong signer set for or : – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Wrong signer set for or : ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “wrong signer set for [{}] or [{}]: [{}]” classname is AwsEc2ServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (awsSigner != null) {
            logger.debug("using AWS API signer [{}]"; awsSigner);
            try {
                AwsSigner.configureSigner(awsSigner; clientConfiguration);
            } catch (IllegalArgumentException e) {
                logger.warn("wrong signer set for [{}] or [{}]: [{}]";
                        CLOUD_EC2.SIGNER; CLOUD_AWS.SIGNER; awsSigner);
            }
        }

        // Increase the number of retries in case of 5xx API responses




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content