# Yellow health status on elastic causing kibana to fail at launch?
**URL:** https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722
**Category:** Kibana
**Created:** [June 19, 2024, 9:52am UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722 "2024-06-19T09:52:59Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Ama](https://discuss.elastic.co/u/Ama)
#### Post date: [June 19, 2024, 9:52am UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722/1 "2024-06-19T09:52:59Z")
Hey everyone,
I tried to launch elasticsearch this morning but I got the following logs on my terminal:
```auto
[2024-06-19T11:44:33,701][INFO][o.e.r.s.FileSettingsService] [LAPTOP-32SOQ4EE] setting file [C:\Users\amazi\Downloads\elasticsearch-8.14.0\config\operator\settings.json] not found, initializing [file_settings] as empty
[2024-06-19T11:44:33,711][INFO][o.e.c.c.NodeJoinExecutor] [LAPTOP-32SOQ4EE] node-join: [{LAPTOP-32SOQ4EE}{uX3EK5tVQOieVnq7d6JRVQ}{wDv5vWGCS3a2CgZukxOiVw}{LAPTOP-32SOQ4EE}{127.0.0.1}{127.0.0.1:9300}{cdfhilmrstw}{8.14.0}{7000099-8505000}] with reason [completing election]
[2024-06-19T11:44:33,727][INFO][o.e.h.AbstractHttpServerTransport] [LAPTOP-32SOQ4EE] publish_address {192.168.10.249:9200}, bound_addresses {[::]:9200}
[2024-06-19T11:44:33,789][INFO][o.e.n.Node] [LAPTOP-32SOQ4EE] started {LAPTOP-32SOQ4EE}{uX3EK5tVQOieVnq7d6JRVQ}{wDv5vWGCS3a2CgZukxOiVw}{LAPTOP-32SOQ4EE}{127.0.0.1}{127.0.0.1:9300}{cdfhilmrstw}{8.14.0}{7000099-8505000}{ml.allocated_processors=4, ml.machine_memory=3967725568, transform.config_version=10.0.0, xpack.installed=true, ml.config_version=12.0.0, ml.max_jvm_size=1983905792, ml.allocated_processors_double=4.0}
[2024-06-19T11:44:35,133][INFO][o.e.x.s.a.Realms] [LAPTOP-32SOQ4EE] license mode is [basic], currently licensed security realms are [reserved/reserved,file/default_file,native/default_native]
[2024-06-19T11:44:35,235][INFO][o.e.l.ClusterStateLicenseService] [LAPTOP-32SOQ4EE] license [2756b818-3984-42d0-938c-4843baed9365] mode [basic] - valid
[2024-06-19T11:44:35,301][INFO][o.e.g.GatewayService] [LAPTOP-32SOQ4EE] recovered [34] indices into cluster_state
[2024-06-19T11:44:39,608][INFO][o.e.h.n.s.HealthNodeTaskExecutor] [LAPTOP-32SOQ4EE] Node [{LAPTOP-32SOQ4EE}{uX3EK5tVQOieVnq7d6JRVQ}] is selected as the current health node.
[2024-06-19T11:44:45,176][INFO][o.e.c.r.a.AllocationService] [LAPTOP-32SOQ4EE] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana-observability-ai-assistant-conversations-000001][0]]])." previous.health="RED" reason="shards started [[.kibana-observability-ai-assistant-conversations-000001][0]]"
```
I can access elasticsearch just fine, but then when I try to start kibana it won't work, and I'm getting the following logs:
```auto
[2024-06-19T11:37:08.345+02:00][INFO][plugins.alerting] using indexes and aliases for persisting alerts
[2024-06-19T11:37:37.820+02:00][WARN][plugins.reporting.config] Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2024-06-19T11:37:49.806+02:00][INFO][plugins.cloudSecurityPosture] Registered task successfully [Task: cloud_security_posture-stats_task]
[2024-06-19T11:38:44.959+02:00][INFO][plugins.securitySolution.endpoint:user-artifact-packager:1.0.0] Registering endpoint:user-artifact-packager task with timeout
of [20m], interval of [60s] and policy update batch size of [25]
[2024-06-19T11:38:44.961+02:00][INFO][plugins.securitySolution.endpoint:complete-external-response-actions] Registering task [endpoint:complete-external-response-actions] with timeout of [5m] and run interval of [60s]
[2024-06-19T11:38:53.068+02:00][INFO][plugins.assetManager] Server is NOT enabled
[2024-06-19T11:38:54.134+02:00][INFO][plugins.screenshotting.chromium] Browser executable: C:\Users\amazi\Downloads\kibana-8.14.0\node_modules\@kbn\screenshotting-plugin\chromium\chrome-win\chrome.exe
[2024-06-19T11:39:56.825+02:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. connect ETIMEDOUT 192.168.10.28:9200
```
I was suspecting that it's due to the yellow health status, because everything worked just fine yesterday and I didn't change anything in my .yml files and they still have default settings. any ideas ? I'm on windows btw
EDIT: here are my .yml files just in case:
elasticsearch.yml
```auto
# ======================== 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: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- 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: 192.168.0.1
#
# 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.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.
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 18-06-2024 10:09:19
#
# --------------------------------------------------------------------------------
# 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: ["LAPTOP-32SOQ4EE"]
# 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 -------------------------
```
kibana.yml:
```auto
# 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: "localhost"
# 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://localhost: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: "pass"
# 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.default:
# type: file
# fileName: /var/logs/kibana.log
# layout:
# type: json
# Example with size based log rotation
#logging.appenders.default:
# type: rolling-file
# fileName: /var/logs/kibana.log
# policy:
# type: size-limit
# size: 256mb
# strategy:
# type: numeric
# max: 10
# 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
# Enables debug logging on the browser (dev console)
#logging.browser.root:
# 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"
# =================== 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
# This section was automatically generated during setup.
elasticsearch.hosts: ['https://192.168.10.28:9200']
elasticsearch.serviceAccountToken: ***************
elasticsearch.ssl.certificateAuthorities: ['C:\Users\amazi\Downloads\kibana-8.14.0\data\ca_1718706315734.crt']
xpack.fleet.outputs: [{id: fleet-default-output, name: default, is_default: true, is_default_monitoring: true, type: elasticsearch, hosts: ['https://192.168.10.28:9200'], ca_trusted_fingerprint: *************** }]
```
Thanks in advance
---
### Author:  [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [June 20, 2024, 12:41pm UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722/2 "2024-06-20T12:41:45Z")
Hi @Ama,
Welcome to the community! Looking at your logs it looks like the cluster that was red, but is now yellow:
```auto
[2024-06-19T11:44:45,176][INFO][o.e.c.r.a.AllocationService] [LAPTOP-32SOQ4EE] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana-observability-ai-assistant-conversations-000001][0]]])." previous.health="RED" reason="shards started [[.kibana-observability-ai-assistant-conversations-000001][0]]"
```
I would recommend following the steps in [this troubleshooting guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html#:~:text=Red%20health%20status%3A%20The%20cluster,and%20can%20degrade%20cluster%20performance.) to find out the cause of the issue. There is also some recommendations on how to fix such issues as well.
Hope that helps!
---
### Author:  [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [June 20, 2024, 12:50pm UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722/3 "2024-06-20T12:50:36Z")
> [@Ama](#):
>
> because everything worked just fine yesterday and I didn't change anything in my .yml files and they still have default settings. any ideas ?
Your IP has changed, check your logs.
> [2024-06-19T11:44:33,727][INFO][o.e.h.AbstractHttpServerTransport] [LAPTOP-32SOQ4EE] publish\_address { **192.168.10.249** :9200}
But in your `kibana.yml` you have this:
> elasticsearch.hosts: ['https:// **192.168.10.28** :9200']
And in your kibana log errors you have this:
> [2024-06-19T11:39:56.825+02:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. connect **ETIMEDOUT 192.168.10.28:9200**
The health status has nothing to do with it, Kibana just cant connect to your Elasticsearch anymore.
On your `kibana.yml` change all references to the IP `192.168.10.28` to `127.0.0.1` and it should work.
---
### Author:  [@Ama](https://discuss.elastic.co/u/Ama)
#### Post date: [June 21, 2024, 9:20am UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722/4 "2024-06-21T09:20:18Z")
thank you! I was able to fix my problem by doing just that
---
### Author:  [@Ama](https://discuss.elastic.co/u/Ama)
#### Post date: [June 21, 2024, 9:20am UTC](https://discuss.elastic.co/t/yellow-health-status-on-elastic-causing-kibana-to-fail-at-launch/361722/5 "2024-06-21T09:20:53Z")
thank you for the kind welcome 🙂 I managed to fix it