Fix error: Unable to retrieve node fs stats

Elastic Stack ECE ECK Elastic Cloud Hosted Self Managed

 Error: unable to retrieve node fs stats 

This error occurs when Kibana or another Elasticsearch client can't fetch version information from an Elasticsearch node. Without version information, the client can't confirm compatibility or proceed with requests.

Possible causes include network issues, incorrect configuration, or unavailable nodes. To diagnose, first try these general actions:

• Ensure that all nodes are up and running.
• Check the network connectivity between the client and the nodes.
• Verify configuration settings.

If the issue persists, check the Elasticsearch logs for details, then continue with the tips below.

This error typically appears in the Kibana logs during startup. Because Kibana acts as a client to Elasticsearch, it requires access to several resources:

• The cluster's host and port
• Authentication credentials, if required
• TLS settings, if applicable

If Kibana can't reach the configured nodes, it can't verify version compatibility and logs the unable to retrieve error. Check these possible access issues:

• One or more entries in elasticsearch.hosts are unreachable or misconfigured
• The KBN_PATH_CONF environment variable points to a different config file
• A firewall is blocking access between Kibana and Elasticsearch

Settings are defined in kibana.yml, usually located at $KIBANA_HOME/config. You can change the path as needed:

KBN_PATH_CONF=/home/kibana/config ./bin/kibana

Check the relevant settings:

elasticsearch.hosts: ["http://localhost:9200"]
elasticsearch.username: "kibana"
elasticsearch.password: "your_password"
elasticsearch.ssl.certificateAuthorities: ["path/to/ca.crt"]

Kibana tries every endpoint in elasticsearch.hosts, so even one unreachable node can cause the error. Use https if your cluster requires encrypted communication.

Use curl to test the connection to each host in elasticsearch.hosts:

curl http://es01:9200/

If you're using TLS, try one of the following:

# Insecure test
curl -u elastic -k https://es01:9200/

# Secure test
curl -u elastic --cacert ~/certs/ca/ca.crt https://es01:9200/

Example response:

{
  "name" : "node01",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "fxP-R0FTRcmTl_AWs7-DiA",
  "version" : {
    "number" : "7.13.3",
    "build_flavor" : "default",
    "build_type" : "tar",
    "build_hash" : "5d21bea28db1e89ecc1f66311ebdec9dc3aa7d64",
    "build_date" : "2021-07-02T12:06:10.804015202Z",
    "build_snapshot" : false,
    "lucene_version" : "8.8.2"
  },
  "tagline" : "You Know, for Search"
}

If you're still encountering issues, check the Kibana logs for more details and context.