# Elasticsearch master not discovered exception in AWS EC2 instance
**URL:** https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292
**Category:** Elasticsearch
**Created:** [October 4, 2019, 7:14am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292 "2019-10-04T07:14:17Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:14am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/1 "2019-10-04T07:14:18Z")
We configured elasticsearch in the AWS EC2 instance. It was running smoothly we upgraded to version 7.3.1 (both elasticsearch and kibana in the same version).
While starting both services, elasticsearch(ip:9200/?pretty) works fine and produces following result.
{
"name" : "node-1",
"cluster\_name" : "c1s",
"cluster\_uuid" : "_na_",
"version" : {
"number" : "7.3.1",
"build\_flavor" : "default",
"build\_type" : "deb",
"build\_hash" : "4749ba6",
"build\_date" : "2019-08-19T20:19:25.651794Z",
"build\_snapshot" : false,
"lucene\_version" : "8.1.0",
"minimum\_wire\_compatibility\_version" : "6.8.0",
"minimum\_index\_compatibility\_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}
but when we go into the kibana(ip:5601), it throws **kibana server not ready yet**
also when we go to **http:ip:9200/\_cat/nodes/** , it produces error,
`{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}`
---
### Author:  [@MiTschMR](https://discuss.elastic.co/u/MiTschMR)
#### Post date: [October 4, 2019, 7:18am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/2 "2019-10-04T07:18:16Z")
Hi @Ilamparithi_Karthike
Please share the configuration files for Elasticsearch and Kibana with us. Without them it is rather difficult to guess, what your setup is.
---
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/3 "2019-10-04T07:25:31Z")
# ======================== Elasticsearch Configuration =========================
```
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: c1s
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: 0.0.0.0
network.publish_host: xxxx.aws.com(public DNS)
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
```
---
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:29am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/4 "2019-10-04T07:29:13Z")
```
# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601
# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: 0.0.0.0
# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""
# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false
# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576
# The Kibana server's name. This is used for display purposes.
server.name: "c1s-staging"
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://ip:9200"]
# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true
# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"
# The default application to load.
#kibana.defaultAppId: "home"
# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
#elasticsearch.username: "kibana"
#elasticsearch.password: "pass"
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key
# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key
# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]
# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500
# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000
# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]
# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}
# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 30000
# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000
# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
#elasticsearch.logQueries: false
# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid
# Enables you specify a file where Kibana stores log output.
#logging.dest: stdout
# Set the value of this setting to true to suppress all logging output.
#logging.silent: false
# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false
# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false
# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000
# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English - en , by default , Chinese - zh-CN .
#i18n.locale: "en"
```
---
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:29am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/5 "2019-10-04T07:29:38Z")
@MiTschMR hope this helps
---
### Author:  [@MiTschMR](https://discuss.elastic.co/u/MiTschMR)
#### Post date: [October 4, 2019, 7:33am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/6 "2019-10-04T07:33:39Z")
Hi @Ilamparithi_Karthike
Thank you for the configurations. What does the logs of Elasticsearch and Kibana say? There must be something (like an error etc.) that indicates what is wrong.
---
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:37am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/7 "2019-10-04T07:37:34Z")
This was the log of elasticsearch
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:800) [netty-transport-4.1.36.Final.jar:4.1.36.Final]
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:757) [netty-transport-4.1.36.Final.jar:4.1.36.Final]
at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1031) [netty-transport-4.1.36.Final.jar:4.1.36.Final]
at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:310) [netty-transport-4.1.36.Final.jar:4.1.36.Final]
at org.elasticsearch.http.netty4.Netty4HttpChannel.sendResponse(Netty4HttpChannel.java:43) [transport-netty4-client-7.3.1.jar:7.3.1]
at org.elasticsearch.http.DefaultRestChannel.sendResponse(DefaultRestChannel.java:129) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.rest.RestController$ResourceHandlingHttpChannel.sendResponse(RestController.java:536) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.rest.action.RestActionListener.onFailure(RestActionListener.java:58) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.action.support.TransportAction$1.onFailure(TransportAction.java:74) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$3.onClusterServiceClose(TransportMasterNodeAction.java:244) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onClusterServiceClose(ClusterStateObserver.java:318) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onClose(ClusterStateObserver.java:237) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.cluster.service.ClusterApplierService.doStop(ClusterApplierService.java:175) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.common.component.AbstractLifecycleComponent.stop(AbstractLifecycleComponent.java:79) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.cluster.service.ClusterService.doStop(ClusterService.java:108) [elasticsearch-7.3.1.jar:7.3.1]
at org.elasticsearch.common.component.AbstractLifecycleComponent.stop(AbstractLifecycleComponent.java:79) [elasticsearch-7.3.1.jar:7.3.1]
---
### Author:  [@Ilamparithi\_Karthike](https://discuss.elastic.co/u/Ilamparithi_Karthike)
#### Post date: [October 4, 2019, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/8 "2019-10-04T07:43:43Z")
@MiTschMR for kibana, i can't find logs
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 1, 2019, 7:43am UTC](https://discuss.elastic.co/t/elasticsearch-master-not-discovered-exception-in-aws-ec2-instance/202292/9 "2019-11-01T07:43:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.