Kibana server is not ready yet

Hey,

I just install elasticsearch and kibana version 7.8.1. I am able to access elasticsearch through IP but when I try to access kibana through IP it says kibana server not ready yet. can someone help here

below is elasticsearch.yml file

# ======================== 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: cluster name
#
# ------------------------------------ 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: /opt/data/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: ["0.0.0.0", "x.x.x.x"]

#
# 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
#xpack.security.enabled: true

below is kibana.yml file

# 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: "x.x.x.x"

# 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: "name"

# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://x.x.x.x: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: "user"
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"

can some one help here

Hi @Bigranawab,

Can you provide the Kibana logs when it starts up, I'm curious if there's anything informative there that can help.

these were the logs

:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","crossClusterReplication"],
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","indexLifecycleManagement"]
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","watcher"],"pid":29364,"mes
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","rollup"],"pid":29364,"mess
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","snapshotRestore"],"pid":29
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","transform"],"pid":29364,"m
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","ingestPipelines"],"pid":29
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","plugins","monitoring","monitoring","
Sep 04 11:35:33 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:35:33Z","tags":["info","savedobjects-service"],"pid":29364,"
Sep 04 11:36:03 elk kibana[29364]: {"type":"log","@timestamp":"2020-09-04T11:36:03Z","tags":["warning","savedobjects-service"],"pid":2936

Thanks for providing those, would you be able to grab the history from the first log line to when Kibana is up and running? It seems to have only captured 10 lines in the middle of the startup cycle.

The last line should be something like the following

[info][listening] Server running at http://localhost:5603

Service starts normally but can not be access over web.
how can I get more logs?

You can set logging.verbose: true within kibana.yml and it will provide more logs.

Hey,
I resolved this issue, I re-installed elasticsearch and kibana as they both were newly isntalled, set elasticsearch to localhost and set kibana to be accessed over IP address.
after restarting both services, I was able to access kibana through IP.
I know by doing this I wont be able to send data to elasticsearch as it is on localhost, so I stopped both services and reconfigured elasticsearch on IP and somehow I was able to access kibana and send logs to elasticsearch.

During this activity I came to know (correct me if I am wrong) that this issue will occur when kibana is not able to access elasticsearch.

I think elasticsearch team should have a documentation on this issue with possible reasons and their solution.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.