Kibana server is not ready yet

I am getting this in the browser. Here are my configs

messi@fifa:~$ sudo systemctl status kibana elasticsearch
● kibana.service - Kibana
     Loaded: loaded (/lib/systemd/system/kibana.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-09-14 21:21:08 IST; 1min 16s ago
       Docs: https://www.elastic.co
   Main PID: 2818 (node)
      Tasks: 11 (limit: 2247)
     Memory: 250.1M
        CPU: 38.777s
     CGroup: /system.slice/kibana.service
             └─2818 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist

Sep 14 21:21:50 fifa kibana[2818]: [2022-09-14T21:21:50.910+05:30][INFO ][plugins.ruleRegistry] Installing common resources shared between all indices
Sep 14 21:21:51 fifa kibana[2818]: [2022-09-14T21:21:51.022+05:30][INFO ][plugins.cloudSecurityPosture] Registered task successfully [Task: cloud_security_posture-stats_task]
Sep 14 21:21:52 fifa kibana[2818]: [2022-09-14T21:21:52.851+05:30][INFO ][plugins.screenshotting.config] Chromium sandbox provides an additional layer of protection, and is support>
Sep 14 21:21:52 fifa kibana[2818]: [2022-09-14T21:21:52.972+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. connect ECONNREFUS>
Sep 14 21:21:55 fifa kibana[2818]: [2022-09-14T21:21:55.392+05:30][INFO ][plugins.screenshotting.chromium] Browser executable: /usr/share/kibana/x-pack/plugins/screenshotting/chrom>
Sep 14 21:22:16 fifa kibana[2818]: [2022-09-14T21:22:16.192+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 21:22:17 fifa kibana[2818]: [2022-09-14T21:22:17.964+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 21:22:20 fifa kibana[2818]: [2022-09-14T21:22:20.473+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 21:22:22 fifa kibana[2818]: [2022-09-14T21:22:22.964+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 21:22:25 fifa kibana[2818]: [2022-09-14T21:22:25.451+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>

● elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-09-14 21:22:14 IST; 11s ago
       Docs: https://www.elastic.co
   Main PID: 2807 (java)
      Tasks: 80 (limit: 2247)
     Memory: 962.0M
        CPU: 1min 19.279s
     CGroup: /system.slice/elasticsearch.service
             ├─2807 /usr/share/elasticsearch/jdk/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=/usr/share/elasticsearch/bin/elasticsearch -Dcli.libs=lib/t>
             ├─2884 /usr/share/elasticsearch/jdk/bin/java -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -Djava.security.manager=allow -XX:+AlwaysPreTou>
             └─2913 /usr/share/elasticsearch/modules/x-pack-ml/platform/linux-x86_64/bin/controller

Sep 14 21:21:08 fifa systemd[1]: Starting Elasticsearch...
Sep 14 21:22:14 fifa systemd[1]: Started Elasticsearch.

kibana.yml

# For more configuration options see the configuration guide for Kibana in
# https://www.elastic.co/guide/index.html

# =================== System: Kibana Server ===================
# 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: "a.b.c.d"

# 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.
# Defaults to `false`.
#server.rewriteBasePath: false

# Specifies the public URL at which Kibana is available for end users. If
# `server.basePath` is configured this URL should end with the same basePath.
#server.publicBaseUrl: ""

# The maximum payload size in bytes for incoming server requests.
#server.maxPayload: 1048576

# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"

# =================== System: Kibana Server (Optional) ===================
# 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

# =================== System: Elasticsearch ===================
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://a.b.c.d:9200"]

# 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_system"
elasticsearch.password: "test"

# Kibana can also authenticate to Elasticsearch via "service account tokens".
# Service account tokens are Bearer style tokens that replace the traditional username/password based configuration.
# Use this token instead of a username/password.
# elasticsearch.serviceAccountToken: "my_token"

# 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

# The maximum number of sockets that can be used for communications with elasticsearch.
# Defaults to `Infinity`.
#elasticsearch.maxSockets: 1024

# Specifies whether Kibana should use compression for communications with elasticsearch
# Defaults to `false`.
#elasticsearch.compression: false

# 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

# =================== System: Elasticsearch (Optional) ===================
# 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

# 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

# =================== System: Logging ===================
# Set the value of this setting to off to suppress all logging output, or to debug to log everything. Defaults to 'info'
#logging.root.level: debug

# Enables you to specify a file where Kibana stores log output.
logging:
  appenders:
    file:
      type: file
      fileName: /var/log/kibana/kibana.log
      layout:
        type: json
  root:
    appenders:
      - default
      - file
#  layout:
#    type: json

# Logs queries sent to Elasticsearch.
#logging.loggers:
#  - name: elasticsearch.query
#    level: debug

# Logs http responses.
#logging.loggers:
#  - name: http.server.response
#    level: debug

# Logs system usage information.
#logging.loggers:
#  - name: metrics.ops
#    level: debug

# =================== System: Other ===================
# The path where Kibana stores persistent data not saved in Elasticsearch. Defaults to data
#path.data: data

# Specifies the path where Kibana creates the process ID file.
pid.file: /run/kibana/kibana.pid

# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000ms.
#ops.interval: 5000

# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English (default) "en", Chinese "zh-CN", Japanese "ja-JP", French "fr-FR".
#i18n.locale: "en"
#xpack.security.enabled: true
#xpack.ingestManager.fleet.tlsCheckDisabled: true
#xpack.encryptedSavedObjects.encryptionKey: "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
# =================== Frequently used (Optional)===================

# =================== Saved Objects: Migrations ===================
# Saved object migrations run at startup. If you run into migration-related issues, you might need to adjust these settings.

# The number of documents migrated at a time.
# If Kibana can't start up or upgrade due to an Elasticsearch `circuit_breaking_exception`,
# use a smaller batchSize value to reduce the memory pressure. Defaults to 1000 objects per batch.
#migrations.batchSize: 1000

# The maximum payload size for indexing batches of upgraded saved objects.
# To avoid migrations failing due to a 413 Request Entity Too Large response from Elasticsearch.
# This value should be lower than or equal to your Elasticsearch cluster’s `http.max_content_length`
# configuration option. Default: 100mb
#migrations.maxBatchSizeBytes: 100mb

# The number of times to retry temporary migration failures. Increase the setting
# if migrations fail frequently with a message such as `Unable to complete the [...] step after
# 15 attempts, terminating`. Defaults to 15
#migrations.retryAttempts: 15

# =================== Search Autocomplete ===================
# Time in milliseconds to wait for autocomplete suggestions from Elasticsearch.
# This value must be a whole number greater than zero. Defaults to 1000ms
#unifiedSearch.autocomplete.valueSuggestions.timeout: 1000

# Maximum number of documents loaded by each shard to generate autocomplete suggestions.
# This value must be a whole number greater than zero. Defaults to 100_000
#unifiedSearch.autocomplete.valueSuggestions.terminateAfter: 100000

Elasticsearch.yml

# ======================== 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: my-application
#
# ------------------------------------ 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 -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
network.host: a.b.c.d
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
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.type: single-node
#
#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.
#
#
# --------------------------------- Readiness ----------------------------------
#
# Enable an unauthenticated TCP readiness endpoint on localhost
#
#readiness.port: 9399
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false
#xpack.security.enabled: true
#xpack.security.authc.api_key.enabled: true
#
#xpack:
#  security:
#    authc:
#      realms:
#        native:
#          native1:
#            order: 0
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 14-09-2022 05:33:15
#
# --------------------------------------------------------------------------------

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
#cluster.initial_master_nodes: ["fifa"]

# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0

# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
#transport.host: 0.0.0.0

#----------------------- END SECURITY AUTO CONFIGURATION -------------------------

Looks like Kibana can not connect to elasticsearch for more information on this per the docs run

journalctl -u kibana.service

And look at the logs and look for the error

Sep 14 11:27:45 fifa systemd[1]: Started Kibana.
Sep 14 11:27:57 fifa kibana[892]: [2022-09-14T11:27:57.102+05:30][INFO ][node] Kibana process configured with roles: [background_tasks, ui]
Sep 14 11:28:54 fifa kibana[892]: [2022-09-14T11:28:54.726+05:30][INFO ][http.server.Preboot] http server running at http://localhost:5601
Sep 14 11:28:54 fifa kibana[892]: [2022-09-14T11:28:54.895+05:30][INFO ][plugins-system.preboot] Setting up [1] plugins: [interactiveSetup]
Sep 14 11:28:54 fifa kibana[892]: [2022-09-14T11:28:54.912+05:30][INFO ][preboot] "interactiveSetup" plugin is holding setup: Validating Elasticsearch connection configuration…
Sep 14 11:28:55 fifa kibana[892]: [2022-09-14T11:28:55.030+05:30][INFO ][root] Holding setup until preboot stage is completed.
Sep 14 11:28:55 fifa kibana[892]: i Kibana has not been configured.
Sep 14 11:28:55 fifa kibana[892]: Go to http://localhost:5601/?code=080950 to get started.
Sep 14 12:56:47 fifa systemd[1]: Stopping Kibana...
Sep 14 12:56:56 fifa kibana[892]: [2022-09-14T12:56:55.066+05:30][INFO ][plugins-system.preboot] Stopping all plugins.
Sep 14 12:57:02 fifa systemd[1]: kibana.service: Deactivated successfully.
Sep 14 12:57:02 fifa systemd[1]: Stopped Kibana.
Sep 14 12:57:02 fifa systemd[1]: kibana.service: Consumed 40.322s CPU time.
Sep 14 12:57:02 fifa systemd[1]: Started Kibana.
Sep 14 12:57:13 fifa kibana[7690]: [2022-09-14T12:57:13.461+05:30][INFO ][node] Kibana process configured with roles: [background_tasks, ui]
Sep 14 12:58:52 fifa kibana[7690]: [2022-09-14T12:58:52.560+05:30][INFO ][http.server.Preboot] http server running at http://192.168.141.131:5601
Sep 14 12:58:52 fifa kibana[7690]: [2022-09-14T12:58:52.656+05:30][INFO ][plugins-system.preboot] Setting up [1] plugins: [interactiveSetup]
Sep 14 12:58:52 fifa kibana[7690]: [2022-09-14T12:58:52.789+05:30][WARN ][config.deprecation] The default mechanism for Reporting privileges will work differently in future version>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.202+05:30][INFO ][plugins-system.standard] Setting up [121] plugins: [translations,monitoringCollection,licensing,globalSear>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.227+05:30][INFO ][plugins.taskManager] TaskManager is identified by the Kibana UUID: ef6a598c-2982-4032-beca-7284f76aeb05
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.409+05:30][WARN ][plugins.security.config] Generating a random key for xpack.security.encryptionKey. To prevent sessions fro>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.410+05:30][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recomm>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.455+05:30][WARN ][plugins.security.config] Generating a random key for xpack.security.encryptionKey. To prevent sessions fro>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.457+05:30][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recomm>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.468+05:30][WARN ][plugins.encryptedSavedObjects] Saved objects encryption key is not set. This will severely limit Kibana fu>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.488+05:30][WARN ][plugins.actions] APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. P>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.607+05:30][WARN ][plugins.reporting.config] Generating a random key for xpack.reporting.encryptionKey. To prevent sessions f>
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.616+05:30][WARN ][plugins.alerting] APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. >
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.705+05:30][INFO ][plugins.ruleRegistry] Installing common resources shared between all indices
Sep 14 12:58:53 fifa kibana[7690]: [2022-09-14T12:58:53.742+05:30][INFO ][plugins.cloudSecurityPosture] Registered task successfully [Task: cloud_security_posture-stats_task]
Sep 14 12:58:55 fifa kibana[7690]: [2022-09-14T12:58:55.662+05:30][INFO ][plugins.screenshotting.config] Chromium sandbox provides an additional layer of protection, and is support>
Sep 14 12:58:56 fifa kibana[7690]: [2022-09-14T12:58:56.126+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:58:58 fifa kibana[7690]: [2022-09-14T12:58:58.260+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:58:59 fifa kibana[7690]: [2022-09-14T12:58:59.864+05:30][INFO ][plugins.screenshotting.chromium] Browser executable: /usr/share/kibana/x-pack/plugins/screenshotting/chrom>
Sep 14 12:59:00 fifa kibana[7690]: [2022-09-14T12:59:00.730+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:03 fifa kibana[7690]: [2022-09-14T12:59:03.272+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:05 fifa kibana[7690]: [2022-09-14T12:59:05.722+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:08 fifa kibana[7690]: [2022-09-14T12:59:08.254+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:10 fifa kibana[7690]: [2022-09-14T12:59:10.726+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:13 fifa kibana[7690]: [2022-09-14T12:59:13.249+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:15 fifa kibana[7690]: [2022-09-14T12:59:15.735+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:18 fifa kibana[7690]: [2022-09-14T12:59:18.349+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:20 fifa kibana[7690]: [2022-09-14T12:59:20.808+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>
Sep 14 12:59:23 fifa kibana[7690]: [2022-09-14T12:59:23.290+05:30][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. socket hang up - L>

am actually trying to setup a HOME Lab and following a particular blog

and if you can have a look at this too as after the following changes like adding the xpack.security and following lines to both kibana and elasticsearch.yml file am receiving Unable to Connect error and kibana automatically stops after few minutes

Apologies, No I do not help with outside Blogs / Etc as they are often not up to date. Example what you are pointing at is nearly 2 years old, is referring to 7.x and now elastic is 8.x which has changed significantly in that time especially around setup and security.

So either go back to installing 7.x Elasticsearch or follow our official documentation for 8.x

Good Luck! :slight_smile:

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