How To Solve Issues Related to Log – No ec2 metadata returned from

How To Solve Issues Related to Log – No ec2 metadata returned from

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “No ec2 metadata returned from” it’s important to understand a few problems related to Elasticsearch concepts cloud-aws, discovery-ec2, metadata, node, plugins. See bellow important tips and explanations on these concepts

Log Context

Log”no ec2 metadata returned from {}” classname is Ec2CustomNodeAttributes.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             in = urlConnection.getInputStream();
            BufferedReader urlReader = new BufferedReader(new InputStreamReader(in; StandardCharsets.UTF_8));

            String metadataResult = urlReader.readLine();
            if (metadataResult == null || metadataResult.length() == 0) {
                logger.error("no ec2 metadata returned from {}"; url);
                return null;
            }
            ec2Attributes.put("aws_availability_zone"; metadataResult);
        } catch (IOException e) {
            logger.debug("failed to get metadata for [placement/availability-zone]"; e);




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Filter out metadata fields and only return source fields in elasticsearch

21.04 K 29

S Instance Metadata For Iam Is Not  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now