我到处都在寻找这个错误，但是找不到任何解决方案。
我必须运行ec2实例，一个实例使用elasticsearch，另一个实例使用kibana。
在我的浏览器中如果我在端口9200上访问elasticsearch我可以检索数据。 但是如果我对kibana做同样的事情，我会得到
"Kibana server is not ready yet"
我不是弹性搜索和基巴纳人的专家，所以如果有人可以帮助我弄清楚我在做错什么。
我发布了模板：
这是我的kibana.yml
# 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: "your-hostname"
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["https://10.0.105.100: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 are used to verify the identity of Kibana to Elasticsearch and are required when
# xpack.security.http.ssl.client_authentication in Elasticsearch is set to required.
#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"
这是我的elasticsearch：
# ======================== 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: production
#
# ------------------------------------ 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
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# 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"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1"]
#
# 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
cluster.name: production
node.name: node-1
network.host: 0.0.0.0
http.port: 9200
discovery.seed_hosts: ["host1"]
cluster.initial_master_nodes: ["10.0.105.100"]
elasticsearch和kibana都是相同的版本7.6.2
有什么想法吗？
答案 0 :(得分：1)
基于对“评论”部分的讨论，我总结了可能有助于解决问题的步骤：
答案 1 :(得分：0)
May 3 11:37:38 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:38Z","tags":["warning","elasticsearch","admin"],"pid":794,"message":"No living connections"}
May 3 11:37:41 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:41Z","tags":["warning","elasticsearch","admin"],"pid":794,"message":"Unable to revive connection: https://10.0.105.100:9200/"}
May 3 11:37:41 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:41Z","tags":["warning","elasticsearch","admin"],"pid":794,"message":"No living connections"}
May 3 11:37:43 ip-10-0-105-101 systemd-resolved[645]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 3 11:37:43 ip-10-0-105-101 systemd-resolved[645]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 3 11:37:43 ip-10-0-105-101 systemd[1]: Stopping Kibana...
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins-system"],"pid":794,"message":"Stopping all plugins."}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","bfetch"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","graph"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","apm"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","cloud"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","spaces"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","home"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","share"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","data"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","translations"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","apm_oss"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","security"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","features"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","timelion"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","canvas"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","metrics"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","usageCollection"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","code"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","encryptedSavedObjects"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","infra"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","licensing"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","siem"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","plugins","taskManager"],"pid":794,"message":"Stopping plugin"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["info","savedobjects-service"],"pid":794,"message":"Starting saved objects migrations"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["warning","savedobjects-service"],"pid":794,"message":"Unable to connect to Elasticsearch. Error: Cluster client cannot be used after it has been closed."}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: {"type":"log","@timestamp":"2020-05-03T11:37:43Z","tags":["fatal","root"],"pid":794,"message":"Error: Cluster client cannot be used after it has been closed.\n at ClusterClient.assertIsNotClosed (/usr/share/kibana/src/core/server/elasticsearch/cluster_client.js:187:13)\n at ClusterClient._defineProperty [as callAsInternalUser] (/usr/share/kibana/src/core/server/elasticsearch/cluster_client.js:108:12)\n at callAsInternalUser (/usr/share/kibana/src/core/server/elasticsearch/elasticsearch_service.js:72:29)"}
May 3 11:37:43 ip-10-0-105-101 kibana[794]: FATAL Error: Cluster client cannot be used after it has been closed.
May 3 11:37:45 ip-10-0-105-101 systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
May 3 11:37:45 ip-10-0-105-101 systemd[1]: kibana.service: Failed with result 'exit-code'.
May 3 11:37:45 ip-10-0-105-101 systemd[1]: Stopped Kibana.
May 3 11:37:45 ip-10-0-105-101 systemd[1]: Started Kibana.
第一个错误块是由于尚未设置ICMP。但是一旦我允许ICMP，它们就不会再发生。
这些是我能找到的有关kibana的所有日志，因为我没有kibana.log的特定文件onlig
答案 2 :(得分：0)
在 kibana.yml 中，确保您指向正确的 Elastic 搜索实例。 默认情况下它指向 9200 端口。如果您更改了端口，则需要在 kibana.yml
的 elasticsearch.hosts 属性中提及相同内容elasticsearch.hosts: ["http://localhost:9401"]
此外，在 ES .kibana_task_manager_1 和 .kibana_1 上可能有 2 个索引。如果它们的状态不是绿色，则可能会产生问题。 删除这 2 个索引并重新启动 kibana。